Fix: Typo and wording of description in readme

Describe the bug
The description of the project in the readme has a typo in the spelling of the word "components" and is worded wrong.
To Reproduce
Go to readme and read first line after title.
Expected behavior
It should say instead: "Open Source Project for beginners. A playground UI library published on npm to practice creating components with React and TypeScript."

@ValerioCipolla Hi there! Can I help fix the typo?


Add basics of system overview doc

fyi @smile21prc @stephentoub @KKK9527 @Priya91

Very useful overall.  Thanks, @mmitche!

A good starting doc :) Thanks @mmitche


Writing parsers for custom structs in define_language! macro

I'm trying to write a custom parser for a language term that uses a struct that I have defined.
Let's say I have a language defined as,
define_language! {
    pub enum DummyLang {
        Point2D(Point2D),
    }
}

where Point2D is
#[derive(Debug, Clone, Hash, PartialEq, Eq, PartialOrd, Ord, Display, FromStr)]
#[display("(x:{x},y:{y})")]
pub struct Point2D {
    pub x: i32,
    pub y: i32,
}

Then the below line
let exprViaString: RecExpr<DummyLang> = "(x:24,y:36)".parse().unwrap();

results in a BadOp(FromOpError { op: "x:24,y:36", children: [] })',
I setup a minimal example in a repo with a testcase showing that the parser for Point2D exists, but I'm not able to parse it to a RecExpr.
A sort of workaround I've been living with is to define Point2D as a list of Ids, like
define_language! {
  Num(i32),
  "point2D" = Point2D([Id; 2]) // (point2d 24 36) now parses.
}

But as you can imagine, this results in a lot of boilerplate in unpacking the ids when wanting to inspect Point2D, and it's easy to mess up the order of point2D args.
(I have a feeling I'm missing something obvious, but my rust foo is not strong enough to figure it out.)

Ahhhhh, that worked! Thank you for the quick response! I knew I was missing something obvious :/

:+1:


Uncaught exception 'FastRoute\BadRouteException'

I'm using the next routing with some regex, but I'm getting the next error:

Uncaught exception 'FastRoute\BadRouteException' with message 'Regex "(true|false)" for parameter "value" contains a capturing group'

my code:
    $this->put('/vendido/{id:[0-9]+}/{value:(true|false)}', function (Request $request, Response $response) {
        //..code go here
    });

I need to pass boolean values, as you can see. So. Can I do that?...and if so, how is the correct way to implement a regex that uses boolean and capturing group?. Thanks :)

duh!, I can't use true or false xdxd. My mistake, sorry  :)


Introduce flatgeobuf to eoxmap as a possible format

It would be great to include support for loading a flatgeobuf cloud optimized vector data format https://www.npmjs.com/package/flatgeobuf
https://guide.cloudnativegeo.org/flatgeobuf/flatgeobuf-in-js.html
Example how it was used in eodash v4
https://github.com/eurodatacube/eodash/pull/1631/files#diff-0d6cb8beb4a03a94cdb041528f0c2583093011bc7884f413735bc14d24d0d3d5R187-R230

Probably best suited for the "advanced layers and sources"


Update for .Net 6.0

hi,
Can this repository for .Net be updated to the net6.0 version as it is the standard open source version if I may used across various platform(s).
--
Thanks & regards,
Ragavendra

I see the nuget package GtfsRealtimeBindings needs to be supported for net6.0 , which needs to be updated, hence re - opening this issue.


Can't use ULA addresses in NAT64

Ran into an issue where routing on the OCP cluster gets confused by the use of ULA addresses on the machine network.
OCP uses ULA addresses for internal networks, OVN kubernetes for example. When using ULA addressing on the machine network there is race when building the routing tables - and in some cases the hosts end up using the wrong source address in outgoing traffic.
To fix this, switch to GUA addresses.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/approve


Fix PKGBUILD and update it to latest release

Signed-off-by: Itai-Nelken<EMAIL_ADDRESS>

The AUR already has it up to date, so I can either make it identical to this or vice versa
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=dollarskip


Support for adding/removing physical volumes

This sits on top of #128.  The idea is that this is wrapped by "atomic storage", just as "--reset".
This change is intended to support the Cockpit use cases describes here:
https://github.com/cockpit-project/cockpit/wiki/Atomic:-Docker-Storage

