First & second container

Referring to issue #6, I have made the first container with added text & image of a MacBook. I'll still need to put in some work on refactoring the code for styling. I will start working on the second container soon.
Status of first container:

[x] First container
[ ] Refactor code

Status of second container:

[ ] Second container
[ ] Refactor code

Noted I'll get to this.

@EugeneGohh howdy!
Review
I was reviewing some of the work in this draft #21 and my first suggestion is that you need to fetch upstream to get in sync with the main branch. I think your branch is behind. I was going to leave you a comment see:

Your branch is behind
But then I realize that your branch is behind main here. There's already a ThemeProvider component and I move it in #20 to be separated out from App.js by moving it to it's own folder / file, just throw in your default styling there so you can reuse it throughout the whole App and that way you don't need to repeat yourself & keep it D.R.Y. & reduce complexity. Your branch here is behind because I don't see that file & folder from #20 frontend\src\theme-style\materialtheme.js

Ignore if...
Unless you had a specific reason why you wanted to create another ThemeProvider component then ignore my suggestions above.

I have made some changes. The changes include:

Refactored code for Body.js.
Separating the first container into another file. This change includes creating another file for styling named FirstContainerStyle.js. Then import the style into FirstContainer.js. After making the first container, I have exported it to be able to use it in Body.js.
Deleted bodyStyles.js since the file is not being used.
I have renamed materialtheme.js to materialTheme.js because it looks more conventional I guess. I am just following some of the naming conventions. 😐
Added responsiveFontSizes() in materialTheme.js. I'm not sure if I added it correctly, more info about it here (https://material-ui.com/customization/typography/).
In App.js, I renamed import { Theme } from '../../theme-style/materialtheme' to import { Theme } from '../../theme-style/materialTheme'.
In Body.js, I have imported FirstContainer.js. I have added <section> not sure if it is SEO friendly, I am following Semantic HTML. I have deleted classes={classes} on <TrustBadgeContainer> because I am not really sure what it does, let me know if you have any reasons for that I can always add it back.
Checked, my branch is up to date.

For second container, I have made some changes to it:

Add illustration to the container.
Separate secondContainer into a component then import to Body.js.
Use vh and vw. Remove ch.

For first container, I have made the following change:

Use vh and vw. Remove ch.


Frontend - Set up the boilerplate for the Create Dataset Form

Overview of the Feature Request
Set up the boilerplate for the Create Dataset Form. This is only the UI, so no API connected
Features:

It will only contain the Dataset title field
The Save Button should validate the inputs and show the validation error if necessary.
It should have the logic for calling the create use case if the title is valid and redirecting to the dataset page afterwards.

Mock

What kind of user is the feature intended for?
Logged in users
What inspired the request?
Frontend meeting discussion about the next user workflows that could extend the SPA to cover more features horizontally without too much detail.
What existing behavior do you want changed?
None
Any brand new behavior do you want to add to Dataverse?
No
Any open or closed issues related to this feature request?

@MellyGray, can you assign this to me?

@M27Mangan you should have permissions to do it yourself. Please contact Ceilyn so she can add you to the dataverse-dev team on Github
Then, please follow this workflow to assign yourself the issue:

Notify Ceilyin about the extra points for the sprint
In the projects section of this issue, go to Dataverse_Global_Backlog and move the issue to the Clear of the Backlog column
In the projects section of this issue, add a new project [IQSS/dataverse]https://github.com/orgs/IQSS/projects/2#card-91048600 and move the issue to the This Sprint column
Assign yourself
Move the issue to the In Progress column of the iqss/dataverse project once you start working on it

I could do all the steps myself but I think is better if we ensure that you have the permissions to do it by yourself.
Let me know if have any questions!

I have no idea if this will be helpful or not but 7 (!) years ago @raprasad came up with a proof of concept at https://github.com/IQSS/json-schema-test ... "JSON Editor takes a JSON Schema and uses it to generate an HTML form" according to the tool he used.
We now have an (unmerged) PR where we are adding a JSON Schema for a dataset:

https://github.com/IQSS/dataverse/pull/10109

Please ignore me if this is all just crazy talk! 😜

@MellyGray - Is there any business logic for what a "Valid" title should be? Or simply that the Title field contains a value? Do you know what file fragment on the original dataverse repo I should look at?

I have no idea if this will be helpful or not but 7 (!) years ago @raprasad came up with a proof of concept at https://github.com/IQSS/json-schema-test ... "JSON Editor takes a JSON Schema and uses it to generate an HTML form" according to the tool he used.
We now have an (unmerged) PR where we are adding a JSON Schema for a dataset:

JSON Schema creator and validator dataverse#10109

Please ignore me if this is all just crazy talk! 😜

Unfortunately HTML isn't really applicable for the SPA, but I appreciate you thinking of me :)

@MellyGray - Is there any business logic for what a "Valid" title should be? Or simply that the Title field contains a value? Do you know what file fragment on the original dataverse repo I should look at?

Hi @M27Mangan, this is the first issue in the SPA for migrating a form. As part of the scope, we need to figure out the best way to migrate validations from the original dataverse repo. To understand how the title is validated, please check the dataverse repo's original JSF code and its interaction with the backend.
If you discover that the validation in the JSF code is tied to the backend without a corresponding API endpoint for the logic, please make a note of it. Feel free to comment in Slack if you believe extending the API might be necessary to implement this feature.

If you pass an empty string for a title, you get this error:
{
"status": "ERROR",
"message": "Validation Failed: Title is required. (Invalid value:edu.harvard.iq.dataverse.DatasetField[ id=null ]).java.util.stream.ReferencePipeline$3@55407b76"
}
(Yes, what a weird error.)
It seems like a single character is allowed. I tried "z".
I ran this:
mvn test -Dtest=DatasetsIT#testCreateDataset

after editing this file:
scripts/search/tests/data/dataset-finch1.json

Generally speaking we use Bean Validation: https://www.youtube.com/watch?v=xg9A3q-fRyo

Must be they took it down. I will figure something out!

We now have an (unmerged) PR where we are adding a JSON Schema for a dataset

Some more details from the frontend meeting this morning:

Use JSON Schema from https://github.com/IQSS/dataverse/pull/10109 ?

It will tell you which fields are required per collection.
There is also a static JSON Schema file for the generic out-of-the-box case of five required fields for a dataset. See https://dataverse-guide--10109.org.readthedocs.build/en/10109/api/native-api.html#retrieve-a-dataset-json-schema-for-a-collection


ECDSA-SECP256R1 signature failure with openssl

Hi,
I'm getting issue while using EC/ECDSA certificate generation with TPM-PKCS11 and signing with openssl
TPM generated key
    Type: Private key (EC/ECDSA-SECP256R1)

Label: greenkey
Flags: CKA_NEVER_EXTRACTABLE; CKA_SENSITIVE;
ID: 33:64:33:31:31:31:38:33:66:61:30:64:65:38:66:65

RootCA generated by openssl for verifying TPM generated Device Certficate
Referred Section -<IP_ADDRESS> the secp256r1 curve was referred to as prime256v1:
openssl ecparam -name prime256v1 -genkey -noout -out rootCA.key

Getting Signature check failure
        openssl x509 -req -in deviceCert.csr -CA rootCA.pem -CAkey rootCA.key -CAcreateserial -out deviceCert.pem -days 500 -sha256

failed:Signature did not match the certificate request
`I have checked with
`openssl ecparam -list_curves
…
secp192k1 : SECG curve over a 192 bit prime field
secp224k1 : SECG curve over a 224 bit prime field
secp224r1 : NIST/SECG curve over a 224 bit prime field
secp256k1 : SECG curve over a 256 bit prime field
secp384r1 : NIST/SECG curve over a 384 bit prime field
secp521r1 : NIST/SECG curve over a 521 bit prime field
…

“secp256k1” is supported in openssl but not “secp256r1”. The later is standardized
and required by tpm2-pkcs11 as it supports RSA 2048-bit keys and ECDSA P-256 keys.
Is it not supported in OpenSSL 1.1.1b ? Why “secp256k1”
instead of “secp256r1”?
help will be appreciated.
Regards,
kaushendra sah

secp256r1 is  supported. It is listed  under the -list_curves output under the alias prime256v1.

Hi mattcaswell,
I agree with you and i have already mentioned it that i have followed
openssl ecparam -name prime256v1 -genkey -noout -out rootCA.key
To generate ecdsa-secp256r1 key using openssl Section <IP_ADDRESS>
But its not able to sign properly with TPM2-Pkcs11 generated ECDSA-certificate(deviceCert.csr)