This change allows adding disks to the storage pool, and removing them again.  Providing information about the storage pool will be supported by a later PR.
The --add option has been added to offer easy adding of disks, without having to edit /etc/sysconfig/docker-storage-setup.  The --add operation is a one-time, immediate change to the storage pool that either works or doesn't and does not have any effect beyond that.  For example, the block devices given to --add are not processed again the next time docker is started.
The ``--reset-and-reduceoption has been added to offer opportunistic removal of unused block devices from the pool, in a way that puts the devices back into a state that is acceptable to--add`.
The user interface and API to these features is via the atomic storage command, see https://github.com/projectatomic/atomic/pull/373.

@mvollmer It will help a lot if you write a good description of what you are doing and why you are doing. One line descriptions really don't help.

--add should really not be a command line option. One can easily add a disk in /etc/sysconfig/docker-storage-setup (DEVS="/dev/sda /dev/sdb") and restart docker-storage-setup service.

I think removing of disks and volume group can easily be done outside of docker-storage-setup. Why not do it that way.
docker thin pool and root lv share same volume group by default. And these disk might easily be used by root lv and attempt to reduce volume group and disk will fail anyway.
So instead of making docker-storage-setup complicated, I think it might be better that removing the disk from volume group is done outside of docker-storage-setup using lvm commands.

@mvollmer I think we should open issues to discuss.
A user wants to add additional storage to the docker storage, How would he do it? How could I do this from program control?
A user wants to remove storage from docker storage, How would he do it?  How could I do this from program control?
Then we need to document these use cases and figure out how we could do this from atomic or cockpit, if we choose to implement them.

Most of these use cases should be just modify /etc/sysconfig/docker-storage-setup and restart docker-storage-setup command.

--add should really not be a command line option. One can easily add a disk in /etc/sysconfig/docker-storage-setup (DEVS="/dev/sda /dev/sdb") and restart docker-storage-setup service.

/e/s/d-s-s is a shell script, and having to edit it is not a nice API.

I think removing of disks and volume group can easily be done outside of docker-storage-setup. Why not do it that way.

Because d-s-s is the entity that adds disks, and it thus makes sense to me that it should also be the entity that removes them.  Wiping the disks just right is not entirely straightforward, and d-s-s know what it does with partitions and it can thus take the responsibility to undo that upon removal.

docker thin pool and root lv share same volume group by default. And these disk might easily be used by root lv and attempt to reduce volume group and disk will fail anyway.

Yeah, sh*t happens. :-)  But not always, and if we deem it important, we can use a dedicated volume group by default, or advise people to do that.  The alternative would be to require people to reinstall the host in order to get the disks out of the docker storage pool, which might be totally acceptable.

So instead of making docker-storage-setup complicated, I think it might be better that removing the disk from volume group is done outside of docker-storage-setup using lvm commands.

d-s-s might have less code, but I think the bigger picture would be more complex.

Most of these use cases should be just modify /etc/sysconfig/docker-storage-setup

Editing /e/s/d-s-s programmatically is painful and unreliable.  We can do better.
Removing disks is not possible by changing /e/s/d-s-s.
The use cases should be docker-agnostic and be done via the atomic storage command, not d-s-s.

I think removing of disks and volume group can easily be done outside of docker-storage-setup.

Would it be appropriate to do it inside atomic storage?

It will help a lot if you write a good description of what you are doing and why you are doing. One line descriptions really don't help.

I have included a longer description at the top.  Does this help?

The user interface and API to these features is via the atomic storage command, see projectatomic/atomic#373.

In other words, I don't really care how the work is divided between atomic and docker-storage-setup and whether atomic does its job by editing /e/s/d-s-s or not.

Are the tests expected to pass?  This looks like it probably isn't my fault:
tests/004-test-devmapper-cleanup: line 62: test_overlay: command not found
FAIL: 004-test-devmapper-cleanup

I think adding this to atomic storage is a better idea,  I believe we should keep d-s-s to reading the config and creating the storage, Reset is fine in d-s-s since it is doing some stuff inside that external tools would not know about.
atomic storage --add-device=/dev/foobar
atomic storage --list
atomic storage --remove-device=/dev/foobar

atomic also has the nice benefit of being written in python versus Bash, so doing more complex things like managing config files is a little easier to do.

I think adding this to atomic storage is a better idea,

How would you propose to implement atomic storage add, in contrast to https://github.com/projectatomic/atomic/pull/373?

I think adding additional commands in atomic sounds like a decent idea.
What I find little odd about it though that part of the configuration happens directly by working on config file (/etc/sysconfig/docker-storage-setup) and then rest of the configuration happens using atomic.
I think lets take it case by case basis. For the "status" of current state, I feel it should be implemented in docker-storage-setup and atomic status can just call it. Adding and removing disks can completely be an atomic implementation without any support from docker-storage-setup.

Yes anthing to do with modifying /etc/sysconfig/docker-storage-setup should be done with external tools like vi, atomic and potentially cockpit.  Then just restart docker-storage-setup to read the modified config and fix the configuration.

Sure, now only thing is that instead of cockpit, you are willing to provide all that functionality in atomic. I think that's fine. Life will become easier for normal command line users as well. Dealing with volume groups and lvs and pvs is not always easy.

Yes anthing to do with modifying /etc/sysconfig/docker-storage-setup should be done with external tools like vi, atomic and potentially cockpit. Then just restart docker-storage-setup to read the modified config and fix the configuration.

So atomic storage add /dev/foo would change /etc/sysconfig/docker-storage-config and make sure that DEVS includes /dev/foo, right?  Would it also run d-s-s?  Would it remove /dev/foo from DEVS afterwards?  Always, or only when d-s-s fails?

It would leave it there permanently, and yes, I would figure it would rerun the service. If it fails it would restore the /etc/sysconfig/docker-storage-setup.
Something like:
cp /etc/sysconfig/docker-storage-setup  /etc/sysconfig/docker-storage-setup.bkp
modify   /etc/sysconfig/docker-storage-setup
run d-s-s
if Success
rm  /etc/sysconfig/docker-storage-setup.bkp
else
mv  /etc/sysconfig/docker-storage-setup.bkp   /etc/sysconfig/docker-storage-setup
d-s-s
fi

Something like: [...]

Alright, I'll do that. Thanks!

This is obsolete, see https://github.com/projectatomic/atomic/pull/373.


Add RIOT CoAP Channel

CoAP channel for the RIOT platform.
All channels share the same server and delegate the message to the correct Channel based on the other federates IP-Address.

I have added a test under test/unit/riot/coap_channel_test and restructured this PR to be ready for review so far I would say.
I am really not so sure how to integrate the coap_channel_test with cmake yet, but at least it is possible to run it when using make all in the folder

Okay I have now made the unit test run in CI as well.
I have also renamed our CI workflows to make it more clear what they are about and reduced duplication (I think the jobs don't need to contain the word "zephry" or "RIOT" if the wokflow is already called so. :)

I think the problem with clang-format is that you have a different version than the CI:
> clang-format --version
Ubuntu clang-format version 18.1.3 (1ubuntu1)

Is it possible for you to get that exact version?

So I installed clang-format-18 and configured this project to use that specific formatter version instead and it works fine now. :)


Update repo from private version (NOTE: this is not my code)

Publish private version

Thank you for fixing all those changes! The PR looks good


Change checkbox color

Hi
I need change Checkbox TintColor
Is it possible?

No, per What's New in Version 2:

No dynamic color support, your dialogs will match your app theme.

You could pass a ContextThemeWrapper in your dialog constructor, though, if you don't want the checkboxes to match your app's colorAccent.


latest master build failed for AWS VPC resources

Looks like the latest master build failed for bunch of AWS resources, VPC is just an example.
2020/09/01 10:25:58 aws importing region us-east-1
2020/09/01 10:26:01 aws importing... vpc
2020/09/01 10:26:02 Refreshing state... aws_vpc.tfer--vpc-002D-049c01d370e4b6a94
2020/09/01 10:26:02 Refreshing state... aws_vpc.tfer--vpc-002D-4314a139
2020/09/01 10:26:02 Refreshing state... aws_vpc.tfer--vpc-002D-026dcb2561926e019
2020/09/01 10:26:02 ERROR: Read resource response is null for resource aws_vpc.tfer--vpc-002D-026dcb2561926e019
2020/09/01 10:26:02 ERROR: Read resource response is null for resource aws_vpc.tfer--vpc-002D-4314a139
2020/09/01 10:26:02 ERROR: Read resource response is null for resource aws_vpc.tfer--vpc-002D-049c01d370e4b6a94
2020/09/01 10:26:02 ERROR: Unable to refresh resource tfer--vpc-002D-026dcb2561926e019
2020/09/01 10:26:02 ERROR: Unable to refresh resource tfer--vpc-002D-049c01d370e4b6a94
2020/09/01 10:26:02 ERROR: Unable to refresh resource tfer--vpc-002D-4314a139
2020/09/01 10:26:02 aws Connecting....
2020/09/01 10:26:02 aws save vpc
2020/09/01 10:26:02 aws save tfstate for vpc

Same https://github.com/GoogleCloudPlatform/terraformer/issues/631 ?


pydantic-yaml emits annoying warning

Saving to yaml from a pydantic model generates this annoying warning:
/afs/eufus.eu/g2itmuse/user/g2ssmee/duqtools/venv/lib/python3.7/site-packages/pydantic_yaml/mixin.py:159: UserWarning: Explicit custom root behavior not yet implemented for pydantic_yaml. This may not work as expected. If so, please create a GitHub issue: https://github.com/NowanIlfideme/pydantic-yaml/issues/new
  "Explicit custom root behavior not yet implemented for pydantic_yaml."

It is related to the use of __root__ in e.g. Runs, but it does not have any negative effects on our code so it can be ignored.

merged into #141


right to left support

this library can be support right to left customize?

Would be great if RTL support is added.
Thank you for sharing! :-)


STAR-Fusion crashes because of missing DB_File module

We need to find a way to activate DB_File when building Perl. We might need to package BerkeleyDB for this.

Fixed. DB_File can be build separately.


How to do inference on video datasets?

Thanks for the code updates you have made. Glad to see deep featurte flow for semantic segmentation.
Kindly let us know do you have inference codes written for video sequence? Kindly let us know.

No, I only follow the original paper to do the evaluation on the 20th frame. It's simple to apply to the video sequence


Cannot save animation libraries

Godot version
4.0.dev (15740c37a3)
System information
Linux, 64-bit, Fedora 36, AMD RX 590, Vulkan
Issue description
Trying to save an animation libraries fails, reporting _button_pressed called expected 3 arguments but was called with 4.
Steps to reproduce
Try to save an animation library by clicking the save button in the the tree column.  The popup that allows you to select the message is never shown and an error is printed out.
Minimal reproduction project
No response

Duplicate of #61422. There's already a PR, too.


Real-Time Order Book

This is a basic implementation of a real-time order book as described and implemented in the official Node.js client library.
I did some initial validation by watching the bid-ask spread on the GDAX web UI and console output produced by this code. It could use some more features for exposing the state of the order book in a thread-safe manner.

This looks great. I am merging for more thorough testing from the community before pushing to PyPI.


"Error - ReceiveSymboleE"

Not sure what the full error message is as it seams cut in both ends, but since two weeks all my trackers only says "Error ReceiveSymboleE".
If I click on it, sometime it shows the graph for a micro second.
This it what it looks like: https://imgur.com/07qR5sg

@jandolina I fiddled around with some settings and managed to get a view that does not have it. Though I've noticed some other issues which may or may not be related.

Graphs are really wired sometimes, they can be flat or like sawtooth, but not the actual data. When this happens is usually for one or two of the graphs.
Daily graphs are off and it's seams to be timezone related. The tickers I'm looking at are Swedish and our market is open between 9am to 5:30pm, but that's not the data I see graphed.

Use ^OMXS30 and compare what you get out to this https://www.avanza.se/index/om-indexet.html/19002/omx-stockholm-30
And now all graphs just turned to "ReceiveSymbolE" again, so I guess it didn't fix itself as I though for a moment 😅

I'm still seeing this too and have for many weeks really.

Clicking the "Yahoo" link gives an "File not found"

I'm from Denmark if that is relevant.

Any updates on this? I'm still having this issue.

I have been unable to recreate this bug in the US and in the UK. I am looking for a solution but it is hard to fix without being able to recreate it. Apologies for the downtime.

If it's location related and you have access to a vpn service, try going out through Sweden and see if that gives the error.

Or via VPN from Denmark here we seem to have the same issue and it's really sad as I really enjoy your plugin :D

Just tried starting FIddler and have a look...and it's actually odd, it looks like only ONE of the requests actually fail, but I see errors on all of the buttons.

That's it! Now I removed the USDDDK that failed, closed StreamDeck and started it again and now it works!
So apparently this happens, if just one of the button setups fails.

This is good news! Thank you for the debugging. I will see where
USDDDK goes wrong and see if I can't debug it.
On Wed, Jun 28, 2023 at 8:54 AM Mads Laumann @.***>
wrote:

That's it! Now I removed the USDDDK that failed, closed StreamDeck and
started it again and now it works!
So apparently this happens, if just one of the button setups fails.
[image: image]
https://user-images.githubusercontent.com/1378458/249394304-09ff8f9e-a4dc-4b96-9547-d10c1df339dc.png
—
Reply to this email directly, view it on GitHub
https://github.com/Phando/Streamdeck-Stonks/issues/42#issuecomment-1610941977,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUXMD3GADANDFUZ5I3WDTXNPPMZANCNFSM6AAAAAAY5PMA74
.
You are receiving this because you commented.Message ID:
@.***>

You don't have to live without that symbol, you can use USDDKK=X.
Since the queries are batched. I figure a bad ticker will make the whole
batch to error out.
On Wed, Jun 28, 2023 at 8:59 AM Joe Andolina @.***> wrote:

This is good news! Thank you for the debugging. I will see where
USDDDK goes wrong and see if I can't debug it.
On Wed, Jun 28, 2023 at 8:54 AM Mads Laumann @.***>
wrote:

That's it! Now I removed the USDDDK that failed, closed StreamDeck and
started it again and now it works!
So apparently this happens, if just one of the button setups fails.
[image: image]
https://user-images.githubusercontent.com/1378458/249394304-09ff8f9e-a4dc-4b96-9547-d10c1df339dc.png
—
Reply to this email directly, view it on GitHub
https://github.com/Phando/Streamdeck-Stonks/issues/42#issuecomment-1610941977,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUXMD3GADANDFUZ5I3WDTXNPPMZANCNFSM6AAAAAAY5PMA74
.
You are receiving this because you commented.Message ID:
@.***>

Yeah the "problem" as I see it isn't really that this one fails - its that one can take down them all thats the problem :)

@Laumania Thanks again for your direction.
I put out a new release with this fix and one for the day change scaling.
https://github.com/Phando/Streamdeck-Stonks/releases/tag/v1.1.16

@Laumania Thanks again for your direction. I put out a new release with this fix and one for the day change scaling. https://github.com/Phando/Streamdeck-Stonks/releases/tag/v1.1.16

Cool - how is it with StreamDeck, it updates automatically right?

I think the plugin will update once it is approved. In the meantime, you
can manually update it by taking the release .sdPlugin and move it to the
Plugins folder.
On macOS - path ~/Library/Application Support/com.elgato.StreamDeck/Plugins
On Windows - path %appdata%\Elgato\StreamDeck\Plugins\
On Wed, Jun 28, 2023 at 2:44 PM Mads Laumann @.***>
wrote:

@Laumania https://github.com/Laumania Thanks again for your direction.
I put out a new release with this fix and one for the day change scaling.
https://github.com/Phando/Streamdeck-Stonks/releases/tag/v1.1.16
Cool - how is it with StreamDeck, it updates automatically right?
—
Reply to this email directly, view it on GitHub
https://github.com/Phando/Streamdeck-Stonks/issues/42#issuecomment-1611441528,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABUXMGUUZLC3RV6VJRDJULXNQYKXANCNFSM6AAAAAAY5PMA74
.
You are receiving this because you commented.Message ID:
@.***>

The yahoo actually returns 401: invalid cookie error:
{"finance":{"result":null,"error":{"code":"Unauthorized","description":"Invalid Cookie"}}}

@nerakhon Thank you for the note. I am afraid the cookie error has to do with location (Czech Republic). I will look into this, but without being able to recreate the error myself it has been hard to fix.

Well i'm having same issues from some days.. with the Stream deck plugin store i've got the "Error ReceiveSymboleE" and with the latest release v1.1.16 i've got every icon with the Green Falcon and nothing else.. if i click on the Yahoo Finance it gives me the blank page with the ERR_FILE_NOT_FOUND..

I'm using it from italy.. any fix??

I'd be more than happy to assist, we can do screen sharing or some other method or I can gather some data. Let me know what and I'll be happy to help.

Maybe one thing I played a bit with the URL in a browser, and at least there, the 401 can be averted by grabbing the crumb from  https://query1.finance.yahoo.com/v1/test/getcrumb and adding crumb as a query argument.

I have been unable to recreate this bug in the US and in the UK. I am looking for a solution but it is hard to fix without being able to recreate it. Apologies for the downtime.

I started seeing this in the US on Thursday or Friday. Still seeing it today.

Is this old news? Found this on the Yahoo Finance API Feedback form (reference => https://docs.google.com/forms/d/e/1FAIpQLSeyb7xMtZFjoNYI7XG1rjlhUopKAxdLAfSRcaPxg9p-9ii-_g/viewform?fbzx=-7189957683680596558"}}})


[STORM-1390] If you find a suitable constructor do NOT need to look for a d…

If you find the right constructor, you do not have to look any further.

@lispking regarding the original code, I think it means to give a warning when it meets multiple eligible constructors (sort of like multiple bindings for slf4j), so I don't think we should break on first match.

@unsleepy22 i see, but this may make people confused.

@lispking
Though I've addressed potential bug point, I'm with @unsleepy22.
Its role is not that we strongly need to optimize. It doesn't affect performance.
Knowing user's intention correctly is the most important point to Flux so finding out missing point and showing warning is vaild operation, I think.

@HeartSaVioR Thank reminder, your proposal is appropriate。


Update style.css and Add space around search bar

The style.css has been updated to add space around the search bar

kindly so me the output so that I can verify it.

hello @codervivek5. Thanks for responding !   Added top margin space for the button and aligned it to center. It looks like this now.. do tell me if any more changes are required.. Thank you!

kindly mention your PR number

hello @codervivek5 . Could you help me where i can find the PR number

it's my mistake Actually I want to tell you about the issue number. You have to mention the issue number at PR time.

Hello @codervivek5.. is this what you wanted? It shows #36 below opened issue here

dude when i assign it to you then you was working in under a issue so I want to know that issue number

Hello @codervivek5.. is this what you wanted? It shows #36 below opened issue here

this is PR number and I want issue number

I'm sorry. It shows #8 as you can see in the image

ok ok ......maybe It's would be my mistake


Add iPhone XS to our device lab

To monitor our performance on newer iPhones.
We'll later use this to test our metal performances too.

This would also help https://github.com/flutter/flutter/issues/31086

We've setup mac8 with iPhone X (currently in my desk instead of in the lab). I'll close the issue once we've done some successful performance benchmarks through https://github.com/flutter/flutter/pull/35556

FYI I believe it's the XS, not the X, that has the higher sampling rate that causes performance issues. Just want to make sure you are setting up the correct device.

Luckily, we did buy the iPhone XS as Apple is no longer selling iPhone X on its website :) Edit the title of this issue to reflect that.

Almost done. I only need to move the Mac Mini and iPhone XS from my desk to the actual lab.

Our lab is currently running out of space. So the device will remain on my desk for a while. The test will keep running.

Moved to the new device lab desk. Closing.


View Changes does not apply

I'm using anuglar2-meteor package and I have a problem with views.
when I change an html file in my IDE, changes does not apply in the browser (even after client refreshing).
clear cache in browser is helpful and after that I can see those changes I made. any solution for this?

Yes, there seems to be no way currently to control caching in the @View annotation or any other way. But you can always turn off caching for a particular site today in most browsers with the help of development tools. I personally develop and test using Google Chrome Dev tools, and have no trouble with the caching.

Is there a point to the @View annotation?  I never use it, since template and templateUrl can go in @Comonent, is there any point to @View?

@mehdibalouchi no, view metadata is added anyways though @Component if there is no @View. But my answer was not exactly right. You can always try something like:
@Component({
templateUrl: devMode ? 'foo.html?v=' + Random.id() : 'foo.html'
})
It might help.

We also may consider adding some similar feature in the future.

We recommend to use template as string in the components.
Check out https://github.com/Urigo/angular2-meteor#static-resources.
Thus, problem has dissolved itself for now.
In future, it's gonna be possible to import template URLs as well:
import url from './foo.html!url', where url comes with a hash param.


Flashing a progream with cargo embed or probe-rs download fails on metro_m0

Describe the bug
Flashing a progream with cargo embed or probe-rs download fails on metro_m0. The same program succeeds when flashing via openocd:
% cat memory.x
MEMORY
{
  /* same problem when using memory.x from metro_m0 package with 8 kiB offset for bootloader */
  FLASH (rx) : ORIGIN = 0x00000000, LENGTH = 256K
  RAM (xrw)  : ORIGIN = 0x20000000, LENGTH = 32K
}
_stack_start = ORIGIN(RAM) + LENGTH(RAM);
% probe-rs download target/thumbv6m-none-eabi/release/blinky --chip ATSAMD21G18A --log-file /tmp/log.txt
 WARN probe_rs::session: Could not clear all hardware breakpoints: An ARM specific error occurred.

Caused by:
    0: Error using access port.
    1: Failed to read register DRW at address 0x0000000c
    2: An error occurred in the communication with an access port or debug port.
    3: Target device did not respond to request.                                                                                thread 'main' panicked at probe-rs/src/probe/cmsisdap/mod.rs:918:16:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

log.txt.gz - yapicoprobe firmware
Probe is put in wrong state and I need to reconnect.
And on debugprobe firmware:
probe-rs download target/thumbv6m-none-eabi/release/blinky --chip ATSAMD21G18A --log-file /tmp/log.txt
 WARN probe_rs::architecture::arm::core::armv6m: Core is running, but we expected it to be halted                                                                                WARN probe_rs::session: Could not clear all hardware breakpoints: An ARM specific error occurred.

Caused by:
    Timeout occurred during operation.                                                                                Error: The flashing procedure failed for 'target/thumbv6m-none-eabi/release/blinky'.

Caused by:
    0: Something during the interaction with the core went wrong
    1: A timeout occurred.

log2.txt.gz - RPI debugprobe pico firmware
To Reproduce
Steps to reproduce the behavior:

Create any firmware (blinky should do)
Attach probe to metro_m0
Set permissions to usb device
Run cargo embed or probe-rs download

Expected behavior
Firmware downloads on board
Stacktrace
Caused by:
    Timeout occurred during operation.

Stack backtrace:
   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
   1: <probe_rs::session::Session as core::ops::drop::Drop>::drop
   2: core::ptr::drop_in_place<probe_rs::session::Session>
   3: probe_rs::cmd::download::Cmd::run
   4: probe_rs::main
   5: std::sys_common::backtrace::__rust_begin_short_backtrace
   6: std::rt::lang_start::{{closure}}
   7: std::panicking::try
   8: std::rt::lang_start_internal
   9: main
  10: __libc_start_call_main
  11: __libc_start_main@@GLIBC_2.34
  12: _start                                                                                Error: The flashing procedure failed for 'target/thumbv6m-none-eabi/release/blinky'.

Caused by:
    0: Something during the interaction with the core went wrong
    1: A timeout occurred.

Stack backtrace:
   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
   1: probe_rs::cmd::download::Cmd::run
   2: probe_rs::main
   3: std::sys_common::backtrace::__rust_begin_short_backtrace
   4: std::rt::lang_start::{{closure}}
   5: std::panicking::try
   6: std::rt::lang_start_internal
   7: main
   8: __libc_start_call_main
   9: __libc_start_main@@GLIBC_2.34
  10: _start

Desktop (please complete the following information):
NixOS:
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.44, NixOS, 24.11 (Vicuna), 24.11pre664135.5e0ca22929f3`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Additional context
It works with OpenOCD:
% cat script.cfg
transport select swd
set CHIPNAME at91samd21g18
set CPUTAPID 0x0bc11477
source [find target/at91samdXX.cfg]

adapter srst delay 100
adapter srst pulse_width 100
% openocd -f interface/cmsis-dap.cfg -f script.cfg -c init -c "reset halt" -c "program /mnt/home-bin/mpiechotka/Sources/embassy/examples/atsamd-metro_m0/target/thumbv6m-none-eabi/release/blinky" -c reset -c shutdown
Open On-Chip Debugger 0.12.0
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
adapter srst pulse_width: 100

Info : Using CMSIS-DAPv2 interface with VID:PID=0x2e8a:0x000c, serial=E6614C311B414738
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: Test domain timer supported
Info : CMSIS-DAP: FW Version = 2.1.2
Info : CMSIS-DAP: Serial# = E6614C311B414738
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 0 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : clock speed 400 kHz
Info : SWD DPIDR 0x0bc11477
Info : [at91samd21g18.cpu] Cortex-M0+ r0p1 processor detected
Info : [at91samd21g18.cpu] target has 4 breakpoints, 2 watchpoints
Info : starting gdb server for at91samd21g18.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : [at91samd21g18.cpu] external reset detected
[at91samd21g18.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000c0 msp: 0x20008000
[at91samd21g18.cpu] halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000c0 msp: 0x20008000
** Programming Started **
Info : SAMD MCU: SAMD21G18A (256KB Flash, 32KB RAM)
** Programming Finished **
shutdown command invoked

probe-rs attach works. probe-rs gdb doesn't - but openocd debugger works.

Sorry but I believe this is a duplicate of https://github.com/probe-rs/probe-rs/issues/507
Feel free to reopen if this is a different issue.


contractcourt: log amount if incoming htlc times out

This PR adds logging of the amount of incoming HTLCs when they timeout. This helps to identify HTLCs with sub-dust amount.

Ack


Complete GWAS step

To create dummy files:
generate dummy files to practice
for anc in AFR EUR
do
    mkdir -p ${genotype_processed_dir}/$anc
    for i in {1..22}
    do
        touch ${genotype_processed_dir}/${anc}/${bfile_prefix}${i}.bed
        touch ${genotype_processed_dir}/${anc}/${bfile_prefix}${i}.bim
        touch ${genotype_processed_dir}/${anc}/${bfile_prefix}${i}.fam
    done
done

for anc in AFR EUR
do
    for phen in bmi sbp
    do
        for age in "1-2" "46-50"
        do
            touch ${phenotype_processed_dir}/${phen}_${anc}_${age}.txt
        done
    done
done

There will be many GWASs per cohort and it could amount to a lot of data. Need to think carefully about minimising storage requirements.

Keep SNP info once for all GWAS and then keep only beta, se, n, af per GWAS (in the same order and with no filtering so that it matches the bim file)
could store it in different ways. Quick experiment of storing beta, se, n, af for 10M sips in different formats:

size = 241825823  format = temp.fst
size = 206942953  format = temp.rds
size = 602965124  format = temp.txt
size = 261485887  format = temp.txt.gz
size = 202288623  format = temp100.fst

gzipped text file is the default choice choice. If we store everything in rds format it would be about 25% smaller, but a bit more cumbersome to use. fst is slightly smaller when using maximum compression, so if we were using rds we might as well use fst due to speed improvement

Update on compression - moving to use rds because fst package installation could be challenging


int64 support

need
duk_push_uint64
duk_to_uint64
functions

That would be doable but the API call would not always be available (Duktape doesn't assume that 64-bit C types are available because they are missing from some targets).
But note that because numbers are represented internally as IEEE doubles, pushing an (u)int64 will only preserve integer precision up to 2^53, so what you push and read back won't necessarily be exactly the same.

Since there's no native 64-bit type in Ecmascript, any such API is exactly equivalent to:
duk_push_number(ctx, (double)i64value);

I don't think that adding API surface just to avoid a cast is necessary.

workarround: http://jsfromhell.com/classes/bignumber

I need the support of uint64 function, because my project uesd GUID(uint64), in addition to using string instead, are there any good Suggestions? I'm a c programmer, and not familiar with javascript

There is no int64 type in Ecmascript.  Numbers, by specification, only have as much precision as an IEEE double, so passing the GUID as an integer into Ecmascript code is likely to lose information and corrupt it.  You'll need to pass your GUIDs around as strings or objects, not numbers.  duk_push_uint64() will not solve this.

thank you，duktape is 牛逼

@MarilynDafa guid output is a string can be generated at C and send to Duktape without operations with 64-bit
checkout:
http://stackoverflow.com/questions/105034/create-guid-uuid-in-javascript
https://github.com/dandean/guid
http://guid.us/GUID/JavaScript

@MarilynDafa The clean, portable options are:

Using a string
Using a buffer (duk_push_fixed_buffer(ctx, 8)); memory usage is similar to using a string in practice

If you're guaranteed to be running on a 64-bit target and a void pointer is >= 64 bits, you could also cast the uint64 to a void * and use duk_push_pointer(). Typing-wise this is obviously unclean, but it's more memory efficient than the alternatives.
Longer term I've been looking into alternative tagged value representations which might allow a 64-bit integer to be represented more efficiently - but no concrete design exists for that yet.

Relevant:
https://github.com/tc39/proposal-integer

Having BigInts as a standard would be awesome, as they would be useful in a variety of use cases, and Duktapa already needs to embed a minimal bigint library for double<->string conversions.


TODO: Trim the response suffix when they are identical to the request suffix

Sometimes the models will generate trailing parenthesis even though they are already in the source code.
Can it be done by prompt engineering?

It might be possible to trim the response suffix by implementing "insertion" like this: https://openai.com/blog/gpt-3-edit-insert. I'm not sure if this is already how CopilotForXcode works but I think it is possible with GitHub Copilot as well.

Looks like LlamaCode supports a prompt format that can be used to generate fill-in-the-middle content https://ollama.com/library/codellama

Released in 0.2.0


UX: Streamlined API for the simplest use cases?

We've been using and recommending age for a "small" use cases, like wrapping/unwrapping sensitive material, where there's only one X25519 or passphrase recipient and a tiny amount of data. This is very nice as the users of the software can easily be instructed to use the age CLI to prepare data, and nobody is rolling their own (combination of) crypto.
For this, instead of using things like std::iter::once and the rest of the top-level example in https://docs.rs/age, it would be great to have simplified (not composable) high-level APIs directly in age itself.
I imagine something like fn encrypt(recipient, plaintext: &[u8]) -> Result<Vec<u8>> and fn decrypt(identity, ciphertext) -> Result<Vec<u8>> as top-level library exports, with a few ergonomic additions to construct appropriate identities and recipients, so users can easily decrypt given a passphrase, or encrypt against say a SSH public key, etc.
Is this in scope for the project or do you prefer to stick with the composable parts and let the user figure out how to combine them?

Yeah, this seems useful. The API was simpler in the past, but when the Recipient and Identity traits were introduced in 0.5.0 to replace the earlier enums, the APIs did gain some (needed) complexity.
I do have another significant API refactor planned (to remove the split between recipients and passphrases), but that shouldn't affect an API at this high level.

The refactor mentioned above is #504.

I've added age::{encrypt, encrypt_and_armor, decrypt} functions in #525. Combined with the new age::scrypt module, I think this creates a sufficiently streamlined API for simple use cases.


Fix for race condition due to m_callbacks_running being altered without mutex protection

Fixes #32

Awesome, thanks for your debug work and your merge request!


current_user helper not installing to application_controller if subclassed

The installer injects some code into application_controller, and it uses after: "ActionController::Base" for the injection position. If the application_controller is subclassed, then that search fails and the snippet is not injected. Workaround for now is to add the rad_hoc_user method and helper method manually.

Closing this as we will be pulling Rad Hoc back into Groundswell.


feat: allow author edits and update of profile

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] All commits are signed-off.

New author command: profile.  profile-generate and profile-assemble
given a profile, generate will create markdown for the profile with special editing sections for any Adds that it does.
A user may edit the content and/or add new sections.
Then profile-assemble will load the markdown and replace the adds in the profile with the new content.
In addition, the objective part of a control is written in the same indented and structured format as the statement.
This includes a re-structuring of ControlIO into separate reader and writer classes.
This is a preliminary PR and the documentation needs updating prior to merge, but it is ready for initial review.

I leave the proposed exception handling for CLI commands here. @fsuits @butler54 please take a look, if you agree with the structure we can adopt it more. Here an example of the proposed structure for the author/profile.py:
The proposition is to handle all unexpected exceptions here and return code 1. We also preserve stack-trace for debug purposes.
def _run(self, args: argparse.Namespace) -> int:
        try:
            log.set_log_level_from_args(args)
            trestle_root = args.trestle_root
            if not fs.allowed_task_name(args.output):
                logger.warning(f'{args.output} is not an allowed directory name')
                return 1

            profile_path = trestle_root / f'profiles/{args.name}/profile.json'

            markdown_path = trestle_root / args.output

            return self.generate_markdown(trestle_root, profile_path, markdown_path)
        except Exception as e:
            logger.error(f"Generation of the profile failed with error: {e}")
            logger.debug(traceback.format_exc())
            return 1

example of handling error in methods such as @staticmethod     def assemble_profile(         trestle_root: pathlib.Path, orig_profile_name: str, md_name: str, new_profile_name: str     ) -> int:
Proposition is that we only catch the exceptions that we expect, we let all other unexpected exceptions fall up the call tree.
...
new_prof_dir = trestle_root / f'profiles/{new_profile_name}'
try:
    if new_prof_dir.exists():
        logger.info('Creating profile from markdown and destination profile directory exists, so deleting.')
        shutil.rmtree(str(new_prof_dir))

    new_prof_dir.mkdir()
    orig_profile.oscal_write(new_prof_dir / 'profile.json')

    return 0
except OSError as e:
    raise TrestleError(f'Error while writing profile from markdown to {new_prof_dir}: {e}')
except AnyOtherSpecificError as e:
    raise TrestleError(f"something went wrong: {e}")

@enikonovad @butler54 The suggestions for exception handling make sense - I will add them in here and aim to use them in the future.


How to Integrate Voice Search in Android tv and ios tv

Description
Hi @douglowder  ,This is not a kind of bug ,its more of kind of question , is there any possible way to interate voice search (text to speech using remote) in react native tvos for Android Tv and Ios Tv , Please Provide Some Input Thanks
React Native Version
<EMAIL_ADDRESS>Output of npx react-native info
System:
OS: macOS 13.5
CPU: (8) arm64 Apple M1
Memory: 97.75 MB / 8.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.3.1 - /opt/homebrew/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 9.6.7 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.12.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, watchOS 10.2
Android SDK: Not Found
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.11005911
Xcode: 15.1/15C65 - /usr/bin/xcodebuild
Languages:
Java: 19.0.2 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.0.0 => 18.0.0
react-native: Not Found
react-native-macos: Not Found
react-native-tvos: 0.69.8-0
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
NA
Snack, screenshot, or link to a repository
NA

Hi @douglowder Currently iam using @react-native-voice/voice latest version its bit working fine in android tv but in Apple tv it is not working

I looked at the react-native-voice repo... last release was 2 years ago, and its podspec is configured for iOS only, tvOS is not enabled.

Hi @douglowder  Thanks for the response, so is there any possiblity for tvOS for Voice search

Hi @douglowder  thanks for the response, so is there any key to trigger the voice recognizer programically in tvos


Wrong size configuration of android splashes? same configuration for long and not-long assets

This has been bugging me for a while.. It looks like most (not all) of the android screens sizes in specs.js have the same width and length for both the long and not-long screen resolutions.
E.g.
exports['android-default-notlong-port-xxxhdpi'] = {
[...]
width: 1280,
height: 1920,
[...]
};
exports['android-default-long-port-xxxhdpi'] = {
[...]
width: 1280,
height: 1920,
[...]
};
This looks so obviously wrong that I'm wondering if I am missing something instead.
If you can confirm this is a bug I'll be happy to submit a pull request to fix this.

Yes, that must be wrong although I can't make much of http://docs.appcelerator.com/platform/latest/#!/guide/Icons_and_Splash_Screens-section-29004897_IconsandSplashScreens-PreviousRecommendations either. In the end it's always better to use 9-patch. You'll never be able to serve all devices with regular images.
But if you have a good suggestion for better sizes, please lmk.

Yeah, I think you are right. I thought this was just a mistake, now I see this is a larger problem. 9-patch will do. Thanks


Add [[Phishing]] #malicious GA7MVR…RBKCYT

Address: GA7MVRRFEMBKH2PNEAJGFOWELNJC5BFLUJHKG62OJEUWYMQIJJRBKCYT
Tags: malicious
Title: [Phishing]
Requested by @c0x41lch0x41

Address used to disperse funds from phishing attack. Original addresses are GDLUDZY2M5AB3XQNADDHK43ZFXIJUECOLF2Y2AMKGISYBZHGAQ5EW7QT and GD3EF272CQAA4QJPOGT7RJOVDVRPWVG42TTNHKAAXMRVZBOYI3EJDFHH

@C0x41lch0x41
Please continue discussion on original posting on similar types of problems. Please supply any supporting information about these most likely fradulent accounts and activities. Facts need to be supplied to enable flagging a fradulent address.
https://github.com/stellar-expert/public-directory/issues/202


fix: support make serve on mac os

Unfortunately df -Th . does not work on mac os.
I'm open to other alternatives, however, this seems to work okay.
Signed-off-by: Chris Butler<EMAIL_ADDRESS>

This is an automated message:
You can preview this docs PR at http://485.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.

/ok-to-test


Whether DB.hashSet()  will create a thread safe set?

Hi,
I want to know , Whether DB.hashSet()  will create a thread safe set?
Thank you !

Yes, the HashSet is thread safe


Fix /help: Cannot read properties of undefined (reading 'find')

Bug found in: slash help command
When you search a commands with no options/sub commands bot returns an error:
ERROR: interactionRun: modalResponse.reply is not a function because of the unhandled exeption (when there's no opts)
So I made it optional so in case options doesn't exist it skips finding options
btw, all bot's have this issue

I haven't personally faced this error but anyways these changes won't break the code.
Merging this


TypeError: Converting circular structure to JSON

Im using Firebase in my Query function with a custom Promise
When i click on the query in the React Query Console , it throws this error:

code:

I have a nearly identical queryFn in another component, and it dosent throw the error if i use the RQ Console there.

This is because your data that you are caching contains a circular reference. Unfortunately you would need to remove this  to use the dev tools right now. And honestly I don’t think you would necessarily want the circular reference anyway. They can cause issues with caching and storage.

Thanks for the comment, Tanner!
Meanwhile i found out the glitch in the matrix. If you encounter the same bug, this might help:
Look for parameters, variable declarations, loops etc. that might use the same name as elements from the useQuery-Hook (data, error, etc.) ANYWHERE in that component (one other time i had the problem with using identical variable names in queryFn Tags)
my rather silly mistake
render(
....
{
data.map(
data => ...
)
}
);

Thanks verry much


Are failed onledger transactions returned as success or error in submitTransaction API?

Heres an example of a failed onledger transaction:
Stokenet
https://stokenet-dashboard.radixdlt.com/transaction/txid_tdx_2_1yma9m9p05dqjjj7zuhr6yt7enc9vufhnraxskya02erdh2p0crsqpzkjhg/summary
How are transactions like these returned by the sendTransaction API? Are those returned as success or error? In case of error, which errorType?

It's returned as an error. If you're using sendTransaction from RDT you won't see errorType(for committed transaction) but rather TransactionStatus from the ledger.

Is there documentation on TransactionStatus?
You said its not an error type but I saw there is submittedTransactionHasFailedTransactionStatus, is that maybe what Im looking for or something else?

Ok, first things first - you should most likely be looking at RDT repository rather than this. RDT wraps wallet-sdk with some nicer APIs and does transaction status polling after it's been submitted.
TransactionStatus is defined by gateway-sdk here
As far as I remember submittedTransactionHasFailedTransactionStatus will never occur with recent Radix Wallet versions. It's because Radix Wallet responds to wallet-sdk right after transaction has been submitted (Radix Wallet doesn't yet know if transaction has been accepted or rejected). After receiving transactionIntentHash we can check the status ourselves - by querying Gateway API.
sendTransaction in wallet-sdk successful response contains transactionIntentHash which is later used by RDT to poll for actual transaction status (code here).

@dcts coming back to original question because I might have introduced some misunderstanding
Transaction like the one you've linked will be returned as success from wallet-sdk (because it has been submitted) but as an error from radix-dapp-toolkit (after polling we see it's committed failure).
submittedTransactionHasFailedTransactionStatus can occur if the wallet fails to submit a transaction (name is misleading)