Type: Private key (EC/ECDSA-SECP256R1)
Label: greenkey
Flags: CKA_NEVER_EXTRACTABLE; CKA_SENSITIVE;
ID: 33:64:33:31:31:31:38:33:66:61:30:64:65:38:66:65`

And I'm getting signature check failure while signing

openssl x509 -req -in deviceCert.csr -CA rootCA.pem -CAkey rootCA.key -CAcreateserial -out deviceCert.pem -days 500 -sha256
Signature did not match the certificate request

While everything works fine if i used RSA-2048 algorithm.
It will be helpful ,if you let me understand the case of failure of my scenario.
Regards,
kaushendra

Hi @mattcaswell
It will be helpful if you provide a quick respone into this as i'm on Bridge to implement this
Thanks,
kaushendra

Unfortunately I don't know the answer.

Marking as inactive, to be closed at the end of 3.4 dev barring further input


Should we embed helm directly to avoid depending on helm client to reduce one more install?

Right now users of our module will need to install:

kubectl
helm client
kubergrunt

Can we embed the helm client into kubergrunt to drop one more tool?

Helm features are removed, so this is no longer relevant.


new function advise

any possible if a word is in select, when open CTRL+R or CTRL+SHIFT+R,
auto paste is in the window,

in this version i have to copy and CTRL+R and paste then click

Good suggestion. :+1: I'll look into adding it.


⚠ ClamAV has degraded performance

In 3565230, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 445 ms

Resolved: ClamAV performance has improved in 7deb745 after 5 minutes.


link component

Allows you to specify web links within Unity.

@caseyyee when you get a chance, can you open a PR (even if it's a WIP) for https://github.com/caseyyee/unity-webvr-export/tree/links? thanks!

Now that @cvan has landed inbound links with https://github.com/mozilla/unity-webvr-export/commit/b13328929d0bcca1976a297396b05fac483da310, we'll need a component that makes it easy to create links within unity.


Two items heating

I have an underfloor system where I am opening a valve with your dual smart thermostat. I want also to switch at the same time the pump on. How can I add two (or more) items to the string?
Hope you can help me, thank you.
Example of what I have. I want to add       switch.1_kinderkamer_cv3 to the heater:
climate:

platform: dual_smart_thermostat
name: Zolder
heater:
switch.1_kinderkamer_cv4
target_sensor:
sensor.lumi_lumi_weather_0f08e207_temperature
min_temp: 15
max_temp: 22.5
ac_mode: false
target_temp: 19
target_temp_high: 26
target_temp_low: 23
hot_tolerance: 0.5
min_cycle_duration:
seconds: 10
keep_alive:
minutes: 3
initial_hvac_mode: "off"
precision: 0.1

I would create an automation. I do it like that in my system (I have 4 zones)


Future of this project

I was wondering if you still have time to maintain this project.
There seems to be several forks (@art103, @kohrar ,..) which are moving it forward by it's own way.
Maybe it would be better to unite, choose a new maintainer and keep all the development there. I see some new features there, I would like to add my own but cannot decide where to contribute.
What do you think?

It seems OpenDPS is no longer relevant(for example no DPS8005 support). There are other firmware that are actively developed. for example https://profimaxblog.ru/whats-new-in-firmware-4-0/

It seems OpenDPS is no longer relevant(for example no DPS8005 support). There are other firmware that are actively developed. for example https://profimaxblog.ru/whats-new-in-firmware-4-0/

Thanks, but that doesn't look like opensource to me...

the profimax fw looks interesting, but since there is opensource fw, that we can change and customize - other close source fw is much much less interesting to me, at least.
I dont think this is at all 'irrelevant'.  I'm sorry I didn't see this years ago when it first came out ;)

That firmware has some interesting features. For me, OpenDPS is good enough for the few DPS modules that I still have. I don't intend on getting more of these units and I haven't been keeping up with any of the newer offerings.
However, it would be nice to see these pull requests get merged in. If I remember correctly, memory is sort of a constraining factor at the moment, so some effort would be required to make everything fit or have the make file include/exclude features cleanly.

Well, sadly I do not have much time to maintain OpenDPS anymore. If anyone creates a fork for maintenance I would be happy to refer to it.

Any update?

Are you still interested in the project?
@Xenoamor, @kohrar, @frederikvs, @tzarc, @danielkucera, @lukedempsey, @polihedron, @JackNewman12, @jimmyw, @goosenphil, @gojimmypi, @MarcusLindemann, @martinstep, @ilium007, @TheAssassin, @X-Ryl669, @m-kozlowski, @mabels, @Cabalist, @atx, @jenda122, @Spudmn, @cortices, @bjerrep

There's no need to spam everyone. As kanflo said, we don't have much time. You're free to fork and take on this project.

@kohrar Sorry, I didn't mean any harm... Just sad about this project, it's the only open-source digital power supply firmware in the world.

Maybe we could try crowdfunding, like Patreon?

Still, with every new message, over 24 people, many completely unrelated to the project, receive messages. You knew this was going to happen.
I hope you learned your lesson. While typing, you posted even more spam. This is considered extremely bad behavior in open-source communities. Just because you're unhappy with any detail (for whatever reason, maybe the firmware just works for everyone involved so far...) doesn't justify spam like this.
@kanflo please lock the issue or ban @violavon, either stops the spam.

Sorry (really).

I think @violavon is a "young padawan" (joined a week ago) who learnt a lesson. Will close the issue though.

I have my own fork and I am going to post it to my own github area, shortly.  it was a 'logn time ago' when I first did some mods and now that some time has gone by, I might have forgotten a few things.  but its still my go-to open source low-cost programmable psu.

hey, i know nothing about programming language or anything, but i have a question, is it possible to use a bugger screen on the original dps software?
thanks!

@justincr83

hey, i know nothing about programming language or anything, but i have a question, is it possible to use a bugger screen on the original dps software? thanks!

it's not considered polite to post unrelated questions on an old thread like this -- it means every prior participant gets notifications.
But in answer, no, you absolutely cannot just use a bigger screen on this or any other DPS software.


Provide a mechanism to revive the VDC controller in case the node it runs on fails

FR linked to the bug described in https://github.com/threefoldtech/js-sdk/issues/2965 .
When a user has reserved a VDC he paid TFTs in advance, plus he has workload running.
Putting the responsibility entirely with the farmer doesn't work as an end user has paid the VDC provider. So VDC provider should put a mechanism to rebuild the VDC controller in case the node it was running on was down. Or refund the user.

duplicate of #2989


AG import should extract sample ids from filenames if given regex

The file paths for objects often have a specimen/sample id in them - according to the rules of the lab that did the sequencing. We should allow the dataset config to define a regex (i.e. a capture group) that if matches defines the specimen id.

VCGS samples (for instance) have a pattern 00W000000 that could easily be extracted. Our 10G datasets have a pattern of HG00000 that could also be extracted. That would allow the UI to at least display something for specimen id.

Adding to this I suppose this also could add the DatasetCase Id regex configurable from the config file.
Currently this is the FamilyId gotten regex from FAM\d+ from the filename as well.

Yes its possible we could make all the magic strings of the algorithm be configurable from the dataset config..


Wall time and trusted time

When using ACE/OAuth for authentication, the tokens (CWTs) typically carry expiry information. Currently, we don't have wall time, let alone trusted wall time.
A document I'm working on in T2TRG (raytime) describes what is about a minimal thing a device can do, but it'd still be about keeping some time. (In essence, it's about just keeping a lower bound of time, bumping it guided by seen tokens, and pushing it along while the device has a timer running).
So, what do we need in general, what do we want, and what should be default?

Do we expect that securely networked devices are used in a mode that can do with no time at all?

If yes, how should this be made opt-in so that we are still secure by default (with "secure" following general guidance on not granting infinitely long-lived access)?

Do we want to offer wall time as an OS-wide service? How many of them / at which trust levels?

Some secure time source authorized by the owner? The AS itself?
What precisions do we expect?
Which reliability v. security trade-offs are acceptable for which clock?
Can we even protect high precision time sources? (GNSS such as GPS can give us "perfect" time without authentication, AS provided time is ultimately trusted but goes through a full network round trip and might include extra times when the AS is heavily guarded)
How does an application select "the" time to use, eg. for storing timestamps of sensor values?

Do we want to check token validity against a wall-time-ish service, or do we better split those, let the token security parts do their own weird raytime thing, and trust the time multiplexer to keep things efficient hardware-wise?

One approach I start favoring is that the OS manages something like cumulative experienced-time. This is a time counter on some constant scale, and it is monotonous across reboots. As this would be backed by flash writes that consume power and wear down flash, it may make sense to model this as an interval (guaranteed-monotonous, best-effort-latest), the monotony only applies to the lower bound, but the application querying time can request this interval to be arbitrarily small (but requesting a small interval may force the OS to do a flash write, so applications please use lose bounds), or may contribute to the system wide policy on how large that window may become. (Early guesses are that when the time is requested, an application might ask for a maximum 10-minute window, which would create a flash write every 10 minutes while under load, and a maximum of 1-day when idle).
As a monotonous counter, any adjustments for clock skew would need to be applied at run time, but I don't expect precision requirements above what even built-in oscillators can provide. The value would only be allowed to reset if all credentials used with the clock are erased.
Then, the storage of an authorization server (especially when different ASes are around) can express their AS's time scale as an offset from the cumulative uptime, and the flash writes are decoupled from the individual AS's time lines.
Rough data structure:

Constant:

Unit of time (eg. 1s)
Confidence intervals for the conversion between ticks and SI units

in RAM or peripherals: Time since last stored (this value overflowing is rounds for a system reset, as apparently the time update task has not completed in time)
in RAM, if we want "uptime": Cumulative counter when the system came up
in configuration ROM:

Stored cumulative uptime
For each AS we are RS for (or other peer with which we want to have time base freshness): Maximum difference between AS time and cumulative uptime (adjusted for the fastest expected clock tick rate)

Calculated: Cumulative uptime is stored cumulative uptime + time since last stored

If "uptime" is a deliverable, we'll want to have the confidence intervals (at least one-sided), so that uptime can be reported as the most likely value. If all users are like the AS clocks that can err on the side of caution (there, accepting certificates/tokens for a few minutes longer is tolerated, but rejecting a short-lived token because we think we're ahead of time by a few minutes breaks things), the confidence intervals may just as well be baked into the tick-to-time conversion factor.


[ares] Initial integration of pma_malloc

This vendors pma_malloc from @ashelkovnykov and hooks it up to our event lifecycle.  This works for the small pills, but it doesn't work for the full azimuth pill because that needs to write 3MB of data in one event, and the hard-coded dirty page limit of 163 only allows ~650KB.  It's unclear what the right solution to this is -- I suppose we should convert the page directory to a B+ tree, otherwise you would need a lot more double-buffered metadata pages, or another solution entirely.
This includes several fixes in pma_malloc, which should be reviewed carefully (and probably synchronously).  The full PR diff is unhelpful for these, but this sub-diff should work.
This puts pma_malloc alongside the existing "just jam and double-buffer" persistence mechanism and puts them both behind a Snapshot trait.  It's unclear if this will continue to be useful, but it's convenient for now.  You can switch between them in serf.rs by changing one line.
This extracts arvo to the PMA after every event (though only syncs when the king requests it).  This isn't strictly required, but in the future it will make it easier to recover from errors and add parallelism, and even now it reduces snapshot latency.
Since we can't write to pages after they've been synced except by mallocing again, we mug every noun immediately before it goes into the PMA.  This shouldn't be expensive, we already do this in vere.
However, it's unclear how unifying equality can work on two noun references in the PMA.  If they turn out to be equal, we should rewrite one to the other, but this requires changing a page which may not be dirty and therefore is likely mmap'd PROT_READ.  Two solutions that come to mind are: always mmap PROT_READ | PROT_WRITE, or supply an interface function for marking a page as dirty (and therefore copying the page behind the scenes).
Finally, there is not yet a garbage collector for the PMA.  I'm not sure what algorithm we should prefer -- copying is likely the easiest and implicitly compacts, though mark-and-sweep may work out better for larger arenas.

@philipcmonk I'm out today but it might be worth syncing this evening anyway.

To be clear, the first goal of this work was to determine what kind of an impact integrating pma_malloc would have on the serf architecture.  I want to drive toward error handling a nock computation by running it in a thread and killing it, and you need to be copying out of the stack between each event to do that properly, so I wanted at least a mock of a PMA.  I figured I'd play around with pma_malloc and stop if I ran into an individual problem I couldn't solve in an hour or two, and this is how far I got.  Total time investment in this code is only 2-3 half-days, which is completely worth it just for how edifying it has been for me.
With the understanding I now have of pma_malloc, It would be easy to create a mock PMA with system malloc, and that would let me continue on to look at error handling.  So this PR isn't blocking for me.
The bugs I fixed in pma_malloc are mostly small and simple -- forgot to intialize a variable, etc.  I knew development had been interrupted, so that wasn't a surprise.  I did want to know if there were deeper issues that hadn't been considered, and the easiest way for me to learn that kind of thing is dig into the code.  The answer seems to be no: once those small bugs were fixed, it mostly just works, except those issues you guys have already identified and planned solutions for.
The changes I made to pma_malloc beyond bug fixes are:

Added pma_in_arena(void*) so the copying code knows whether it needs to copy a noun out.
Added root to the metadata to record where the most recent root is, which will generally be the arvo state, bytecode cache, and anything else that needs to be persisted.  You need this so that when you load, you know where to get started.  There are a few possible variations, for example we could put the event number and epoch number inside the root as well.
Made pma_load return the epoch number, event number, and root.  Right now it returns these as a struct, but out parameters plus an error code return could be preferable.

I don't have an opinion on the location of the pma_malloc code, and I'm happy to port these changes wherever.  It can certainly go into a c/ directory, though I'm not sure programming languge is the best top-level directory scheme.  It's also easy to keep it in a separate repo, though I believe @eamsden would object to a submodule.
We use a lot of cells, and 650KB is about 20,000 cells.  Both my test pill and many real-life events will generate more than 20,000 cells in a single event.  For example, if you save an 800 line hoon file as a tape, even just in a dojo variable, you will generate more than 20,000 cells.  However, if the goal is to move to B+ trees, then we don't need to consider this anymore, and I can work around the limit if I need to for any testing.

We use a lot of cells, and 650KB is about 20,000 cells. Both my test pill and many real-life events will generate more than 20,000 cells in a single event. For example, if you save an 800 line hoon file as a tape, even just in a dojo variable, you will generate more than 20,000 cells. However, if the goal is to move to B+ trees, then we don't need to consider this anymore, and I can work around the limit if I need to for any testing.

To Alex's point, the limit is 164 possibly multi-page entries, not 164 pages. The idea is that the copier should count up how much space it needs (rather like the jam implementation in vere) and then malloc a single chunk of space.
But yes, this limit will be entirely dropped with a B+ tree page index. This will also allow us to run the NockStack inside the PMA and store the root by resetting the NockStack to be a single frame with the roots in its locals.

Proposal for top-level directory schema:
silt - for glue code to the big ball of mud (c/rust/other terran code)
rock - for the crust around the diamond (runtime-level hoon)
</bikeshed>

To Alex's point, the limit is 164 possibly multi-page entries, not 164 pages. The idea is that the copier should count up how much space it needs (rather like the jam implementation in vere) and then malloc a single chunk of space.

I'm not sure I understand this idea.  If you do one big malloc, you aren't able to free nouns individually, right?  And you need to do that for mark-and-sweep gc.  Do you construct entire pages of each size of allocation, or something like that?

This will also allow us to run the NockStack inside the PMA and store the root by resetting the NockStack to be a single frame with the roots in its locals.

I still don't really understand this, or why it's helpful to run the NockStack inside the PMA.

To Alex's point, the limit is 164 possibly multi-page entries, not 164 pages. The idea is that the copier should count up how much space it needs (rather like the jam implementation in vere) and then malloc a single chunk of space.

I'm not sure I understand this idea. If you do one big malloc, you aren't able to free nouns individually, right? And you need to do that for mark-and-sweep gc. Do you construct entire pages of each size of allocation, or something like that?

Presumably you're not mallocing and freeing in the same event. The dirty page cache isn't the limit for the arena, it's just the limit for pages that need to be written in the next snapshot.
@ashelkovnykov am I remembering this right?

This will also allow us to run the NockStack inside the PMA and store the root by resetting the NockStack to be a single frame with the roots in its locals.

I still don't really understand this, or why it's helpful to run the NockStack inside the PMA.

Running the NockStack inside the PMA decouples computation memory limits from available system RAM and swap by treating the PMA backing store as swap. It also lets us store a custom struct (with the Preserve trait) as a snapshot root instead of needing to use space in the snapshot metadata to for this.
The idea is that we won't do a snapshot in the middle of an event, so the event computation can just run in the arena with stack pages mapped to disk, but never written to disk unless the kernel decides to evict them. When we're done with an event computation, we reset the stack and then write a struct with references to a noun (Arvo) and a bytecode cache into a local in the top frame of the newly-reset stack. We know where this top frame is, so we can treat that local as the root when we garbage-collect the PMA. When we start a new event computation we just grab arvo and the bytecode cache from the local slot in that stack frame and commence the event computation.

The dirty page limit is 164 [multi-page allocations/frees] + [pages touched by shared-page allocations/frees].
You're both correct, in different ways. @philipcmonk  is correct that anything we pma_malloc as a single chunk needs to be freed as a single chunk as well, regardless of when this happens in the future. @eamsden is correct that there's optimizations on the table for how to work around this: (e.g. even if we read a file as a tape, we can pre-compute how much space it needs).
However, I recall that in a conversation we had with Ted, Ed brought up an idea for how it's possible to work around this based on some guarantees about what we're storing/how we're using it. @eamsden Does this sound familiar?
Regardless, B+ Tree page directory is the future.
re: NockStack -
Please correct me @eamsden if this is a bad way to visualize it, but the way I picture it is that it's like the PMA is one giant Vere road, but at the end of an event it's always left with only one thing in the stack: a pointer to Arvo root.

I think the right thing to do here is:

I'll remove pma_malloc from this PR and transfer the diffs against it to a PR to ashelkovnykov/pma_malloc
I'll delete snapshot/pma.rs.  It will be available in the git history if we want to refer to it when we actually integrate pma_malloc
I'll preserve the changes to abstract over the snapshot mechanism, to make it easier to switch between different options during development.
I may go ahead and implement a trivial outside-the-stack arena so that we can look at running events inside killable threads.  That arena will either be system malloc or just a separate NockStack (either of which will leak, but that's fine for scaffolding)

I did the first three of those, and will reserve the fourth for a later PR.  I also merged status, fixing clippy errors, etc.  This is ready for review.


Shapley Flow implementation?

Hi @slundberg
Having found the "Shapley Flow: A Graph-based Approach to Interpreting Model Predictions" paper you wrote with 2 co-authors, I wonder if it's planned to implement it in shap library in a foreseeable future?
Keep the good works!

Does Shapley Flow aim this issue?

Predictive and Causal Implications of using Shapley Value
for Model Interpretation https://arxiv.org/pdf/2008.05052.pdf

Hi @slundberg,
Has there been any updates on an open-source implementation of Shap Flow?
Also, I am curious to know, would Shap Flow be applicable to a 'system of ML models'. In the paper, each node corresponds to a particular feature, but how would one go about providing explainability to a system where the nodes themselves may be individual ML models. In such a scenario, a human in the loop may want to decompose an explanation based on the final output of the system (conditioned on the final model's immediate inputs) into an explanation conditioned on the inputs to those sub-models whose outputs are fed into the final model. Do you know if there any related papers on this sort of topic?
Best regards,


Improve Documentation Resources

After documenting the major use case (actually -- all of them) extension methods, there's a few items to do on the wiki.
New Content:

[x] API Overview:

[x] ConfigurationContainer

[x] ConfigurationProfiles

[x] TypeConfiguration
[x] MemberConfiguration
[x] ISerializer
[x] IElement
[x] IContents
[x] IConverter
[x] ISerializerExtension

[x] Add basic extension to Example Scenarios.

Existing Content:

[x] Add TL;DR to README
[x] Wiki Navigation Redo
[x] Flesh out wiki topic about Configuration API: https://github.com/ExtendedXmlSerializer/ExtendedXmlSerializer/wiki/Configuration-API
[x] Update custom serialization example scenario to use v2 registration.

Whew.  So glad to be done with this. :P

Our new wiki:
https://github.com/ExtendedXmlSerializer/home/wiki


[Update Request]: Google.Chrome hash mishmatch

What type of update are you requesting?
A new version of an existing package
Current Package Identifier
Google.Chrome
Package Version
114.0.5735.134
Please describe the changes you would like to see
The manifest is hardcoded to always update to the latest version.

https://dl.google.com/dl/chrome/install/googlechromestandaloneenterprise64.msi

Since the update last week we have moved from version 114.0.5735.110 to 114.0.5735.114 and now have a hash mismatch, that can't be ignored while running as Admin or System.
It would be preferable if we can have a few manifest versions, with static deployment URL to avoid this in the future, if possable.

@ChrisWarrenCodux Hi! Please vote on this three issues if you can https://github.com/microsoft/winget-cli/discussions/3313#discussioncomment-6135375

I am also facing same issue.


 Here I am proposing an API for training and using estimators. I haven't thought through how this may extend to other stateful APIs, but perhaps there will be a natural extension.
First, sklearn essentially builds everything around fit and predict. So you can basically always depend on:
model = LinearRegression()
model.fit(X, y)

model.predict(X_test)

When unpickling trained models you can pretty much depend on this being the API as well:
model = pickle.load(...)
model.predict(...)

Obviously we can't take the OO approach which modifies internal state. Instead, what we can do is build estimators from data structures. This is the same approach Axon takes. So essentially you will have a Scholar struct:
defstruct :estimator, :state, :name, :id

Where :estimator is the model to run and :state is a unique state which is associated with the estimator. For :linear_regression this might be a map of coefficients and intercepts. For other models it will be different. Regardless, state will be unique to whatever the :estimator is.
Scholar will then expose 2 functions: predict and fit. Both of which delegate training and prediction logic to an internal compiler based on the estimator. Now, we can construct estimators from constructors:
model1 = Scholar.linear_regression(...)
model2 = Scholar.svm(...)

And we can introduce some interesting combinators of estimators for pipelines and ensembles.
Finally, I don't believe we should restrict ourselves to only models which can be implemented in pure Nx. For each model we should make a best faith effort to ensure it's efficiently written (e.g. delegate to Nx as much as possible); however, I believe there is a benefit to having models available despite maybe not being pure Nx. Applying the models is important to learning, so just having some parity with sklearn would be huge for beginners. We can worry about optimizing implementations with NIFs or other means later.
Once we finalize on an API I will go through and create a functionality checklist which can guide contributions :)

We have two options:

Have a single shared struct, as you described above

Make Scholar a protocol with a predict function. So you do this:
model = Scholar.SVM.fit(...)
Scholar.predict(model, data)

I am more inclined towards the second because it will give us more flexibility and we don't need to tie everything into a single struct. WDYT?

We also need to answer how this will work with Nx.Container and pickling. Maybe we should expand Nx.Container to have deserialize and serialize functions too. WDYT @seanmor5?

I like the protocol route. I think we should hold off on adding special serialization for containers right now though and instead if we need scholar specific serialization we can add it.
With the protocol in mind I will make a list of estimators to reach some parity with sklearn. The API surface will be pretty large

I agree, I like the protocol idea as well. It should make things easier for other common functions as well. I've been thinking about how Explorer will integrate with Scholar. Specifically things like sampling and train/test splits, but also ways to rapidly/simply get model information into tidy formats for evaluation and visualisation a la broom. A protocol should simplify integration.
@seanmor5 I'm curious about what you have in mind re: models that can't be implemented in pure Nx. Do you mean falling back to plain Elixir? Any models jumping out at you?

I like "train/predict" in terms of function names. I think it's clearer than fit/predict.

I agree with protocols as well because we can handle other kind of cases like unsupervised learning functions that does not take x/y as arguments.
model = Scholar.NearestNeighbors.train(samples)
kneighbors = Scholar.predict(model, data)


API error message content-type ignores Accept header

When I hit the comment limit using the API, the error messages are coming back as HTML. I am using the API directly from custom javascript.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>403 Forbidden</title>

Forbidden

3 direct responses to my-test-post

The request headers include Content-Type: application/json and Accept: application/json so the server should be responding with only JSON. A simple response like {"message": "3 direct responses to my-test-post"}  should allow clients to read the reason for the error.

Fixed by #488


feat: adding kube prometheus monitoring stack

This PR introduces a new monitoring setup, which primarily replaces our existing infrastructure setup. Instead of deploying everything via Pulumi, we utilize a different tool for setting up this part of the infrastructure configuration with a dedicated tool called kube-prometheus.
This middle-ground solution allows us to tweak most of the settings more easily and use built-in configuration options. For things that are not covered by the tool, we still depend on the Pulumi stack, such as the Traeffic ingress or any additional stuff that's easier to do via Pulumi.
Changes performed:

New tool added to the unchained monitoring setup
CI configured to apply the changes to our cluster after approval
Because kube-prometheus does not offer diff functionality similar to Pulumi, we depend on kubectl diff to preview the changes to be made to our stack

Closes #700

Sample diff run of the current state: https://app.circleci.com/pipelines/github/shapeshift/unchained/2654/workflows/38665915-3819-492a-83e2-1d2c696ce163/jobs/10249

to clarify, does the kube prometheus actually deploy grafana/loki/prometheus, or just bundle grafana dashboard views and different alerts?

to clarify, does the kube prometheus actually deploy grafana/loki/prometheus, or just bundle grafana dashboard views and different alerts?

It's the full stack. Prometheus operator, node exporter, grafana, alert manager plus some nice default dashboards and alerts


Play url

Hello, maybe this does not go here, but I really need help, I am looking for how to execute a url with headers for the chrome cast, and I think this library can help me, I already saw how I can send local videos to my chrome cast, it works fine , but now I want to send a url with headers
It's possible? if so, how? It would be very helpful if you could give me a hint, thank you very much

You have to do it manually, there is a class in Cast SDK called NetworkRequestInfo that can help you pass headers.

This class is for the web_receiver, it is not for android, I have to upload html code to a web page, buy the service in Google Cast SDK Developer Console for 5 dollars, and then publish the page to connect it with the cast, I have tried everything to modify the headers, but it does not work, I have left that and I have opted for the option that the cell phone itself is a proxy, that is what https://play.google.com/store/apps/details?id=com does. instantbits.cast.webvideo & hl = es_PE & gl = US
You can see the following thread in discussion here:
https://github.com/warren-bank/Android-WebCast/issues/6
I would like to do the same, I just don't know where to start yet, if I had an example web_receiver code where you can add the headers it would be very helpful

I am not much aware of things going on with cast SDK. I'm sorry I can't halp you much!


CORS disabled on states end point

The Access-Control-Allow-Origin header isn't being sent from the /api/states end point.
The /api/us endpoint still works fine.

I'm seeing it still. Can you give any further details that would help reproduce the issue?

From a page running on localhost I get the CORS error. It worked all day until just now.
The attached screenshots show the us endpoint responding with the right access-control-allow-origin: * header and the states endpoint responding without it.

Looks like you're getting a 500 error from /api/states.json. The quick fix is to remove the .json at the end of the url. Try /api/states instead. I'll figure out why there's a 500 error is happening.

I changed to /api/states and everything works again. Thanks!
Nevertheless, /api/states.json was working literally all day until just now and /api/us.json is still working. I'll close the ticket but there is some inconsistent behavior in the endpoints.


Fix source path for coverage.

Coverage reports on codecov are currently broken - this is an attempt to fix that.

This doesn't work - coverage is still not being processed by codecov. I can't see what the issue is (the report is being sent to their servers) and have emailed them for help.

@craigloftus I figured out the issue in the end - you should see codecov reporting something on this PR. It will say no base coverage because master currently has no coverage report.


Prevent crash from unsupported URI downloads

As discussed here, here's a try/catch implementation to mitigate blob crashes, with the block restricted to the call site of the exception. Here's a video of the current behaviour. It might make sense to send a toast about the download being unsupported. Please let me know if you feel like that's desirable.
https://user-images.githubusercontent.com/8260207/149483121-5a31a03e-7d00-4b31-a9d2-a01249c5997b.mp4

@TheAlmightyBob - Thanks for your review. While I agree that this should be the preferred way to handle the error, IMHO the addition of a new API should be handled in a separate issue. I have created one here. I am happy to help with that, however, I don't have as much context around non-Android platforms.
This PR simply aims to achieve parity with the behaviour on iOS and mitigates an easily avoidable app crash which many users are suffering from. The solution proposed in this PR was very close to getting merged in the previous review, only barring the scope of the try/catch here. There has also been https://github.com/react-native-webview/react-native-webview/pull/2065 which also closed due to inactivity.
As highlighted in the previous PR, a lot of users have resorted to patching the library with this exact same fix (or some variant of it), as the primary concern seems to be mitigating crashes on Android. I am not sure what your stance is on merging this solution, but if the maintainers feel like the addition of onDownloadError is a blocker for releasing this fix, we will sadly have to resort to patching as well.

I don't have as much context around non-Android platforms

I think the event could be documented as Android-only, at least for now. Or do you mean that you don't have much context with the React Native side?
Thanks for the iOS example. That at least has the yellowbox warning to communicate the problem to developers, rather than a silent failure. Although, to the previous point, I suppose that if it is showing a yellowbox warning that suggests there is an error that could theoretically also be raised on iOS via event... (I'm actually rather curious how that warning is being shown... I don't see any code in react-native-webview that would do it)
I'm aware of the history of this issue and would also like to see it addressed, I'm just a bit wary of hiding information from developers that could help them fix the root cause.
Using the Android logging class to log a warning (and passing the exception to it) seems like it would at least be better than using println/printStackTrace, no? (I realize onDownloadStartcurrently uses that pattern, but it's the only place inRNCWebViewManager` that does so I'm not sure it's the example to follow)
(also I'm sorry I didn't start this conversation as a review comment in the code so this could be a thread...)

I'm actually rather curious how that warning is being shown... I don't see any code in react-native-webview that would do it

I can't point out the exact callsite for now, because I'm fighting with XCode 13 incompatibilities, but it definitely looks like the yellow box is coming from react-native-webview. The iOS code seems to be using the RCTLogWarn API in multiple places, allowing it to create a yellow box from native. I did not have any userland code doing console.warns above example - it was exactly the same as the one I ran on Android.
<WebView
  source={{
    uri: 'https://codepen.io/vidhill/pen/bNPEmX'
  }}
  automaticallyAdjustContentInsets={false}
/>

Here is a longer stacktrace for the iOS yellowbox:

If we want to do do yellow boxes on Android, we could use com.facebook.react.util.RNLog. However, this is only available starting react-native 0.63 and adding it might break compatibility for users on older versions. I'm not entirely sure how we're enforcing React Native versions in this project.
Aside: I gave some further thought to adding an onDownloadError. Upon reading @avinashsahoo's comment from here, it looks like onShouldStartLoadWithRequest is only called during page navigation and not on file downloads (contrary to what is described in the comment for iOS). Maybe that would be a better way to delegate choice to the user.

I thought about this more and I think you made a reasonable point for why the error event, while useful, does not strictly need to be part of this PR. I think I'm good with this if the logging switches to use the Android logger (unless you have an argument for why it shouldn't?).