Thanks a lot for detailed explenation!


Update aws-java-sdk-dynamodb to 1.12.762

About this PR
📦 Updates com.amazonaws:aws-java-sdk-dynamodb from 1.11.1034 to 1.12.762
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-dynamodb" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #591.


Fix for starting a single-use daemon when client has low memory

The previous logic was testing whether the daemon parameters had
a memory setting, but not whether that setting was the default or
whether it actually came from the user. The default settings are
ignored for the purpose of forking a single-use daemon, so they
also need to be ignored in the decision whether the current VM
has enough memory.

I've added an integration test and also adjusted the unit test. It didn't catch the problem before because it was actually testing for the scenario where the user explicitly requests an empty list of JVM args. What we care about is the scenario where the user doesn't pass JVM args at all though.


Use user's specified config rather than default_config

There's a small issue in the SQS code in which the default_config is being used rather than the one the user provided in the request. I believe that my edit reflects the original intention.

Thanks for the fix.


CSS test failure: Using PUT in existing container › is disallowed without accessTo Write or Append

Using CSS v1.0.0.
Given an .acl of
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.

<#authorization>
    a               acl:Authorization;
    acl:agent       <http://test.com/card#me>;
    acl:mode        acl:Read;
    acl:mode        acl:Control;
    acl:accessTo    <./>.