The iOS code seems to be using the RCTLogWarn API in multiple places

Yeah, but I looked through those and none of them seemed related... I'm not blocking this PR on that question though, I'm just curious.

If we want to do do yellow boxes on Android, we could use com.facebook.react.util.RNLog. However, this is only available starting react-native 0.63

Okay, that seems like a decent reason to hold off for now.

Aside: I gave some further thought to adding an onDownloadError. Upon reading @avinashsahoo's comment from here, it looks like onShouldStartLoadWithRequest is only called during page navigation and not on file downloads (contrary to what is described in the comment for iOS). Maybe that would be a better way to delegate choice to the user.

Interesting thought... I'm not sure if I'm quite following you though. "Delegating choice" seems like a different thing from "handling and reporting errors."

Interesting thought... I'm not sure if I'm quite following you though. "Delegating choice" seems like a different thing from "handling and reporting errors."

Yes, you're right. We shouldn't mix up the two.

onShouldStartLoadWithRequest - Here, I believe that the user should be able to prevent downloads too, depending on the URL in question. Currently, we don't allow this - the user can allow/disallow navigation, but not downloads.
onDownloadError - My concern is that this API might give users the impression that we're handling more than we really are (e.g failed downloads due to bad network). blob downloads not working seems like a limitation more than an error to me.