and a quick modification to authenticate as as http://test.com/card#me:
--- a/config/ldp/authentication/dpop-bearer.json
+++ b/config/ldp/authentication/dpop-bearer.json
@@ -6,6 +6,10 @@
       "@id": "urn:solid-server:default:CredentialsExtractor",
       "@type": "WaterfallHandler",
       "handlers": [
+        {
+          "@type": "UnsecureConstantCredentialsExtractor",
+          "agent": "http://test.com/card#me"
+        },
         {
           "@type": "DPoPWebIdExtractor",
           "originalUrlExtractor": {

then the request is correctly denied:
% curl -H "Content-Type: application/json" -T package.json http://localhost:3000/src/package.json -i
HTTP/1.1 100 Continue

HTTP/1.1 403 Forbidden
Vary: Accept,Authorization,Origin
X-Powered-By: Community Solid Server
Updates-Via: ws://localhost:3000/
Access-Control-Allow-Origin: *
Access-Control-Allow-Credentials: true
Access-Control-Expose-Headers: Accept-Patch,Link,Location,MS-Author-Via,Updates-Via,WAC-Allow
Accept-Patch: application/sparql-update
Allow: OPTIONS, HEAD, GET, PATCH, POST, PUT, DELETE
MS-Author-Via: SPARQL
Content-Type: text/markdown
Date: Thu, 12 Aug 2021 10:35:24 GMT
Connection: keep-alive
Keep-Alive: timeout=5
Transfer-Encoding: chunked

# Access not allowed
You are logged in, but not allowed to access this resource.

Try requesting access or logging in with a different identity.

## Technical details
_No further details available._

Hence the test Using PUT in existing container › is disallowed without accessTo Write or Append might be broken for other reasons.
To easily test, make the modification above and start with npm start -- -c config/file.json so you can modify the ACL file on disk.

Right, the problem is the test title: https://github.com/solid/web-access-control-tests/blob/6d5b15f8a4020dc554c16d15270a74f73fc37f10/test/surface/create.test.ts#L375
It's actually testing

Having acl:Control does not imply that the agent has acl:Read or acl:Write access to the resource itself, just to its corresponding ACL resource.

So would be good for the test to reflect that.

I'll have a look! I think the test in question is this one.

The ACL used in this test is:
@prefix acl: <http://www.w3.org/ns/auth/acl#>.

<#alice> a acl:Authorization;
  acl:agent <https://solidtestsuite.solidcommunity.net/profile/card#me>;
  acl:accessTo <http://localhost:3000/web-access-control-tests-1628767900725/7/allOtherModes/>;
  acl:default <http://localhost:3000/web-access-control-tests-1628767900725/7/allOtherModes/>;
  acl:mode acl:Read, acl:Write, acl:Control.
<#bobAccessTo> a acl:Authorization;
  acl:agent <https://solid-crud-tests-example-2.solidcommunity.net/profile/card#me>;
  acl:accessTo <http://localhost:3000/web-access-control-tests-1628767900725/7/allOtherModes/>;
  acl:mode acl:Read, acl:Control.
<#bobDefault> a acl:Authorization;
  acl:agent <https://solid-crud-tests-example-2.solidcommunity.net/profile/card#me>;
  acl:default <http://localhost:3000/web-access-control-tests-1628767900725/7/allOtherModes/>;
  acl:mode acl:Read, acl:Append, acl:Write, acl:Control.

I'll see if I can adapt your one to resemble it more closely.

I reproduced that with your steps it returns 403.
Really nice trick by the way with the "UnsecureConstantCredentialsExtractor", super handy for debugging WAC!
But then if you append a second Authorization to src/.acl so that it becomes:
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.

<#authorization>
    a               acl:Authorization;
    acl:agent       <http://test.com/card#me>;
    acl:mode        acl:Read;
    acl:mode        acl:Control;
    acl:accessTo    <./>.

<#authorization2>
    a               acl:Authorization;
    acl:agent       <http://test.com/card#me>;
    acl:mode        acl:Read;
    acl:mode        acl:Append;
    acl:mode        acl:Write;
    acl:mode        acl:Control;
    acl:default    <./>.

You see that the server returns 205 instead of 403, even though accessTo Write or Append is still not given.
Note that default Write and default Append are given, but accessTo Write and accessTo Append are not.

I think the server may be implementing the "default Write implies accessTo Write" behaviour that Inrupt proposed in August 2020. This behaviour was implemented in ESS at the time.
But after some (long) discussion, we concluded that it was a misinterpretation of the spec, and so I don't think this is a bug in the tests.

Thanks, that helps a lot. I was not aware of that discussion.
Nonetheless, I am unsure whether the intended behavior is to allow or disallow:

When an operation requests to create a resource as a member of a container resource, the server MUST match an Authorization allowing the acl:Append or acl:Write access privilege on the container for new members.

Minimal example
@prefix acl: <http://www.w3.org/ns/auth/acl#>.
@prefix foaf: <http://xmlns.com/foaf/0.1/>.

<#authorization>
    a               acl:Authorization;
    acl:agent       <http://test.com/card#me>;
    acl:mode        acl:Write;
    acl:default     <./>.

Let us check the conditions:

an operation requests to create a resource ✅
an Authorization allowing acl:Write ✅
on the container for new members ❓

Does "on the container for new members" mean:

"on the container" (so acl:accessTo)
or "for new members" (so acl:default)

@csarven Do you know what the language on the container for new members is intended to mean, and should it be clarified?
I see traces in the ACL ontology to support the second interpretation, but unsure:
    acl:default     a rdf:Property;
         :comment """If a resource has no ACL file (it is 404),
        then access to the resource if given by the ACL of the immediately
        containing directory, or failing that (404) the ACL of the recursively next
        containing directory which has an ACL file.
        Within that ACL file,
        any Authentication which has that directory as its acl:default applies to the
        resource. (The highest directory must have an ACL file.)
""";
         :domain acl:Authorization;
         :label "default access for things in this" .

    acl:defaultForNew     a rdf:Property;
         :comment """THIS IS OBSOLETE AS OF 2017-08-01.   See 'default'.
        Was: A directory for which this authorization is used for new files in the directory.""";
         :domain acl:Authorization;
         :label "default access for new things in the object" .

OK, we may need to clarify a few things with this issue. The test data does need to include both accessTo and default. It originally included both, but in chat I suggested to remove default based on my understanding of the test/issue ( https://gitter.im/solid/test-suite?at=6114fb1b29b165332e719857 ). But now I think that it should've been the other way around i.e. we want to match an Authorization rule with default because the request is PUT /package.json and not to PUT /. Sorry, I've misread the issue/test.
For PUT package.json, the following is required (as you've noted above):
@prefix acl: <http://www.w3.org/ns/auth/acl#>.

<#authorization>
    a               acl:Authorization;
    acl:agent       <http://test.com/card#me>;
    acl:mode        acl:Write;
    acl:default     <./>.

The text in the title of this issue takes the requirement from the specification but it is inaccurate in context of PUT.
#http-method-access-mode-mapping clarifies this. The relevant part:

As the HTTP PUT method requests to create or replace the resource state, the acl:Write access mode would be required.

That's also hinted at the beginning of the section in #http-crud (for write operation).
Aside: I'm just clarifying what's relevant here. I'd rather not discuss POST, acl:Append, or operations in general now... :)
Any way, you're on the right track in your last example code above.

Nonetheless, I am unsure whether the intended behavior is to allow or disallow:

When an operation requests to create a resource as a member of a container resource, the server MUST match an Authorization allowing the acl:Append or acl:Write access privilege on the container for new members.

The intended behaviour is that matches grant access, as per #authorization-evaluation-applicable :

The evaluation of an authorization is concerned with finding Authorizations that match the required parameters of an operation (Authorization Conformance). Evaluation stops when all access permission requests have been granted by one or more Authorizations. Authorizations that do not match a required access permission have no effect on the outcome of the evaluation. Access is granted when conforming Authorizations are matched, otherwise access is denied.

What's intended with "on the container for new members" is acl:default <./> (Working with #effective-acl-resource and #acl-default :

The acl:default predicate denotes the container resource whose Authorization can be applied to a resource lower in the collection hierarchy

The focus of #reading-writing-resources is access modes, so the requirement didn't explicitly call other combinations that can be in an Authorization rule. Typically there is no ACL resource for a non-existing resource, but the WAC spec doesn't prohibit that. (If there is an ACL resource for a non-existing, server would apply that as usual, i.e., it'd try to match accessTo). So, PUT /package.json (to create/replace) needs to find a container's ACL resource with default, when there is no ACL resource associated with package.json.
With that understanding, I think "for new members" may be imperfect but reasonable - also consistent with the definitions in the ontology. I can also see it working if we omit "for new members" from the requirement. In any case, happy review/incorporate quick suggestions here without major departures.

Perhaps worthwhile to note the following in the example request - I can't say for certain if that's accurate.
Content-Type: text/markdown

Thanks for the extended explanation, @csarven.
This means the bug in the test suite is confirmed.
I have opened https://github.com/solid/specification/pull/297 to suggest slight clarifications to the wording.

I don't think the test is wrong, but let's see if we can explain it better to implementers. That is a task of the spec; once an implementer has read the spec, no test should come as a surprise to them.
I'll talk it through with @csarven next week.
Will leave this issue open for now.

@csarven I think you're forgetting about the permission to create the containment triple. Let's discuss further on the spec issue, I commented there.
This test is working as intended, so closing this here.

Thanks @RubenVerborgh @michielbdejong ! It seems I've been thoroughly confused in this issue multiple times. I couldn't get to the bottom of what's actually being tested but that's not an excuse for my response. I have discussed the requirement many times in detail elsewhere and even documented the consensus that was reached. Somehow I responded to the descriptions we are analysing instead of what's actually documented, e.g. https://github.com/solid/specification/issues/14#issuecomment-683480525 draws from many issues, and for PUT:

Create requires Append (or Write) on C/ and Write on C/R.

As far as I know there are three ways that a match can occur, and I'll quote from a comment:
Two [Authorization rules] in container's ACL document:

accessTo C/
mode Append (or Write)
default C/
mode Write

OR

Single [Authorization rule] in container's ACL document:
accessTo C/
default C/
mode Write

OR (again note that this is only possible if a server pre-associates an ACL resource - I suggest to not test this!)

Single [Authorization rule] in container's ACL document:
accessTo C/
mode Append (or Write)
Single [Authorization rule] in contained resource's ACL document:
accessTo C/R
mode Write

The background that I gave in the previous comment was accurate but I did indeed overlook the permission on container's own space. Thanks for the nudge @michielbdejong with "permission to create the containment triple"! But to be accurate, it is not actually about the containment triple - that's not a WAC requirement - but instead just having permission to container's URI space.

CSS is still failing these 6 tests in both the main and the version/2.0.0 branch, see  https://github.com/solid/community-server/issues/902#issue-968511525

We prefer to examine whether the spec behavior is correct rather than blindly implementing things. See https://github.com/solid/web-access-control-spec/issues/97 and https://github.com/solid/web-access-control-spec/issues/98
Reporting this actual status would be more correct than writing "CSS is getting very close to a correct implementation"; provided of course that the goal of this test suite would be correctness, and that its reported scores would be a representative measure thereof.

Thanks for linking to those issues. They sound like one proposed spec change and one proposed clarification. Unless I misinterpreted them, neither of them sound like actual disputes where the community disagrees about the spec behavior.
We have consensus about what the spec behavior is, there is no dispute (note that a proposal for change is different from a dispute, and text improvements are also different from disputes).
I do hope that apart from the good work you're doing proposing spec changes and proposing spec text improvements, the CSS team will also still commit to implementing the spec behavior about which we currently have a consensus.
Thanks!

These same tests are still failing in CSS v1.1, I just checked.

We know; CSS is configured to.
As written above, we wait for https://github.com/solid/web-access-control-spec/issues/97 to be resolved.

Testing this in CSS v2.0.1 now.

CSS v2.0.1 will have the exact same behavior; we have tests verifying this behavior.
We wait for solid/web-access-control-spec#97 to be resolved.

Fair enough! Vote with your code. :)


Always whole lines showing, regardless of the selection

In visual block and visual line mode, the screenshot shows the whole lines and in the last line up to the cursor, not what is actually selected.

Hi @marqmitk, thx for your bug report and PRs again! normally code always shows line-by-line, as a code snapshot plugin, is block-visual features snapshot really necessary?

good point, thought the same thing already, only reason i would find it useful is for consistency, so if its not implemented i would add a notification that it doesn't work or just remove it from the modes that trigger the preview. but you are right that its not really useful for sharing code

I think block-visual may not be for code snapshot, maybe we can add notification about visual block not work at document, and if more suitable scenario about visual block found, then reopen this issue and consider to implement it, how do you think?

Hi @marqmitk, would you want to maintain this project with me? if you want I will add you to collaborators of this project 😉


image builds of master are failing

The changes from #795 are causing image builds of master to fail.  I haven't had a chance to look at why, but I think it's probably an easy fix.  I'll get to it later today or tomorrow if someone else doesn't take it first.
cc @carlisia @nrb @wwitzel3

I'll start looking


Removed scalar and index fields

Closes #70

SEQ table before:

and after

Unless I've misunderstood something, there are still references left to both SCALAR and INDEX records in the codebase. A short list includes:
* `TableUpdater.table_scalar_records`

* In test_tables.py `table_updater` contains `updater.index_record` mocking.

Please check through all occurrences of the word "scalar" and "index" to ensure all references have been cleaned up.

Apologies accidentally didn't push some work before I asked Tom for review.


Feature/add wordle

PR 설명
연결된 issue (없다면 issue부터 만들기)
#19

Codecov Report

Merging #20 (545ed5c) into master (2f45055) will decrease coverage by 0.37%.
The diff coverage is 96.15%.

@@            Coverage Diff             @@
##           master      #20      +/-   ##
==========================================
- Coverage   97.84%   97.47%   -0.38%
==========================================
  Files           5        6       +1
  Lines          93      119      +26
==========================================
+ Hits           91      116      +25
- Misses          2        3       +1

Impacted Files
Coverage Δ

wordle_py/wordle.py
90.00% <90.90%> (+1.11%)
:arrow_up:

tests/TestCase_wordle.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Ensuring tyro.cli produces objects with consistent serialization

Context
I need to ensure that objects pickle/serialize to consistent values (because I am using a library that strongly depends on this).
Finding
But I found that this was not the case for the following example.
python test.py --a hello --b hello
For test.py:
import sys, dataclasses, pickle, tyro

@dataclasses.dataclass
class Args:
    a: str
    b: str

if __name__ == "__main__":
    args = Args(a="hello", b="hello")

    assert sys.argv[1:] == ["--a", "hello", "--b", "hello"]
    args_from_cli = tyro.cli(Args, args=sys.argv[1:])
    args_from_list = tyro.cli(Args, args=["--a", "hello", "--b", "hello"])

    print(pickle.dumps(args_from_cli) == pickle.dumps(args))  # False
    print(pickle.dumps(args_from_list) == pickle.dumps(args))  # True

I found that this issue originates from this more primitive setting.
argv_list = ["test.py", "--a", "hello", "--b", "hello"]
assert sys.argv == argv_list

print(pickle.dumps(sys.argv) == pickle.dumps(argv_list))
# False

I believe this is because argv_list is compiled, but sys.argv is loaded dynamically at runtime. We can see that the repeated "hello" has the same address for argv_list but not sys.argv (due to this compiled optimization).
print(id(sys.argv[2]) == id(sys.argv[4]))  # False
print(id(argv_list[2]) == id(argv_list[4]))  # True

Solution
This is resolved if we forcefully evaluate the sys.argv expression dynamically at runtime! So we can use eval(str(sys.argv)) instead, like:
print(pickle.dumps(eval(str(sys.argv))) == pickle.dumps(argv_list))
#True

args_from_cli = tyro.cli(Args, args=eval(str(sys.argv[1:])))
print(pickle.dumps(args_from_cli) == pickle.dumps(args))  # True

In this PR, I just processed the args with eval(str( ... )) in the tyro CLI.
Please let me know if that was clear and what you think!
Co-credits: @maxzuo!

Thanks for the PR + detailed explanation @apoorvkh @maxzuo!
Do you think it's addressing the root cause of the issue here?
The behavior you're seeing seems to be the result of interning (where immutable constants are merged into the same object) and the way Pickle translates that into object sharing.
As a result, there are numerous cases where we can see similar inconsistencies without even using tyro. A simple one:
import pickle

if __name__ == "__main__":
    args1 = dict(a="1", b="1")
    args2 = dict(a="1", b=str(1))
    print(args1 == args2)  # True
    print(pickle.dumps(args1) == pickle.dumps(args2))  # False

Since the cause (to me) looks like interning, if we take the first example you listed and swap:
args = Args(a="hello", b="hello")

for
args = Args(a="hello", b="hello "[:-1])

, the solution in this PR will also break.
Perhaps inheriting from DetHashWithVersion in the config dataclass and then overriding det_hash_object() (as, for example, return str(self)) would be more robust?


New-MarkdownCommandHelp -Command accepts wildcards but only processes first file

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.

Steps to reproduce
New-MarkdownCommandHelp -Command accepts wildcards but only processes first file. Also, if the intent is to support wildcards then we need to add the [SupportsWildcard()] attribute.
PS> gcm *-pssession

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Cmdlet          Connect-PSSession                                  <IP_ADDRESS>0  Microsoft.PowerShell.Core
Cmdlet          Disconnect-PSSession                               <IP_ADDRESS>0  Microsoft.PowerShell.Core
Cmdlet          Enter-PSSession                                    <IP_ADDRESS>0  Microsoft.PowerShell.Core
Cmdlet          Exit-PSSession                                     <IP_ADDRESS>0  Microsoft.PowerShell.Core
Cmdlet          Export-PSSession                                   <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          Get-PSSession                                      <IP_ADDRESS>0  Microsoft.PowerShell.Core
Cmdlet          Import-PSSession                                   <IP_ADDRESS>    Microsoft.PowerShell.Utility
Cmdlet          New-PSSession                                      <IP_ADDRESS>0  Microsoft.PowerShell.Core
Cmdlet          Receive-PSSession                                  <IP_ADDRESS>0  Microsoft.PowerShell.Core
Cmdlet          Remove-PSSession                                   <IP_ADDRESS>0  Microsoft.PowerShell.Core

PS> New-MarkdownCommandHelp -Command *-PSSession -OutputFolder .

    Directory: D:\Git\PS-Src\platyPS\v2docs\test\Microsoft.PowerShell.Core

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a---           8/21/2024  2:36 PM          34539 Connect-PSSession.md

Expected behavior
Should create markdown for all matching commands.

Actual behavior
Only creates markdown for first match.

Error details
No response
Environment data
Microsoft.PowerShell.PlatyPS v2 branch commit 27d5ffe

Visuals
No response

Signature of parameter set changed in OPS10. -Command was replaced by -CommandInfo. Wildcards don't apply anymore.


Thunbernail figure missing when gallery_dirs is not None

Hi @Chilipp ,
Thank you very much for the great work you did!
I encountered a bug when I set up gallery_dirs to a not None value.
My example_gallery_config variable is below:
example_gallery_config = {
     'examples_dirs': '../notebooks/',   # path to your example scripts
     'gallery_dirs': 'source/notebooks/',  # path to where to save gallery generated output
     'pattern': '0.+.ipynb',
     'dont_preprocess': True,
     'toctree_depth':2,
}

When I run make html, I got these warning:
1233]± make html                                                                                ✹ ✚ ✭ 17:15:29
Running Sphinx v3.5.1
/home/lhoupert/miniconda3/envs/th_routing/lib/python3.9/site-packages/sphinx_nbexamples/__init__.py:1165: RemovedInSphinx40Warning: The app.add_stylesheet() is deprecated. Please use app.add_css_file() instead.
  app.add_stylesheet('example_gallery_styles.css')
loading pickled environment... done
[NbConvertApp] WARNING | Config option `kernel_spec_manager_class` not recognized by `NbConvertApp`.
Scaling ./images/01_network.png to thumbnail ./images/thumb/gallery_._01_generate_network.ipynb_thumb.png
[NbConvertApp] WARNING | Config option `kernel_spec_manager_class` not recognized by `NbConvertApp`.
Scaling ./images/02_best_route.png to thumbnail ./images/thumb/gallery_._02_compute_best_route.ipynb_thumb.png
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 10 source files that are out of date
updating environment: 0 added, 1 changed, 0 removed
reading sources... [100%] notebooks/index
/media/lhoupert/home_w10/Work/Dev/Python/th_routing/docs/source/notebooks/index.rst:25: WARNING: image file not readable: source/notebooks/images/thumb/gallery_source_notebooks_01_generate_network.ipynb_thumb.png
/media/lhoupert/home_w10/Work/Dev/Python/th_routing/docs/source/notebooks/index.rst:40: WARNING: image file not readable: source/notebooks/images/thumb/gallery_source_notebooks_02_compute_best_route.ipynb_thumb.png
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [100%] th_routing_readme
generating indices... genindex py-modindex done
highlighting module code... [100%] th_routing.tools
writing additional pages... search done
copying images... [100%] notebooks/images/01_generate_network_1.png
copying downloadable files... [100%] notebooks/02_compute_best_route.ipynb
copying static files... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded, 2 warnings.

I got particularly these two warnings:
/media/lhoupert/home_w10/Work/Dev/Python/th_routing/docs/source/notebooks/index.rst:25: WARNING: image file not readable: source/notebooks/images/thumb/gallery_source_notebooks_01_generate_network.ipynb_thumb.png
/media/lhoupert/home_w10/Work/Dev/Python/th_routing/docs/source/notebooks/index.rst:40: WARNING: image file not readable: source/notebooks/images/thumb/gallery_source_notebooks_02_compute_best_route.ipynb_thumb.png

It seems that the programme seems to be searching the images in docs/source/notebooks/source/notebooks/images/thumb  instead of docs/source/notebooks/images/thumb.
Then the results is that the thumbnail figures are not available.
I found a quick fix by copying my directory images/thumb into a folder docs/_build/html/notebook/source/notebooks/images/thumb
If you tell me where the I can fix the code that generate the figure path in the index.rst, I am happy to do a PR
Thanks,
loïc

Any idea @Chilipp ?

Hey @lhoupert! my apologies for the delay! Unfortunately I do not have resources at the moment to work on sphinx-nbexamples and I'd like to deprecate it anyway (https://github.com/Chilipp/sphinx-nbexamples/issues/17#issuecomment-782036624).
My honest apologies for these troubles. I recommend you to move to nbsphinx. Or do you think it makes sense to transfer the sphinx-nbexamples to a public space, such as sphinx-contrib?


[core] Add react-is dependency

This dependency is called in Menu.js but is not listed in package.json
I detected this problem when I runned a project with yarn berry (v2) using pnp.
The Menu.js component is using 'isFragment' function from the react-is library.
The only package.json that have react-is is in @material-ui/utils.
This change is also related to the #17317

packages/material-ui-lab/package.json needs it as well

I also noticed that material-ui-utils is using react 16.8.0 and react-utils 16.8.6. Is this wanted or it's an issue ? @eps1lon eps1lon

@HeadFox It's a great first pull request on Material-UI 👌🏻. Thank you for working on it!

I'm using material-ui since the v1 ! I'm so happy to be able to contribute now 😄

@HeadFox awesome.
If you could change, add, or remove one thing in the framework, what would it be?


Setting to disable Twitter or Facebook login

Hey, folks! Telescope has changed a lot in the past months, and there is a new React-based version, Telescope Nova (intro video).
The Legacy version is no longer supported, I'm closing this issue. I invite you to check the new version, it's awesome!
Like @Kikobeats pointed out, you can remove/add the accounts packages to disable/enable it. And also you'll need to edit settings.json to add your credentials.
Happy hacking! 🚀
Ps: by the way, don't hesitate to join the Slack and ask any question, you are welcome! 👍


zfs.block_mode should be honored when containers are copied or moved between different storages

This issue is opened from #3873
I have a lxd server with 2 storages:
The old one: with LVM controller (where I run all my non zfs compatible containers)
The new one: with ZFS driver, zfs.block_mode = true
When I copy or move containers from LVM storage to ZFS storage, the zfs.block_mode flag is not honored and the containers are created on ZFS storage as a dataset.
Also if I export containers from the LVM storage and I import them into ZFS storage they are created as dataset instead of zvols.
I understand that “existing instances using datasets will not be converted to zvols” when they are copied or moved between zfs storages, but why zfs.block_mode = true can’t be honored when storages use different drivers?
I found no way to migrate my db/docker containers (that are not compatible with zfs datasets) from LVM to ZFS, and create all of them from scratch is not an option, is there any solution?
I also found this function useless on clusters with different storage and different controllers, because if you mistakenly move a container configured with block mode to a non-zfs storage, you can never go back to zfs block mode.
Regards

Fixed by #11771


GDAL 2.0

In Fedora, we are slowly moving towards GDAL 2.0 and Fiona's tests suite seems to fail a lot. Is this simply because GDAL 2.0 is not supported, or are we doing something wrong?
The build and test log can be found here (search for Executing(%check):).
If GDAL 2.0 is currently not supported, is it at least planned? And if so, is there a schedule (+ maybe something I can help with)?
Thanks

@hroncok GDAL 2.0 has features that I'm looking forward to using, for sure, but neither Fiona nor Rasterio are currently developed with an eye to GDAL 2.0. I imagine that we'll introduce 2.x branches of these that require GDAL 2.x. Let's talk about scheduling this work later this summer. In the meanwhile, I very much appreciate any notes that you have. Summaries are especially useful!

I don't have any notes, just an observation. Most tests fail with
IndexError: list index out of range

I would say this doesn't look too bad. Obviously a lot is broken, but it's not everything! I wonder if anyone has written a guide to porting to GDAL 2.0 already. If not, it wouldn't hurt for us to keep notes and share with others.
============================= test session starts ==============================
platform darwin -- Python 3.4.3 -- py-1.4.26 -- pytest-2.7.0
rootdir: /Users/snorf/Desktop/gdal2/Fiona, inifile:
collected 517 items

tests/test_bounds.py ....
tests/test_bytescollection.py FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
tests/test_cli.py FFF.
tests/test_collection.py .............................FF..F.FF..F.....FFFFFF...........F.........
tests/test_crs.py ..........
tests/test_drivers.py .
tests/test_feature.py .......
tests/test_fio_bounds.py ...........
tests/test_fio_cat.py FF.FF......F
tests/test_fio_load.py .....
tests/test_geojson.py F.
tests/test_geometry.py .........................
tests/test_geopackage.py ss
tests/test_layer.py ..............FF..F.FF..F.....FFF...............FF..F.FF..F.....FFF..............FF..F.FF..F.....FFF..
tests/test_listing.py ....FF......
tests/test_multiconxn.py F......
tests/test_non_counting_layer.py ......
tests/test_props.py ...
tests/test_read_drivers.py ..
tests/test_revolvingdoor.py F
tests/test_rfc3339.py ...........
tests/test_schema.py .FF
tests/test_slice.py FFFFF.
tests/test_unicode.py ...
tests/test_vfs.py ..............FF..F.FF..F.....FFF..............FFF..F.FF..F.....FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

It seems most of the errors were being caused by the new 64-bit integer type:
https://github.com/snorfalorpagus/Fiona/tree/gdal2
From FAILED (errors=94, failures=9), to: FAILED (errors=2, failures=1)
The remaing issues seem to be with encodings (see #153) and OGR_DS_SyncToDisk.

The issue with OGR_DS_SyncToDisk appears to be related to laundering of field names. The tests in test_schema.py trigger an issue because some of the field names are more than 10 characters (the limit for ESRI Shapefiles). I'm not sure why the old code doesn't work here. It seems to, until it comes to writing the data.

BTW  http://svn.osgeo.org/gdal/branches/2.0/gdal/MIGRATION_GUIDE.TXT

As mentioned by @johanvdw in https://github.com/Toblerity/Fiona/issues/259#issuecomment-149126324, Debian is also considering moving to GDAL 2.0.
The build failure of the fiona package is tracked in Debian Bug #802808, in which you can also find the build log.

@sebastic  Support for gdal 2.x is worked on in this PR: https://github.com/Toblerity/Fiona/pull/275
The missing piece is to add support for platforms not supporting gdal-config in setup.py.

Update: 1.7b1 is on PyPI now. See https://github.com/Toblerity/Fiona/issues/289.


Develop (Fixed overlapping of time text in Export Transaction Activity)

Issue pic (At Time 3:56:15 PM was hiding)

Fixed this issue

Thanks for the PR. But it cannot be merged in its current form.
I left some comments in the code review on what could be improved.


update lava

Just an update to latest lava...

Interesting warning that was already before the update:
14>------ Build started: Project: lava-extras.raytracing, Configuration: Release x64 ------
14>Building Custom Rule C:/code/thelavablock_lava-rt/liblava-extras/CMakeLists.txt
14>acceleration_structure.cpp
14>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29910\include\functional(13,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\ext\liblava\liblava/core/types.hpp(9,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\ext\liblava\liblava/core/math.hpp(7,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\ext\liblava\liblava/base/base.hpp(7,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\ext\liblava\liblava/base/memory.hpp(9,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\ext\liblava\liblava/base/device_table.hpp(7,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\ext\liblava\liblava/base/device.hpp(7,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\liblava-extras\liblava-extras/raytracing/acceleration_structure.hpp(4,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)
14>C:\code\thelavablock_lava-rt\liblava-extras\liblava-extras\raytracing\acceleration_structure.cpp(2,1): warning C4103: alignment changed after including header, may be due to missing #pragma pack(pop)

Thanks, appreciate it!
That warning is possibly a known bug: https://developercommunity.visualstudio.com/t/warning-c4103-in-visual-studio-166-update/1057589 There is no pragma pack going on inside lava or my code here, and it definitely wasn't there last time I compiled this 3 months ago

Ok, I guess so, but if you change the include order like this:
#include <liblava/base/device.hpp>
#include <liblava/resource/buffer.hpp>
#include <memory>
#include <vector>

// clang-format off

#include <glm/mat4x3.hpp>

// clang-format on

The warning disappears. Very strange
It is probably not so important, maybe it will be fixed in glm
Another had a similar problem (but the other way round): https://github.com/electronicarts/EASTL/issues/420


Redirect Routes

Acceptance Criteria

[ ] When clicking edit on a GenericWork, it should redirect you to GenericWorkResource.
[ ] Clicking save on GenericWorkResource should go to the GenercWorkResource controller #create
[ ] ref GBH

Notes
This aids with transitioning an application onto valkyrie's data storage

deployed to https://hyku-staging.notch8.cloud/


Content warnings for video

Examples of warnings, from a fairly random site https://www.kapwing.com/resources/use-this-free-template-to-add-a-content-warning-to-any-video/:

Violence, blood, or graphic images
Bright, fast flashes and colors for people who suffer from photosensitive epilepsy.
Dizzying movements that may be disorienting or nauseating. These may be uncomfortable for individuals with certain types of vertigo.

Here's what Netflix say about theirs, for users:
https://help.netflix.com/en/node/2064
For "partners":
https://partnerhelp.netflixstudios.com/hc/en-us/articles/360057622133-Photosensitive-Epilepsy-Guidelines-What-Can-I-Do-If-My-Content-Fails-

Can the PII issue #12 fit with this one?

We have an existing CV for the purpose of content warnings: https://cv.iptc.org/newscodes/contentwarning/ maybe we should review the list?

We found the MDDF list of national/territory ratings systems: https://www.movielabs.com/md/ratings/v2.4.8/html/Summary.html
It looks like we need a field to store one or more national/territory ratings, used for compliance, and separately to track warnings based on the content itself.

For territory ratings, we have #21, so let's focus on content warnings.
For the field, how about the following:

Property Group
Property Name
Definition / Semantics
User Notes
Change Notes
Basic Type/Cardinality
EBUcore Property
XMP Property

administrative
Content Warning
Information to warn potential viewers about nudity, violence etc in the video

New 1.4
CV Term structure (0..unbounded)
n/a
Iptc4xmpExt:ContentWarning

For the CV, here's what we have in our CV vs other systems:

IPTC contentwarning CV
Getty
BBC [source]

Death
Death
Violence

Language
Profanity
Language

Nudity
Nudity
Sex/Nudity

Sexuality
Suggestive Content
Sex/Nudity

Suffering
Graphic Content
Upsetting or disturbing content

Violence
Graphic Content
Violence

Adult Humour / Adult Themes

Drugs / Imitation / Medical scenes

RFI - Flashing Images

So perhaps we should add drugs and flashing images. Do we need "adult humour"?

Resolved with the release of VMHub v1.4


can columnDefinition have common title??

I want to merge some Columndefintion under a single heading. For this I assign same title to the columndefinition it worked but it is throwing warning .Warning: flattenChildren(...): Encountered two children with the same key, CommonTitle. Child keys must be unique; when two children share a key, only the first child will be used`.Because columndefintion is generation key with this title.below is my code.
          <RowDefinition>
              <ColumnDefinition id="someid1" width={30}  title="CommonTitle"
                                                customComponent={customComponent1} />
              <ColumnDefinition id="someid2"  width={30} title="CommonTitle"
                                                 customComponent={customComponent2} />
              <ColumnDefinition id="someid3"  width={30} title="CommonTitle"
                                                  customComponent={customComponent3} />
          </RowDefinition>

This should work in the next version (1.0.3) - Please feel free to follow up if there are any problems.


Fully qualify objects by adding {{node.database}} in sql_builders.sql

Description
dbt-unit-testing assumes a single database should be used throughout the session. However, this raises issues when, for instance, the source data is located in another database than the one defined in the dbt profile. This is probably specific to Snowflake, where multiple databases are commonly used to separate source data from modeled data.
Example
profiles.yml
snowflake:
  target: ci
  outputs:
    ci:
      type: snowflake
      database: CI
      ...

sources.yml
version: 2

sources:
  - name: product
    database: raw
    schema: product
    tables:
      - name: users

tests.sql
{{ config(tags=['unit-test']) }}

{% call dbt_unit_testing.test('stg_users',) %}
  {% call dbt_unit_testing.mock_source('product', 'users') %}
    ...
  {% endcall %}
  {% call dbt_unit_testing.expect() %}
   ...
  {% endcall %}

{% endcall %}

dbt-unit-testing will raise this error because it is unable to find raw.product.users:
19:25:11    Source users columns must be declared in sources.yml, or it must exist in database
19:25:11
19:25:11    > in macro fake_source_sql (macros/sql_builders.sql)
19:25:11    > called by macro build_node_sql (macros/sql_builders.sql)
19:25:11    > called by macro mock_input (macros/tests.sql)
19:25:11    > called by macro mock_source (macros/tests.sql)
19:25:11    > called by macro test (macros/tests.sql)
19:25:11    > called by test test_stg_users (tests/tests.sql)
19:25:11    > called by test test_stg_users (tests/tests.sql)

This is because it looks for users in the same database as the one defined in profiles.yml, not the database defined in sources.yml, as shown by the compiled Snowflake query:
select distinct
            table_schema as "table_schema",
            table_name as "table_name",

            case table_type
                when 'BASE TABLE' then 'table'
                when 'EXTERNAL TABLE' then 'external'
                when 'MATERIALIZED VIEW' then 'materializedview'
                else lower(table_type)
            end as "table_type"

        from ci.information_schema.tables
        where table_schema ilike 'product'
        and table_name ilike 'users'
        and table_name not ilike ''

Proposed Solution
This PR proposes to fully qualify objects in sql_builders.sql such that the node.database is also injected in the SQL queries. From the example above, this would yield the following query which solves the issue described above:
select distinct
            table_schema as "table_schema",
            table_name as "table_name",

            case table_type
                when 'BASE TABLE' then 'table'
                when 'EXTERNAL TABLE' then 'external'
                when 'MATERIALIZED VIEW' then 'materializedview'
                else lower(table_type)
            end as "table_type"

        from raw.information_schema.tables
        where table_schema ilike 'product'
        and table_name ilike 'users'
        and table_name not ilike ''

I'll note that I'm very excited about this project! I recently discovered it when looking for unit testing options for dbt and this one seems to be the most promising! I've been trying to set it up on our own dbt project, but have ran into the issue I've outlined above. Curious to hear your thoughts on the proposed solution.

Hi @chasleslr, Thank you for your feedback and your contribution.
We're really glad that you found the package useful for your case.
Your proposal sounds good.


Low order FD

Fix low order (1, 2) indices for cartesian FD
Removed some unnecessary if/else

Merged.