If I understand your comment correctly, it looks like I've managed to address most of your concerns around this PR. If that's not the case, please feel free to let me know.

onDownloadError - My concern is that this API might give users the impression that we're handling more than we really are (e.g failed downloads due to bad network). blob downloads not working seems like a limitation more than an error to me.

That's a fair concern about the name, but I still think the issue should be communicated in some way so that developers can handle it (e.g., fixing the website so it doesn't try to download via blob scheme, provide some friendly error to the end-user, etc). Perhaps there's a better name... #2091 used onDownloadUnsupportedUrl, but I worry that could have the opposite problem, that maybe there are other reasons that the download manager could throw an error?
(at this point though this conversation should probably be happening in #2335 rather than here...)

Thanks @karthikiyengar!


Builder API for op-node sequencer

adding unit tests to this would be great!

@avalonche I implemented the payload selection by its BlockValue

closes #7


Setting limits and requests for mdsd

Setting the values in the mdsd pod for QoS.  If left empty a best-effort policy is applied.  If defined then it can be either burstable or guaranteed.  This sets the values to burstable.  We need this setting applied to pass the upstream origin test suite.
Specific test:
"[Feature:Platform] Managed cluster should ensure control plane pods do not run in best-effort QoS [Suite:openshift/conformance/parallel]"

@jim-minter @JackQuincy Any ideas on the proper settings for this pod?  I uncommented the settings that were existing.  I attempted a higher CPU value (500m) as a test but received the following error:
<unknown>   Warning   FailedScheduling   pod/mdsd-ll7rf   0/6 nodes are available: 1 Insufficient cpu, 5 node(s) didn't match node selector.

fixes #324

Fixing formatting of resource.Quantity

@kwoodson, based on looking at a cluster I suggest the following values to start with
request
cpu 10m
memory 100Mi
limit
cpu 200m
mem 500Mi
rationale: the request values appear to be the approximately idle values; the limit values are a line in the sand.  I think 400Mi memory limit is too low.
Also, check the case - Mi, not mi.


FLP doesn't handle empty list of labels in certain cases

FLP has the problem that it produces metrics such as the following:
HELP pano_dns_rcode_total
TYPE pano_dns_rcode_total counter
pano_dns_rcode_total{rcode_name=""} 29944.01916207507
pano_dns_rcode_total{rcode_name="NOERROR"} 8147
pano_dns_rcode_total{rcode_name="NXDOMAIN"} 2865
pano_dns_rcode_total{rcode_name="SERVFAIL"} 26
The first entry with "" should not show up.
Here's a simple yaml config file where it does NOT happen:
temp.txt
Here's a more complex yaml file where it DOES happen:
pano-file-dns.txt
(gave the files .txt extensions because github didn't understand yaml files, oddly enough)
Here's a log file to drive it with:
dns-pano.log
(note the yaml files include the config file in a yaml subdirectory)

Hi @emnahum ,
I guess this was the reason for https://github.com/netobserv/flowlogs-pipeline/pull/460 , but as I commented in this PR, I don't think this is a good solution to evict records that have empty labels.
What about doing this exact same thing, but by configuration? Ie adding a filter rule to drop records when rcode_name is absent? cf https://github.com/netobserv/flowlogs-pipeline/blob/main/docs/api.md#transform-filter-api / remove_entry_if_doesnt_exist

I haven't try, but maybe something like that could work?
(adding two new stages, filter_dns and encode_prom_dns)
log-level: error
metricsSettings:
  port: 9102
  suppressGoMetrics: true
  prefix: pano_dns_
pipeline:
  - name: ingest_file
  - name: aggregate_values
    follows: ingest_file
  - name: encode_prom
    follows: aggregate_values
  - name: filter_dns
    follows: aggregate_values
  - name: encode_prom_dns
    follows: filter_dns
parameters:
  - name: ingest_file
    ingest:
      type: file_loop
      file:
        filename: logs/dns-pano.log
        decoder:
          type: json
  - name: aggregate_values
    extract:
      type: aggregates
      aggregates:
        rules:
        - name: aggr_rtt_avg
          operationType: avg
          operationKey: rtt
        - name: aggr_rtt_hist
          operationType: raw_values
          operationKey: rtt
        - name: qtype_count
          groupByKeys:
            - qtype_name
          operationType: count
          operationKey: qtype
        - name: query_count
          groupByKeys:
            - query
          operationType: count
          operationKey: query
        - name: rcode_count
          groupByKeys:
            - rcode_name
          operationType: count
          operationKey: rcode
  - name: encode_prom
    encode:
      type: prom
      prom:
        prefix: pano_dns_
        metrics:
        - name: query_count
          type: counter
        - name: query_total
          type: counter
          valueKey: recent_op_value
          labels:
           - query
        - name: qtype_total
          type: counter
          valueKey: recent_op_value
          labels:
            - qtype_name
        - name: rtt_histogram
          type: agg_histogram
          valueKey: recent_raw_values
          buckets:
           - 0.00001
           - 0.0001
           - 0.001
           - 0.01
           - 0.10
           - 1.00
        - name: rtt_avg
          type: gauge
          valueKey: recent_op_value
          filter: {key: name, value: aggr_rtt_avg}
  - name: filter_dns
    transform:
    - type: filter
      filter:
        rules:
        - input: rcode_name
          type: remove_entry_if_doesnt_exist
  - name: encode_prom_dns
    encode:
      type: prom
      prom:
        prefix: pano_dns_
        metrics:
        - name: rcode_total
          type: counter
          valueKey: recent_op_value
          labels:
            - rcode_name

OK, I managed to configure the equivalent to Kalman's patch.  You can close out this issue if you want.

@emnahum @KalmanMeth if you feel we could improve how to manage such cases, e.g. via easier configuration (more straightforward), we could keep it open, and it would be good to have a proposal.
Else I think we should close it.


Hide white screen doesn't work at all

Tried to uninstall and reinstall runelite and it's not working any possible fix to this?

I'm having the same issue.

Fix for the problem > uninstall ToB Light Up plugin and reset runelite


Adding information about updating package

Possible workaround for an error that shows while updating the package.
Category

[x] Content fix
[ ] New article

Related issues:

mentioned in #4322

What's in this Pull Request?
Suggesting additional content to handle updating versions

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

thx @shaipetel, appreciated. Sorry for the massive delay here.


add support for repeating texture

@urish thank you so much and sorry i didnt reply this soon.

@urish thank you so much for this and im so sorry i didnt reply back soon.


doc directory is cluterred by source files

In GitLab by @jbigot on Jul 26, 2021, 16:57

mentioned in commit b8259aeb759eb91bfb69924fe9a97bf5ddd66308

mentioned in commit 4dc9fa803c09c0706339044b67d1d6fbe4286851


x/mobile: Java to Go bindings crashes with  java.lang.UnsatisfiedLinkError

I have a sample Android app with Java to Go bindings, built using gomobile bind command. When i try to run this code on Nexus 5 (Android 6) it's always crashing with  java.lang.UnsatisfiedLinkError.../libgojni.so: has text relocations. I am not sure whether this is the right repo to report x/mobile issues. Reporting it here because i didn't find any option in golang/mobile
SDK Version
android {
    compileSdkVersion 23
    buildToolsVersion "23.0.1"

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 23
        versionCode 1
        versionName "1.0"
    }

Go bind gradle plugin
go version go1.5.1 darwin/amd64

plugins {
    id "org.golang.mobile.bind" version "0.2.2"
}

10-15 16:08:26.634 1632-1662/io.test.gopherandy I/OpenGLRenderer: Initialized EGL, version 1.4
10-15 16:08:28.242 1632-1632/io.test.gopherandy D/AndroidRuntime: Shutting down VM
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime: FATAL EXCEPTION: main
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime: Process: io.test.gopherandy, PID: 1632
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: /data/app/io.test.gopherandy-2/lib/arm/libgojni.so: has text relocations
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at java.lang.Runtime.loadLibrary(Runtime.java:372)
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at java.lang.System.loadLibrary(System.java:1076)
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at go.LoadJNI.<clinit>(LoadJNI.java:5)
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at java.lang.Class.classForName(Native Method)
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at java.lang.Class.forName(Class.java:324)
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at java.lang.Class.forName(Class.java:285)
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at go.Seq.<clinit>(Seq.java:23)
10-15 16:08:28.256 1632-1632/io.test.gopherandy E/AndroidRuntime:     at go.hello.Hello.Greetings(Hello.java:13)

This is the same as #12890.
I believe you can build with targetSdkVersion=22, but this may have been fixed by 82d11f. Could you try syncing to the latest gomobile and running init and bind again?

@sureshg please reopen this issue if this is not fixed by the latest version of gomobile.

@crawshaw yeah cleaned up the existing gomobile (if that matters) and ran the following commands with new gradle plugin ("org.golang.mobile.bind" version "0.2.3") . Still having the same issue. Did i miss anything?
  $  go get -u golang.org/x/mobile/cmd/gomobile && gomobile init
  $ ./gradlew -b gobuild/build.gradle gobind

0-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime: FATAL EXCEPTION: main
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime: Process: io.test.gopherandy, PID: 22685
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: /data/app/io.test.gopherandy-2/lib/arm/libgojni.so: has text relocations
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at java.lang.Runtime.loadLibrary(Runtime.java:372)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at java.lang.System.loadLibrary(System.java:1076)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at go.LoadJNI.<clinit>(LoadJNI.java:5)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at java.lang.Class.classForName(Native Method)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at java.lang.Class.forName(Class.java:324)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at java.lang.Class.forName(Class.java:285)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at go.Seq.<clinit>(Seq.java:23)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at go.hello.Hello.Greetings(Hello.java:13)
10-15 19:26:31.474 22685-22685/io.test.gopherandy E/AndroidRuntime:     at io.test.gopherandy.MainActivity$1.onClick(MainActivity.java:26)```

@sureshg, update just gomobile is not enough, see #12890 last messages.


[FEATURE] Delayed Connections get removed when departure has passed, when RT Data use "delay" instead of "delay_realtime"

Describe the Bug
For Realtime Updates, instead of "departure_realtime" my Transportation Service uses "delay_realtime".
Delayed Trains get removed from Attributes when the regular scheduled Time has passed.
Expected Behaviour:
Delayed Connection beeing kept in the Attributes as upcoming.
Personally i would prefer having departure_realtime = departure + delay_realtime, as this might make it easier to calculate "Departs in xx Min" in Homeassistant. But any other solution (e.g. internal calculation like include if timestamp_now > timestamp_departure + delay_realtime) would probably work as well.
Steps/data to reproduce the behavior, e.g.
Download the static GTFS: https://rnv-dds-prod-gtfs.azurewebsites.net/latest/gtfs.zip
Register for the API Key for RT-Data: https://github.com/vingerha/gtfs2/issues/51#issuecomment-2057470068 and use them
Set up a Zone with some Stops
Enable RT for that Stop with *.rt as Source
Reload, wait for the next Departures with a delay
See that it gets kicked out after departure time, not taking the delay into account
Release used
gtfs2: <IP_ADDRESS>
HA: HAOS
Core: 2024.4.3
Additional
No logs for that

I see the point but no immediate solution.
The local stops sensor has to first query the static data to find out what departures are upcoming/expected and with those trip_id it then searches for realtime. The static data is limited indeed between now() and now() + range, because the sensor is designed to look ahead.
What a user (you) wants is to continue to see vehicles as long as they have not departed but as I cannot limit the static data based on a single trip/vehicle (it does not have the delay) I would need to extend the limits to between: now() - X and now() + range,
There is no simple (very complex) way to query the data including rt-delay, to e.g. compare with previous state....effort vs. value does not make a business case to me (sorry)
What can be done rather easily is collecting historical departures for anything on that stop up to X in the past and then filter if dep+delay < now()...but.... how long to look back...5 mins, 1 hour, a day?

has to first query the static data to find out what departures are upcoming/expected and with those trip_id it then searches for realtime

Ah i see! Didnt think of that. Makes sense. Too bad.

There is no simple (very complex) way to query the data including rt-delay

Fair enough, i see the huge processing effort in the Background necessary. Absolutely understandable.

What can be done rather easily is collecting historical departures for anything on that stop up to X in the past and then filter if dep+delay < now()

Well - that sounds great! Not sure if understood that correctly - but from my perspective the Result would effectly do that Job, wouldnt it? 😍 It would be something like:

Get all Departures between now() and now() + range
2a. Get all Departures between now() - historyrange and now()
2b. Get the RT Data for Connections found under 2a and discard all found connections dep+delay > now()
2c. Add those to the Array

If i got that right, and that might be doable with a reasonable effort - i'd be superhappy!
In the End i think of the (Realtime) Departure Monitors we do have at all those stops. "Line X arrives in 3 Minutes". Having that in Homeassistant, and do a quick check before leaving would be awesome 👍

...but.... how long to look back...5 mins, 1 hour, a day?

Spontanious: Leave it up to the User. Just like when setting up the static data ("Checking for departures in future from 'now' (in minutes: between 15 and 120"), in the Dialog for the Realtime Integration, there could be a similar option ("Checking against scheduled departures in the past up to (in minutes: between 15 and 120)".
It is clear that the longer the Timespan, the more computing needs to be done.

Spontanious: Leave it up to the User. Just like when setting up the static data ("Checking for departures in future from 'now' (in minutes: between 15 and 120"),

That is the offset you asked in the other request
In this case, how long to look 'back' in order to still see departures that have not yet departed. i.e. I have seen trains that had more than 1 hour delay so would you expect to seem them too? The more historical departures are needed to be scanned and compoared with delay ... the slower it gets. For a few stops and departures bo issue but I have a zone in Basel with more than 15 stops, each with departures every 5 mins or less, the total set of departures reaches more than 150 and that is only 'future' departures

I could also have the user select this but I am also worried about the complexity of adding yet another attribute

Spontanious: Leave it up to the User. Just like when setting up the static data ("Checking for departures in future from 'now' (in minutes: between 15 and 120"),

That is the offset you asked in the other request

Things getting mixed up here, while the two Feature Request sure are related.
The other Feature Request is on setting an offset for Departures (e g.: show Departures in the Range of now() + offset and now() + range).
This here is the other Way around:

in the Dialog for the Realtime Integration, there could be a similar option ("Checking against scheduled departures in the past up to (in minutes: between 15 and 120)".

I could also have the user select this but I am also worried about the complexity of adding yet another attribute

Totally understand your Concerns! I can't estimate the complexity. See below

i.e. I have seen trains that had more than 1 hour delay so would you expect to seem them too? The more historical departures are needed to be scanned and compoared with delay ... the slower it gets.

This would just be a Way for me and probably other affected users, to still catch Delayed connections. I can't estimate how huge the Impact will be - codewise, and also processingwise.
If there would have been such an Option, i would have just given it Shot - "Check for Delayed trains up to: 15 minutes" and see how things go.
In the End, if i got it right, the Basic Workflow at the Moment is:

Get all Departures between now() and now() + range
Get the RT Data for Connections found under 1 and add it to the Connections
Output

This, and the other Feature Request combined would mean a Workflow like:

Get all Departures between now() - history and now() + range  (where history initally would be set to 0 = current behaviour)
Get the RT Data for Connections found under 1 and add it to the Connections
2b. Set departure_realtime = departure + delay
2c. Remove all Departures where now() + offset > departure_realtime (This is the other Feature Request)
Output

If that is too complex, too much effort, too less outcome.... - it is what it is, it is you who surely can assess that!
From my End-Users Perspective the Benefits would be having a Realtime-Departure Monitor including delayed Connections, but only those i will be able to catch if now leaving the House ;-)

I all depends on the area where one lives, there may be places where 15min delays is normal... will try wtih default =15 for now then

And on my above mentioned complexity, the more attributes, the more permutations people need to think of and more complex to reproduce in case of 'errors'

something alike this then?

Whats the approach now for this?
I mean, probably i dont understand or can give advices :-D But just out of Curiosity... ;-)
That is Huge. Really, not kidding. I think to see possible Connections, not filtered by they schedule, but actual Time, is a big Plus imo!! 👍 👍 👍

resolved in <IP_ADDRESS>
Big challenge with the data is the variety of formats of date/datetime/delay in the static data, realtime and server
Solution extracts additional departures till 15min back in time and only filters them out if there is no delay or dep.time+delay < now()

This is great! For sure this is not so easy, especially with the

variety of formats of date/datetime/delay in the static data, realtime and server

But there seems to be an oversight in <IP_ADDRESS>  in the filters for no delay, or departure time+delay < now():

That is not clear neough for me...how often does your sensor update?

For every Stop i set the Interval to 1 Minute.
Only missed this one, and didnt check again.
I am so, so sorry 😢

if the frequency of transport is high...chane the update accordingly to a shorter timespan...yes it will load the system a bit more but at least the data becomes morie usable
Alternative ...if you donot want to run each minute all day long, you can add a button and update the entity when you need it (regular HA sevice call)

As an example, I tie one of those sensors to me as a person, when I am e.g. in Basel I use two buttons,

update location (is often not too fast on &@#&% iPhone)
update stops
With that, my map and stop list update to where I am at that time...quite handy :)


iohyve scram will shutdown ALL bhyve guests.

Running iohyve scram or service iohyve stop will send killall bhyve and this is bad. SO VERY BAD.

Fixed.
https://github.com/pr1ntf/iohyve/commit/9e8f40dd7a132ef0d99a2b1f0417b5c7108b0e10


cp -p in the filesystem updates both mtime and ctime when it should only update ctime.

What happened: cp -p does not keep mtime. Instead it looks like mtime is updated with ctime, which goes against every other file system I tested.
What you expected to happen: cp -p keeps atime and mtime and only changes ctime
How to reproduce it (as minimally and precisely as possible): cp -p oldfile newfile; stat oldfile; stat newfile; and compare results
Anything else we need to know? I tested cp -p on xfs, btrfs, ext4 and in each case, cp -p keeps the atime and mtime and only updates ctime leading me to believe this is a bug in the filesystem.
Environment:

JuiceFS version (use juicefs --version) or Hadoop Java SDK version: git master
Cloud provider or hardware configuration running JuiceFS:
OS (e.g cat /etc/os-release):  RHEL 7.9
Kernel (e.g. uname -a): 3.10.0-1160.25.1.el7.e86_64
Object storage (cloud provider and region, or self maintained): MINIO self maintained
Metadata engine info (version, cloud provider managed or self maintained): TiKV self maintained
Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage): 10GBps
Others:

It does change only the ctime in my test. Could you run cat <mount_point>/.accesslog in another shell when you run the test, and then post the log here?
root@test:/mnt/jfs# stat a
  File: a
  Size: 0               Blocks: 0          IO Block: 65536  regular empty file
Device: 36h/54d Inode: 2           Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-01-31 09:17:42.012940813 +0800
Modify: 2023-01-31 09:17:42.012940813 +0800
Change: 2023-01-31 09:17:42.012940813 +0800
 Birth: -
root@test:/mnt/jfs# cp -p a b
root@test:/mnt/jfs# stat b
  File: b
  Size: 0               Blocks: 0          IO Block: 65536  regular empty file
Device: 36h/54d Inode: 3           Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2023-01-31 09:17:42.012940813 +0800
Modify: 2023-01-31 09:17:42.012940813 +0800
Change: 2023-01-31 09:17:57.599775419 +0800
 Birth: -

@SandyXSD thanks for looking into this, that is what I would have expected as well. To be honest, this log is awesome but looking at it makes me question where it's happening even more so.
Here are the commands ran:

Here is a copy and paste of the log:
2023.01.31 17:32:45.005490 [uid:0,gid:0,pid:243382] getattr (2): OK (2,[drwxrwxr-x:0040775,2,0,130,1673487814,1675204346,1675204346,4096]) <0.001664>
2023.01.31 17:32:45.007006 [uid:0,gid:0,pid:243382] lookup (2,log.txt): OK (4101203,[-rw-rw-r--:0100664,1,1130419,500,1665424815,1674762055,1674762055,15508]) <0.001466>
2023.01.31 17:32:49.598815 [uid:0,gid:0,pid:277781] getattr (2): OK (2,[drwxrwxr-x:0040775,2,0,130,1673487814,1675204346,1675204346,4096]) <0.000970>
2023.01.31 17:32:49.599668 [uid:0,gid:0,pid:277781] lookup (2,log_p): no such file or directory <0.000791>
2023.01.31 17:32:49.601112 [uid:0,gid:0,pid:277781] lookup (2,log.txt): OK (4101203,[-rw-rw-r--:0100664,1,1130419,500,1665424815,1674762055,1674762055,15508]) <0.001335>
2023.01.31 17:32:49.601727 [uid:0,gid:0,pid:277781] lookup (2,log_p): no such file or directory <0.000576>
2023.01.31 17:32:49.602467 [uid:0,gid:0,pid:277781] open (4101203): OK [fh:14431980] <0.000704>
2023.01.31 17:32:49.603069 [uid:0,gid:0,pid:277781] lookup (2,log_p): no such file or directory <0.000567>
2023.01.31 17:32:49.605965 [uid:0,gid:0,pid:277781] create (2,log_p,-rw-------:0100600): OK (11184775,[-rw-------:0100600,1,0,0,1675204369,1675204369,1675204369,0]) [fh:14431981] <0.002852>
2023.01.31 17:32:49.606060 [uid:0,gid:0,pid:277781] write (11184775,15508,0,14431981): OK <0.000026>
2023.01.31 17:32:49.610132 [uid:0,gid:0,pid:277781] setattr (11184775,0x30,[atime=1665424815,mtime=1674762055]): OK (11184775,[-rw-------:0100600,1,0,0,1665424815,1674762055,1675204369,15508]) <0.003999>
2023.01.31 17:32:49.612285 [uid:0,gid:0,pid:277781] setattr (11184775,0x6,[uid=1130419,gid=500]): OK (11184775,[-rw-------:0100600,1,1130419,500,1665424815,1674762055,1675204369,15508]) <0.002114>
2023.01.31 17:32:49.614544 [uid:0,gid:0,pid:277781] setattr (11184775,0x1,[mode=-rw-rw-r--:00664]): OK (11184775,[-rw-rw-r--:0100664,1,1130419,500,1665424815,1674762055,1675204369,15508]) <0.002127>
2023.01.31 17:32:49.619515 [uid:0,gid:0,pid:277781] flush (11184775,14431981,18A443916663FE2E): OK <0.004869>
2023.01.31 17:32:49.619551 [uid:0,gid:0,pid:0] release (11184775,14431981): OK <0.000005>
2023.01.31 17:32:49.619564 [uid:0,gid:0,pid:277781] flush (4101203,14431980,18A443916663FE2E): OK <0.000001>
2023.01.31 17:32:49.619594 [uid:0,gid:0,pid:0] release (4101203,14431980): OK <0.000005>
2023.01.31 17:32:52.050501 [uid:0,gid:0,pid:296215] getattr (2): OK (2,[drwxrwxr-x:0040775,2,0,130,1673487814,1675204369,1675204369,4096]) <0.000835>
2023.01.31 17:32:52.051976 [uid:0,gid:0,pid:296215] lookup (2,log_p): OK (11184775,[-rw-rw-r--:0100664,1,1130419,500,1665424815,1675204369,1675204369,15508]) <0.001420>

Well, this looks like a bug. It was good in my test because the file was empty. For a non-empty file, the mtime is correct for a very short time (set by setattr), and is changed again after data flushed.

@SandyXSD not a problem, we use a custom script that moves the data around and put a work around in it, to touch the files referring to the originals before removing them which works. Luckily the metadata flies with TiKV for us compared to our gluster deployment that it isn't to impacting. If there is absolutely anything I can do to help troubleshoot the issue, I'm available. We are using JFS for petabytes of warm storage so I'm invested  💯

From my point of this issue is important to fix, as it means juicefs is not POSIX compliant.


Update schema.md

Hi.
This modification proposal deals with what I think is a confusion when specifying an schema that really it's a custom schema. Regards.
IL.
What are you changing in this pull request and why?

Checklist

[x] Review the Content style guide so my content adheres to these guidelines.
[ ] For docs versioning, review how to version a whole page and version a block of content.
[ ] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

Adding or removing pages (delete if not applicable):

[ ] Add/remove page in website/sidebars.js
[ ] Provide a unique filename for new pages
[ ] Add an entry for deleted pages in website/vercel.json
[ ] Run link testing locally with npm run build to update the links that point to deleted pages

Hello @ialdg We appreciate this information! Would you be able to open your [comment] pull requests as issues instead so we can triage appropriately? Happy to show you how to link to lines of code if you want.

Hi Leona.
If you could do that I'd appreciate it. Thanks.
Regards.
IL.
El mar, 2 abr 2024 a las 2:17, Leona B. Campbell @.***>)
escribió:

Hello @ialdg https://github.com/ialdg We appreciate this information!
Would you be able to open your [comment] pull requests as issues instead
so we can triage appropriately? Happy to show you how to link to lines of
code if you want.
—
Reply to this email directly, view it on GitHub
https://github.com/dbt-labs/docs.getdbt.com/pull/5176#issuecomment-2030835548,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJPJ6BGHUHD3WAOFK4BKRT3Y3H2KJAVCNFSM6AAAAABFK6WDICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZQHAZTKNJUHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Changing miktex url to ctan!

Miktex url is not working, we have to use CTAN. #2129

We could fix the link to ftp.fau.de, it's the only mirror that supports HTTPS.
https://ftp.fau.de/ctan/systems/win32/miktex/setup/

Existing urls appear to be working now.

@r15ch13 and @brandon93s Sorry for late answers. If existing urls are still working then I will close this pull request.

As long as the mirrors don't use HTTPS they will fail.
I would recommend using https://ftp.fau.de/ instead of downgrading to HTTP

@r15ch13 I was looking for something and I forget to push it. Thx for double reminder and suggestion! 🥂


[FLINK-27755] Introduce a filesystem catalog for table store

The Table Store has store the schema and other information on the file system so that it can actually provide a FileSystemCatalog for users to use.
This catalog is provided in JIRA:

It supports database related management
It supports the creation and deletion of tables
It supports table changes, but currently can only modify the options and other information, the underlying does not yet support the schema column information modification

The use case for filesystem catalog:
CREATE CATALOG table_store WITH (
   'type' = 'table-store',
   'root-path' = '/root-path/'
);

USE CATALOG table_store;

File Table
— create table dir: path '${db_name}.db/${table_name}'
— create schema file in table dir
CREATE TABLE T1 (
    a INT,
    b INT
);

— delete table dir
DROP TABLE T1;

File Table with Kafka Log
— create table dir and schema file
— with kafka existing topic
CREATE TABLE T2 (
    a INT,
    b INT
) WITH (
    'log.system' = 'kafka',
    'log.kafka.bootstrap.servers' = '...',
    'log.topic' = 'my_topic'
);

— delete table dir
DROP TABLE T2;
……

Thanks for the contribution! It looks good in general. I also left some comments. Beyond that, I have the following questions.

For the table T0(created via managed table factory), and the table T1(created by catalog), what is the difference between them (except for the storage location)? Because I saw Schema is recording different options.
Is there any possibility for a catalog impl (which extends TableStoreCatalog) also override supportsManagedTable?

Thanks for the review, I would like to isolate these two ways, finally, we should just provide catalog way.


[BUG] "\n" is missing after capture, i.e, "\nabla" becomes "abla"

Describe the bug
"\n" is missing after capture, i.e, "\nabla" becomes "abla"
To Reproduce
Steps to reproduce the behavior:

Specify the File Name field when add a Capture choice
Click the lightning icon to add command
Select text and call the added command

Expected behavior
Just like ctrl-c ctrl-v
Screenshots

Desktop (please complete the following information):

Linux Mint
Firefox
QuickAdd 0.10.0

This issue still exists.
Did you find out a workaround for it?

@PluggeRo No. I searched but did not find.

@shizidushu I just found a workaround here: https://forum.obsidian.md/t/quickadd-transfer-dataviewjs-linebreak-to-note/60663/3
You can replace \n with the corresponding unicode: \u000a to get the same result.


Keep track of needed wildcards

With the collection status showing how many copies of a card you already own in every booster, I came up with the idea to keep track of the wildcards needed to craft missing cards and display that information somewhere during draft/deck building.

?

👍 Left feedback in the PR.
Interesting question:
What happens if you own a particular card 3x already and end up drafting it 5 times in a draft on your site...
Do you only need to spend 1 wildcard to get the maximum amount of copies and the rest is free in MTGA?

👍 Left feedback in the PR.

Thanks!

Interesting question:
What happens if you own a particular card 3x already and end up drafting it 5 times in a draft on your site...
Do you only need to spend 1 wildcard to get the maximum amount of copies and the rest is free in MTGA?

I think once you own 4 copies, you effectively own an unlimited amount (see Persistent Petitioners), will update to reflect that too :)

First quick feedback after the merge:

I like that the new wildcard warning during the draft is all a single tooltip - it was easy to miss with the two right next to each other before 👌
Normal basic lands are falsely counted towards common wildcards, same happens for snow basics which doesn't require them either
The overview of needed rare/mythic wildcards in the menu headline doesn't account for cards in the sideboard, same goes for the color change in general:

Intentional maybe?
Patch notes could be confusing now as the last one supersedes the former note:

14/02/2021
    Implemented wildcard tracking while drafting and brewing.

30/01/2021
    Added a reminder of the number of owned copies of each card while drafting.

Normal basic lands are falsely counted towards common wildcards, same happens for snow basics which doesn't require them either

Fixed in 30b2638e57be64ac3845273a556a1a7b7535ad82

The overview of needed rare/mythic wildcards in the menu headline doesn't account for cards in the sideboard, same goes for the color change in general:
Intentional maybe?

Yep, see reasoning in PR


Editor cannot edit the metadata of the article

Editor cannot see the TR version of the metadata and more importantly cannot edit the metadata. Thread is opened.
http://ojs.io/journal/3/articles/15

Editor can view TR version if he changes the page language. But it is a different case, I think. No matter what page language is, he should see what author filled

Depends https://github.com/okulbilisim/ojs/issues/990

fixed with workflow-bundle


make install

There should be a make install to simplify making tweaks to the bootstrap files.  Passing the DESTDIR would copy the new files to the users desired directory.

make install DESTDIR=/path/to/dir

Closing out this and punting to your PR.

To my PR?  What did I do wrong?

Oh - I see.  Pull request.  I've never contributed to an OS project via pull request before.  Should I not have created an issue for it?


VSC not seeing symbols in outline for c language (No symbols found in document eg_name.c)

Type: Bug
VSC not seeing symbols in outline for c language (No symbols found in document eg_name.c).
Working for python, etc.
I expected to see function lists and class, etc. like on python.
VS Code version: Code 1.88.0 (5c3e652f63e798a5ac2f31ffd0d863669328dc4c, 2024-04-03T13:26:18.741Z)
OS version: Windows_NT x64 10.0.22631
Modes:
#209755
Use any c code like
#include <stdio.h>
int main() {
   // printf() displays the string inside quotation
   printf("Hello, World!");
   return 0;
}

/extC
Outline is provided by the language service extension, so should be tracked there.

It looks like this is caused by the C extension. Please file the issue to the C extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


LastFM authentication failed on any try to login on Android 10 device.

LastFM authentication failed on any try to login on Android 10 device.
Attached log from login attempt.

Originally posted by @Toxa-Maker in https://github.com/simple-last-fm-scrobbler/sls/issues/568#issuecomment-609502867

Also seeing this issue. Just noticed I hadn't been scrobbling since April 3rd.

Also seeing this, login error and empty cache two weeks worth of scrobbling.

O que vocês fizeram?

Having the same issue ...


Fix semver v2.0.0 floating version for "latest prerelease"

The sample for creating a floating version for a SemVer version suffix is somewhat incorrect, in that it allows an unbounded number of suffixes without incrementing suffix numbers.
For more information, consider reading the documentation about NuGet versioning:
https://docs.microsoft.com/en-us/nuget/concepts/package-versioning#pre-release-versions
Or the SemVer spec:
https://semver.org/spec/v2.0.0.html
We may want to add an additional example for "latest build" as well as "latest prerelease", and possible add comments in the sample MSBuild XML so people can follow it more clearly.

Docs Build status updates of commit 29f1e47:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/consume-packages/Package-References-in-Project-Files.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


New version: Hitencent.JisuTodo version <IP_ADDRESS>

Created by 🥟 Dumplings in workflow run #7142.

Log
Updated: <IP_ADDRESS> → <IP_ADDRESS>
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -2145844848
2024-08-06 07:29:45.455 [CORE] DeliveryOptimization error: 0x80190190, extended error: 0x00000000
2024-08-06 07:29:45.690 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!548657EB: (caller: 54865E1C) Exception(1) tid(340) 80190190 Bad request (400).
2024-08-06 07:29:47.349 [CORE] Download request failed. Returned status: 400
2024-08-06 07:29:47.349 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!5485FA75: (caller: 54860E2B) Exception(2) tid(340) 80190190 Bad request (400).
2024-08-06 07:29:47.466 [CLI ] Failed to download, waiting a bit and retry. Url: https://dl.jisutodo.com/jisutodo_setup_<IP_ADDRESS>.exe
2024-08-06 07:29:53.923 [CORE] DeliveryOptimization error: 0x80190190, extended error: 0x00000000
2024-08-06 07:29:53.923 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\DODownloader.cpp(289)\WindowsPackageManager.dll!548657EB: (caller: 54865E1C) Exception(3) tid(340) 80190190 Bad request (400).
2024-08-06 07:29:54.190 [CORE] Download request failed. Returned status: 400
2024-08-06 07:29:54.190 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(148)\WindowsPackageManager.dll!5485FA75: (caller: 54860E2B) Exception(4) tid(340) 80190190 Bad request (400).

(Automated response - build 887.)

URL: https://dl.jisutodo.com/jisutodo_setup_<IP_ADDRESS>.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 912)


Many statements in Mapping classes not seperated by checkpoints

What it says in the title!
i.e. Star post process
        cp %(tmpdir)s/Log.std.out %(outfile)s.std.log;
        cp %(tmpdir)s/Log.final.out %(outfile)s.final.log;
        cp %(tmpdir)s/SJ.out.tab %(outfile)s.junctions;
        cat %(tmpdir)s/Log.out >> %(outfile)s.log;
        cp %(tmpdir)s/Log.progress.out %(outfile)s.progress;
        cat %(tmpdir)s/%(track)s.bam
        %(unique_cmd)s
        %(strip_cmd)s
        | samtools sort -o %(outfile)s 2>>%(outfile)s.log;
        samtools index %(outfile)s;

If the first samtools command fails, because, for example the samtools syntax changes (again), this will not raise an error.
All bash statements should be seperated by calls to checkpoint
E.g. from the above:
        cp %(tmpdir)s/Log.std.out %(outfile)s.std.log;
        checkpoint;
        cp %(tmpdir)s/Log.final.out %(outfile)s.final.log;
        checkpoint;
        cp %(tmpdir)s/SJ.out.tab %(outfile)s.junctions;
        checkpoint;
        cat %(tmpdir)s/Log.out >> %(outfile)s.log;
        checkpoint;
        cp %(tmpdir)s/Log.progress.out %(outfile)s.progress;
        checkpoint;
        cat %(tmpdir)s/%(track)s.bam
        %(unique_cmd)s
        %(strip_cmd)s
        | samtools sort -o %(outfile)s 2>>%(outfile)s.log;
        checkpoint;
        samtools index %(outfile)s;

I'm happy in theory to work on the solution to this, but not right now as I'm off on holiday.

Hopefully I have resolved this issue in AC-Add_check_mapping branch


VeryGOOD ! I am your forever Fans

This project is one of the best That I have saw . This performance of this WEB Program is very very high.Come on to The top 10 of Programmer Gopher.

thank you very much


Allow to define descriptor for GATT characteristic

First implementation for Descriptor in linux.
Tested as working feature on Raspberry 4.
Feel free to review and comment.
I noticed that bless library does not expand the uuid from 16 bit and 32 bit form.
I put a proposal to use normalize_uuid_str to expand uuid to full value.

Thank you for these additions. I sincerely appreciate that you followed the code style so well. I'll merge this to develop but I won't mark this issue as resolved just yet since I'd like to see if windows and macOS could be implemented too.
Thanks for tackling the DBus backend!

Is it possible to provide a simple example for defining descriptors? @mklemarczyk @kevincar

Sure, I will look in it. Sorry, I was off a bit.