Injecting @FeatureToggle Instance<Boolean> vs @FeatureToggle boolean

The extension doc shows a code snippet which injects an Instance<Boolean> field without explaining why it should be preferred over a simple boolean. I haven't confirmed that yet but I suppose injecting a boolean field doesn't really work because the injected value won't reflect changes to the toggle made in Unleash. By injecting an Instance<Boolean>, each call to Instance#get will return the latest toggle value from Unleash. This is only an asumption so far, I should be able to test it tomorrow and confirm whether it's correct or not.
If it is, I think the doc and javadoc should provide details about the difference between @FeatureToggle Instance<Boolean> and @FeatureToggle boolean.

I confirmed with local testing that @FeatureToggle boolean is not an option because the injected value won't change after the toggle has been updated in Unleash. Let's update the doc to make it obvious to everyone.

Or even better, @FeatureToggle boolean should be detected at build time and trigger a warning or an exception.

I'll submit a PR about this shortly.


Defs support

This is a work in progress. All I've done so far is moved the drawing for each element to a map, so that down the road when the defs and use tags are implemented the use tag can call the draw functions from the map too, rather than reimplement each one.
Fixes #11

OK, let me know when you have it working and tests to prove it.

Tests now pass, same as before. I'm a little confused about the "fill_i.png"s though, I thought something was wrong with what I did, but they're all blank on master as well for me.
I still need to add support for "use" so the defs can actually be used, and then I'll make some svgs that use defs/use and add them to the tests. Then I should be ready for review!

Alright, it's ready for review. Not sure why, but the button to switch from draft to actual PR is missing on my end.

I have to think about some of these changes and also confirm the testing and benchmarking. I will get back to you soon...

This looks very well done Noofbiz. It is like you are completing my thoughts! Great job!
For now I am going to place it in a separate branch, "defs", and let some people test it if they want. They are some of the more serious oksvg users I know of. So, @andydotxyz,  @ajstarks, @rcoreilly, and anyone else, if you want, then please try the defs branch of oksvg. If no problems are reported after a couple of weeks I will merge defs into the main branch.

In my testing it appears to break the loading the background gradient in this file:
https://github.com/fyne-io/examples/blob/develop/solitaire/faces/back.svg

It's probably not calling the gradient since it's saved as a def now but never actually executed. I'll look into it when I can. The solution is probably to make gradients a special case and execute them immediately after being stored in the defs

Maybe gradients and defs should be stored separately? Then there would be
no need for the map's value to have and interface{} type. Also, I would
like to at some point I would like to define the drawFuncs like this:
var (
svgF svgFunc = func(c *IconCursor, attrs []xml.Attr) error {
c.icon.ViewBox.X = 0
c.icon.ViewBox.Y = 0
c.icon.ViewBox.W = 0
c.icon.ViewBox.H = 0
var width, height float64
var err error
for _, attr := range attrs {
switch attr.Name.Local {
case "viewBox":
err = c.GetPoints(attr.Value)
if len(c.points) != 4 {
return errParamMismatch
}
c.icon.ViewBox.X = c.points[0]
c.icon.ViewBox.Y = c.points[1]
c.icon.ViewBox.W = c.points[2]
c.icon.ViewBox.H = c.points[3]
case "width":
wn := trimSuffixes(attr.Value)
width, err = strconv.ParseFloat(wn, 64)
case "height":
hn := trimSuffixes(attr.Value)
height, err = strconv.ParseFloat(hn, 64)
}
if err != nil {
return err
}
if c.icon.ViewBox.W == 0 {
c.icon.ViewBox.W = width
}
if c.icon.ViewBox.H == 0 {
c.icon.ViewBox.H = height
}
}
return nil
}
drawFuncs = map[string]svgFunc{
"svg": svgF,
}
)
For course I only did it for one function. But it avoids having to populate
the drawFuncs map using the init() function.
I doubt it is much of a performance enhancer, but it is a little cleaner
syntactically IMHO.
Not a huge deal. Either you can do it, or I can after we merge your pull
request into the master, once we get deal with the grad issue.
On Tue, Apr 9, 2019 at 1:01 PM Noofbiz<EMAIL_ADDRESS>wrote:

It's probably not calling the gradient since it's saved as a def now but
never actually executed. I'll look into it when I can. The solution is
probably to make gradients a special case and execute them immediately
after being stored in the defs
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/srwiley/oksvg/pull/11#issuecomment-481412964, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALlXB6j_Z_GvMq6C863i2ZDPv6q9ilpPks5vfPGkgaJpZM4bhLuT
.

Figured out how to merge into a separate branch on github. Will delete other 'defs' branch


fix: initialize load more posts counter

Summary

This PR fixes broken logic of loading more posts. Counter variable is not initialized, therefore it is undefined, therefore when adding +1 to it, it becomes NaN, therefore guard if (this.extraPagesLoaded > MAX_EXTRA_PAGES_LOADED) { never works.
Probably this only affects channels with lots of System Message (which can be hidden by user but loaded anyway).
If user opens such channel with system messages hidden then all messages in the channel are being loaded. Which results in heavy load on API.
Also, I added a counter reset after a user clicks on Load more button for better UX.
Ticket Link

Related Pull Requests

Has server changes (please link here)
Has mobile changes (please link here)

Screenshots

Release Note

NONE

Hello @vdvukhzhilov,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.
Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.
This is a standard procedure for many open source projects.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/check-cla

/check-cla

Thanks for changing that! This looks good to me then. The loading of more join/leave messages feels a bit clunky, but I assume that's always been the case as long as they've been combined

yeah. I've noticed that too, but I dont't have enough knowledge of how things work and related in this project, so I left it as is.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/213883

Thanks @vdvukhzhilov
Tested, looks good to merge - pending E2Es - re-running, last report shows multiple spec files were skipped

Verified loading of more posts behavior
Ticket created for tracking https://mattermost.atlassian.net/browse/MM-45495

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/213922

E2E report looks good, no PR related failures.


Should it be signed?

Yup, i got this
Referenced assembly 'MvcRouteTester' does not have a strong name
I'll download the code and create a signature I suppose.

Yes, please sign it on nuget.

any progress?


Update click dependancy version

Update click dependency version to prevent version conflicts with other installed packages, specifically Celery >5.2.1.

Thanks!


Configurable AssetBundle variants

Currently the two variants (normal, alternate) are hardcoded, it should be possible to configure this more dynamically.
Unless it's prefereable to keep it hardcoded.

@lightsoda Have you worked on this as part of the variant stuff you've been working on over the past couple of days?

After further discussion, it seems that asset variants are as configurable as tables are (a matter of dropping things in the right place and adding their name to a list of available variants). That's configurable enough for me!


Try to reconnect if websocket disconnected.

Solves #46.
Note that if I disconnect and reconnect, the server doesn't seem to send the tournament list, so we don't update the current screen to the latest data.

I can make the server do that. It's explicitly only doing that to new connections right now.
Also, I'm pretty certain we should do retrying on onerror as well. All of the instances of the websockets dying on the stream were because of the backend crashing, which results in an error because the termination is not done cleanly. What do you think?

How can it tell which ones are new are which ones are reconnecting? Is it caching IPs?
If the server sends an error message and crashes, a close event is also fired. I tried killing the server with Ctrl + C, and it cleanly closed the WebSocket, so we reconnected. So in that case we're covered. Try it!
What I didn't know was that if the server panics, apparently it doesn't properly disconnect, according to the Internet. I'll try it and see.
In that case, it might be good to use your ping messages and declare us disconnected if we haven't received one in double or triple the amount of time the server sends them after.
What do you think?

Panics were exactly what I was thinking about.  :P
If that full disconnect happens, should the page perhaps reload or something?

Reconnecting to the WebSocket should be enough, right? Do you think something would be missing and we'd need to reload?
Also, it might be nice to disable buttons while we're disconnected, so that people don't navigate away into a 404 while we're disconnected.

I worked a bit on this, although I didn't commit anything.
I think the pulse should be sent every 5 seconds or so, and the page should realize it's disconnected 10 seconds after the last ping. In that case, it could try to reconnect.
Next things: clean and commit, and then turn header into a component and show connectivity there.

Did you commit anything yet? :)

Yup. The reconnection works just fine. I can't get it to appear properly on
the header, though. Haven't I pushed the reconnection?
On Oct 6, 2016 22:57, "Lowe Thiderman"<EMAIL_ADDRESS>wrote:

Did you commit anything yet? :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thiderman/drunkenfall/pull/48#issuecomment-252086409,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABKtlxlGyZ0VMAvrfKoZdAG7oG6e5SSOks5qxWC9gaJpZM4KJZ8U
.

I dunno, you said "I didn't commit anything", so I assumed there was something that was left to be added!

I pushed! It reconnects now, both if the server is closed regularly, and also if it dies unexpectedly (it figures it out by the missing pings).
Take a look at the pull request and let me know if you have comments.

I'll come back later and answer your comments, I'll put Christiana to bed.

I'm adding one small correction, to avoid double attempts at reconnection.

This is fantastic! Thanks so much, man! <3

My pleasure <3


RFC: #[late] statics

Summary
#[late] static are statics that are initialized at runtime, before the entry
point is called and after RAM initialization happens.
Motivation
Consider the allocator example from the quickstart template:
#[global_allocator]
static ALLOCATOR: CortexMHeap = CortexMHeap::empty();

const HEAP_SIZE: usize = 1024; // in bytes

#[entry]
fn main() -> ! {
    // Initialize the allocator BEFORE you use it
    unsafe { ALLOCATOR.init(cortex_m_rt::heap_start() as usize, HEAP_SIZE) }

    let xs = vec![0, 1, 2];

    // ..
}

Quite a few things can go wrong there: you could forget to initialize the
allocator or you could initialize it too late. In either case you end up with
OOM (abort).
This example can be simplified using a #[late] static:
#[late]
#[global_allocator]
static ALLOCATOR: SyncAllocator = unsafe {
    static mut BYTES: [u8; 1024] = [0; 1024];

    // you are familiar with this transformation
    let bytes: &'static mut [u8] = BYTES;

    // `SyncAllocator` is a newtype over `Mutex<SomeAllocator>`
    SyncAllocator::new(bytes)
}

#[entry]
fn main() -> ! {
    // Growable array allocated on the heap
    let xs = vec![0, 1, 2];

    // ..
}

Design
#[late] statics are not lazy statics. Lazy statics are initialized on
first use, they have runtime cost on each access and memory overhead. #[late]
statics are statics that are initialized before the #[entry] function is
called, accessing them is zero cost and they have no memory overhead.
The above example expands to something like this:
// For details about the `.uninint` section see RFC #116
#[link_section = ".uninit.<random-hash>"]
#[global_allocator]
static ALLOCATOR: Late<SyncAllocator> = {
    #[link_section = ".late.<random-hash>"] // new linker section
    static INITIALIZER: unsafe fn() = initialize;

    unsafe fn initialize() {
        let val = {
            // (proc-macro transformation)
            let BYTES: &'static mut _ = {
                static mut BYTES: [u8; 1024] = [0; 1024];

                &mut BYTES
            };

            // (user code)
            // you are familiar with this transformation
            let bytes: &'static mut [u8] = BYTES;

            // `SyncAllocator` is a newtype over `Mutex<Allocator>`
            SyncAllocator::new(bytes)
        };

        ALLOCATOR.initialize(val);
    }

    Late::uninitialized()
};

The Late newtype will be provided by this crate:
/// IMPLEMENTATION DETAIL. DO NOT USE
#[doc(hidden)]
pub struct Late<T> {
    inner: UnsafeCell<MaybeUninit<T>>,
}

unsafe impl<T> Sync for Late<T> where T: Sync {}

impl<T> Late<T> {
    /// IMPLEMENTATION DETAIL. DO NOT USE
    #[doc(hidden)]
    pub const fn uninitialized() -> Self {
        Late {
            inner: UnsafeCell::new(MaybeUninit::uninitialized()),
        }
    }

    /// IMPLEMENTATION DETAIL. DO NOT USE
    #[doc(hidden)]
    pub unsafe fn initialize(&self, value: T) {
        (*self.inner.get()).set(value)
    }
}

impl<T> Deref for Late<T> {
    type Target = T;

    fn deref(&self) -> &T {
        unsafe { (*self.inner.get()).get_ref() }
    }
}

impl<T> DerefMut for Late<T> {
    fn deref_mut(&mut self) -> &mut T {
        unsafe { (*self.inner.get()).get_mut() }
    }
}

As you can see Deref and DerefMut perform no runtime checks. However,
dereferencing is only valid after Late has been initialize-d.
#[late] statics are initialized before #[entry] / main and after RAM
initialization using r0::run_init_array or its equivalent.
fn Reset() -> ! {
    __pre_init();

    r0::zero_bss(&mut __sbss, &mut __ebss);
    r0::init_data(&mut __sdata, &mut __edata, & __sidata);
    r0::run_init_array(&__slate, &__elate);

    main()
}

#[global_allocator]
To compose with the built-in global_allocator attribute we need to provide
the implementation below in this crate.
unsafe impl<T> GlobalAlloc for Late<T>
where
    T: GlobalAlloc,
{
    unsafe fn alloc(&self, layout: Layout) -> *mut u8 {
        T::alloc(self.deref(), layout)
    }

    unsafe fn dealloc(&self, p: *mut u8, layout: Layout) {
        T::dealloc(self.deref(), p, layout)
    }
}

Why unsafe?
Using normal statics within a #[late] static initializer is sound, but using
any #[late] static within the initializer is not because there are no
guarantees about the execution order of #[late] initializers.
Furthermore for global resources like global_allocator trying to use the
resource before it's initialized is also undefined behavior.
#[late]
#[global_allocator]
static ALLOCATOR: SyncAllocator = unsafe {
    static mut BYTES: [u8; 1024] = [0; 1024];

    let xs = vec![0, 1, 2]; // undefined behavior
    ALLOCATOR.alloc(..); // also undefined behavior

    SyncAllocator::new(BYTES)
}

It's not possible to prevent all these issues at compile time so unsafe must
be used. Arguably, we could prevent the first issue by making the static
unnameable (by assigning it a randomly generated name) but this would greatly
reduce the flexibility of #[late] statics.

Thoughts? Are there use cases other than global allocators?

I think this was never discussed?
From my side I see great usage for this, for example when calculating encryption keys for the system on startup.

I personally feel uneasy about bringing the static initialization order fiasco to Rust, but I can see that this would be useful. However, "not forgetting to call a function" doesn't really strike me as the most important use case of this feature either.
It seems like this would effectively bring RTFM's late resources to the non-RTFM world, which would be pretty great, but I'm sure there must be some way of doing that without the unsafety and initialization order problems – RTFM also manages to do this after all.

This sounds like C++ constructors for statics - oh the fun I've had trying to get the compiler to call the constructors in the right order. In the past I used C++ static objects to represent singletons like serial ports, and I could see a use case for that in Rust.


energy transformation class with a fuel output

Description of the issue
From OEKG discussion:
Add energy transformation class with a fuel output as equivalent class (something like "energy-to-fuel" or "fuel production").
Related to:

#1522
#1523

Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every entry in the ontology should have a definition
[ ] classes should arise from concepts rather than from words

Are there energy-to-fuel processes, that are not power-to-fuel (OEO_00330007) but important for the domain?

Ok, sorry, too many thought in my head that I didn't wirte down:
I'd argue that energy-to-fuel is not necessarily the same as fuel-production ("anything-to-fuel").
For steam reforming, the definition says that it can be seen as both, chemical reation and energy transformation. Same would hold for mineral oil refining process. And maybe chemical reaction could be described generically as "energy transformation and (has energy input some chemical energy) and (has energy output some chemical energy)". But this might be an unhealthy generalization?!

I don't think that we should generalise too far, because in the end, every process needs energy.

From OEO dev meeting 58:

Production as subclass of Transformation

Implementation should not bring any problems.

Define two different parallel structures for material transformations and energy transformations.
Discuss distinction between energy transformation and transformation of material entities, e.g. energy carriers

Production as subclass of Transformation

Production is the transformation process of combining various inputs in order to create an output that has value ~and can be used by other processes~.

...various physical inputs... ? what about energy inputs?
can we specify "value"? e.g. econimic value?
When the definition is clear, the (input/output) axioms may be easy to derive.

can we specify "value"? e.g. economic value?

We now have good [^1], maybe that is what is meant here.
[^1]: A good is a continuant that has the good role. => The role of an independent continuant or energy over which ownership rights can be established, whose ownership can be passed from one party to another by engaging in transactions, and that is not money.

Proposal: Production is the transformation process of combining various inputs in order to create an output that is a good ~has value and can be used by other processes~.

axioms:

'has output' some good
'has physical input' some 'material entity'

Fuel production is a production process which has fuel as physical output.
'equivalent to' production and ('has physical output' some fuel)

I am fine with this proposal.

Ready for implementation?

In branch feature-1526-fuel-production I've added fuel production and adapted production.

However, still to be discussed:

Define two different parallel structures for material transformations and energy transformations.
Discuss distinction between energy transformation and transformation of material entities, e.g. energy carriers

material transformation is a good label. Do you have a proposal for a definition?

I am not sure how detailed the def has to be.
Material transformation is a transformation in which one or more input material entities undergo a convertion process and result in output material entites that are, at least partially, physically changed.

Defining transformation via conversion is self-referencing. I thing, the proposal could be shortend to:
A material transformation is a transformation in which one or more input material entities are, at least partially, physically changed and result in output material entites.

Seems we have a solution. I'll implement (after the release).

I am wondering why we didn't make production a transformation subclass. mineral oil refining process is now a production, but not inferred as material transformation...
Infact it was  proposed here https://github.com/OpenEnergyPlatform/ontology/issues/1526#issuecomment-1545448495 .


how remove install propriety from the client ?

i tried many times but the client crashed every time i try to do that

and i want to remove other prop rites from the client but i can't

and i want to remove other things (proprietors )from the client but i can't

Remove this and all places where this variable is referenced: https://github.com/quasar/QuasarRAT/blob/master/Client/Config/Settings.cs#L48
You also need to adjust this: https://github.com/quasar/QuasarRAT/blob/master/Server/Core/Build/ClientBuilder.cs#L87


[CENTOS-11] - Centos image needs to be able to run Ansible scripts

We're not going to do this, it's not necessary for the lab environment


How do I append to (and remove from) arrays in an existing Elastic Search doc?

Which version of Elastic are you using?
[ ] elastic.v5 (for Elasticsearch 5.x)
Please describe the expected behavior
Append to an existing array in a specific ES document
Please describe the actual behavior
elastic: Error 400 (Bad Request): failed to execute script [type=illegal_argument_exception]
or
no error but no changes committed either
Any steps to reproduce the behavior?
Consider the following go struct, representing a type in ES:
type Post struct{
    Content    string
    Likes   []string
}

How would one go about appending and removing specific likes using this package?
Through searching, the closest thing I got to append directly from ES is as follows:
script := elastic.NewScript("ctx._source.Likes += Like").
	Param("Like", newLikerID).
	Lang("groovy")

resp, err := elastic.NewUpdateService(eclient).
	Index(ENTRY_INDEX).
	Type(ENTRY_TYPE).
	Id("AV5yAitA0M7oYBrcyH_q").
	Script(script).
	Do(ctx)

we also tried
resp, err := elastic.Update.(eclient).
	Index(ENTRY_INDEX).
	Type(ENTRY_TYPE).
	Id("AV5yAitA0M7oYBrcyH_q").
	Script(script).
	Do(ctx)

But the execution of this generates the error above.

The illegal_argument_exception indicates that the update failed. The best way to debug this is to first find the correct way to do so with a pure REST call, then translate that into Go code.
You might also want to have a look at the tests. They should give you some hints into how to use the API.

Hello, is it possible to use the API to handle simultaneous changes to a document? Suppose I'm creating a forum with posts containing an array of posts to act as comments. If more than one comment is added simultaneously, how would the API or Elasticsearch prevent one comment form overwriting the other?

@mrb721 ES supports partial updates via the Update API. That's the only way to modify documents in-place. More often, in larger installations, you simply reindex data with the Bulk API, sometimes with a sliding window technique. See Modeling data in the Definite Guide.
Please make sure to not treat ES as a SQL database. Although they share some ideas, their concepts and goals are different.

I wonder if it is possible to index new data into existing index using your package. I tried to use NewBulkIndexRequest but there is no data inserted if the index already exists. I wonder if you have a solution.

@thejuniordevops If you want do to bulk updates, use a BulkUpdateRequest. If you want to update outside the Bulk API, use the Update API which allows partial updates. This is more of an Elasticsearch problem, not a problem related to the Go driver. You might be better off to ask this on discuss.elastic.co.


Another try to fix CHANGELOG.md link in release notes

Summary
Another try to fix CHANGELOG.md link in release notes - see https://github.com/sigstore/sigstore-java/pull/706#issuecomment-2125502914

oh need to amend your commit with -s

oh need to amend your commit with -s

Sure, no problem. It's already signed, but maybe this repo requires to have it signed by the maintainer.

Ok, I've fixed it by adding "signed-off-by" (the commit was signed).

Done

oh right this test can't pass because there is no oidc token... because it's a pull request

Seems to work :)
https://github.com/sigstore/sigstore-java/releases/tag/v0.10.0
(let's skip that there are no changes mentioned ;) ).

Will bring doing that after 1.0


Question: How to modify border title once the widget is instantiated?

How to modify border title once the widget is instantiated?

Hello @miguelmota, I am assuming you are asking about the container title? You should be able to utilize the dynamic layout feature.
In short you specify an ID for the container when creating it by passing this option:
https://github.com/mum4k/termdash/blob/68bf0566e6ec8effaf6e83400ef0046347a5f5f1/container/options.go#L308-L320
And then you can use the container.Update function, specifying the same ID and providing any set of new options, including a new title:
https://github.com/mum4k/termdash/blob/68bf0566e6ec8effaf6e83400ef0046347a5f5f1/container/container.go#L229-L235
However if you are asking about title of a specific widget, that might be different, please let me know.

@mum4k makes perfect sense; thanks!


Account Managment

Users need to be able to register an account, and have a tracked dedicated amount of space for their account. When a user registers, they are given an API key that they need to be able to sign in and view. This API key will allow them to interact with the API server.
Outstanding questions:

What should be the limit for a free account? My thought is 5G.

Just wanted to add a note here for later, but I think that we may end up having to track usage within the application to effectively enforce quotas. It may also be good to get an idea of what we want to track (if anything) outside of raw storage. I'm thinking:

Inbound transfer
Outbound transfer
Number of requests


[SOLVED] Building on linux arm

I'm following this (pretty amazing) tutorial on my rpi itself, rather than a windows or ubuntu pc. However, the building part is an issue. I've downloaded the "AArch64 ELF bare-metal target" for aarch64 but it doesn't work. Any idea on why?
Thanks in advance!
output:
/bin/rm kernel8.elf *.o *.img > /dev/null 2> /dev/null || true
gcc-arm-compiler/bin/aarch64-none-elf-gcc -Wall -O2 -ffreestanding -nostdinc -nostdlib -nostartfiles -c boot.S -o boot.o
gcc-arm-compiler/bin/aarch64-none-elf-gcc: 1: gcc-arm-compiler/bin/aarch64-none-elf-gcc: ELF�0d@@��@8: not found
gcc-arm-compiler/bin/aarch64-none-elf-gcc: 7: gcc-arm-compiler/bin/aarch64-none-elf-gcc: Syntax error: "(" unexpected
make: *** [Makefile:9: boot.o] Error 2

PS: I've extracted the .tar.xz file in my project folder and renamed the directory to 'gcc-arm-compiler'. I've also made these changes in the makefile, where i replaced the GCCPATH

Good news!
I followed your documentation to the point and it worked! I got some warnings, but they didn't seem to matter.
Looks like my problem is truly fixed now! :)

Hey! Just a quick question (this will be the last).
Since I'm both compiling and running on the same device, do I really need to cross-compile?

Possibly not...
Should be easy to test - just change the GCCPATH in the Makefile to point at the gcc binary that comes with Raspbian (probably /usr/bin). You will also need to modify the executable names that run through the Makefile e.g. aarch64-none-elf-gcc will become just gcc, aarch64-none-elf-ld will become ld etc.
Let me know how you get on!

I tried it with someone else's example files, which worked. If I try it with e.g. part 5 of this tutorial it gives the following output:
sjoerdv@raspberrypi:~/Coding/OS/BareMetal $ make
/bin/rm kernel8.elf *.o *.img > /dev/null 2> /dev/null || true
gcc -Wall -O2 -ffreestanding -nostdinc -nostdlib -nostartfiles -c boot.S -o boot.o
boot.S: Assembler messages:
boot.S:7: Error: ARM register expected -- `mrs x1,mpidr_el1'
boot.S:8: Error: ARM register expected -- `and x1,x1,#3'
boot.S:9: Error: selected processor does not support `cbz x1,2f' in ARM mode
boot.S:11: Error: selected processor does not support `wfe' in ARM mode
boot.S:16: Error: ARM register expected -- `ldr x1,=_start'
boot.S:17: Error: immediate expression requires a # prefix -- `mov sp,x1'
boot.S:20: Error: ARM register expected -- `ldr x1,=__bss_start'
boot.S:21: Error: ARM register expected -- `ldr w2,=__bss_size'
boot.S:22: Error: selected processor does not support `cbz w2,4f' in ARM mode
boot.S:23: Error: ARM register expected -- `str xzr,[x1],#8'
boot.S:24: Error: ARM register expected -- `sub w2,w2,#1'
boot.S:25: Error: selected processor does not support `cbnz w2,3b' in ARM mode
make: *** [Makefile:9: boot.o] Error 1

Was the other example using AArch64 assembly instructions? I suspect not. Not all code is created equal!
I just wouldn't go there. Cross-compilation is going to be your friend here... Otherwise, try and see whether you need to give gcc some command-line argument to target AArch64 etc.
Personally, I wouldn't bang my head against a brick wall when a solution exists!

Copy that!😂

You might wanna add a link to this tutorial as an alternative to re-imaging the rpi. It shows you how to build the cross-compiler from source and works perfectly.

Yes, that was my other option (I even mentioned it in passing in my first reply to you at the top of this thread!).
I didn't know how excited you'd be to build the compiler from source though, to be honest. Great that you did it :)

I'm not saying that this solution is the best, because it definetly isn't. I just didn't really like the idea of trying to back up all my stuff from my 128GB sd card to my spare 16GB one.

Hi! I had a similar setup where I was building on the pi and connected it
to another pi via serial to usb. With the 64 bit raspberry pi OS Adams
tutorials worked really well using the native gcc compiler and the
assembler that comes with the 64 bit OS. You just dont need the path, I
could just build it straight away.
You can look at my make file to see the difference.
WARNING the code is not working atm since I was trying some things and then
I took a break continuing with a game and a little hobby parser BUT I
believe the make file is actually OK
Any way, it could possibly help to look at it, should just be the same as
Adams make file but with the native tools about one or 2 steps after the
game in Adams tutorial. I dont quite remember the status of the make file.
I will find my way back to the project evetually :)
Den tors 13 maj 2021 14:09SjoerdV @.***> skrev:

I'm not saying that this solution is the best, because it definetly isn't.
I just didn't really like the idea of trying to back up all my stuff from
my 128GB sd card to my spare 16GB one.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/isometimes/rpi4-osdev/issues/12#issuecomment-840514157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPJGGC3HX25COIBFDPE6JLTNO6QHANCNFSM44UZVFXQ
.


[material-ui][docs] Document Drawer onClose reason in v4

The type shows it is the same as Modal's onClose
https://github.com/mui/material-ui/blob/v4.x/packages/material-ui/src/Drawer/Drawer.d.ts#L31-L36
So I copied the documentation line about reason from Modal.d.ts, ran yarn proptypes and yarn docs:api
This generates almost the same doc as modal.md, but there is an additional line in the modal documentation that wasn't present in Modal.d.ts 🤷
https://github.com/mui/material-ui/blob/v4.x/docs/pages/api-docs/modal.md?plain=1#L54

The reason parameter can optionally be used to control the response to onClose

This is already correctly documented in v5

[x] I have followed (at least) the PR section of the contributing guide.

One caveat is that I am targeting the v4.x branch since this documentation needs to be backported there

Hey @albertchae, thanks for working on this, and sorry for the late review.
I agree with the change. This .md content is generated from Drawer.d.ts, so may I ask you to modify that instead (You can copy it from modal as well) and run yarn docs:api? That should modify the docs content accordingly.

Thanks @DiegoAndai , I followed those steps and pushed my changes with updated PR description. One slightly weird thing I noticed compared to when I manually copied from modal.md is this:
This generates almost the same doc as modal.md, but there is an additional line in the modal documentation that wasn't present in Modal.d.ts 🤷
https://github.com/mui/material-ui/blob/v4.x/docs/pages/api-docs/modal.md?plain=1#L54

The reason parameter can optionally be used to control the response to onClose

Hey @albertchae, sorry for the delay. If you're still interested in merging this change, may I ask you to work on the failing CI tests?


Update description of the Baklava network

Description
Description of the Baklava network currently still references the Stake Off. This PR fixes that.

Jinx!


Allow to use proxy webhook

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ X] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@zirain I created issue 44122

This may be a case where https://istio.io/latest/docs/setup/additional-setup/customize-installation-helm/ is more appropriate


And installer

Step by step of how to get setup.
If there no /location_public/ node show setup
Show instructions of how to insert admins UID into /roles/site_admin/{uid} to get started
We could even display their uid if once they have logged in, since only those setting up the site have access to fire base console.

so far added http://localhost:3020/#!/base/setup page to set some API keys and things.


Possible enhancement: use ar M-scripts to create libmicroros.a

The current implementation uses ar x to extract all objects from all .as in $TARGETDIR/install/lib, then ar rc to merge all objects into a single library again:
https://github.com/micro-ROS/micro_ros_setup/blob/a73f84707874b5a57852cab802d8d032610c3cbd/config/generate_lib/generic/build.sh#L40-L48
The ar documentation has a section on Controlling ar with a Script, which documents the M scripting language.
I've tested this to generate libmicroros.a with the following script (for my particular platform):
CREATE libmicroros.a
ADDLIB /.../install/lib/libactionlib_msgs__rosidl_generator_c.a
ADDLIB /.../install/lib/libactionlib_msgs__rosidl_typesupport_c.a
...
ADDLIB /.../install/lib/libyaml.a
SAVE
END

there is a small difference between the .a generated this way and the current implementation (the M-script version is about 7kB larger), but I've not run into linking issues.
The M-script is very easy to generate:
echo "CREATE libmicroros.a" > ar_script.m
for file in $(find "$FW_TARGETDIR/install/lib/" -name '*.a'); do
  echo "ADDLIB ${file}" >> ar_script.m
done
echo "SAVE" >> ar_script.m
echo "END" >> ar_script.m

and is very fast (approx 250ms on my system for 98 libraries).
There could be a potential downside to using it, which would be that ar appears to use a last-ADDLIB-wins approach when adding libraries with object files which have the same name.
I'm not sure how much of a problem that really is, as, looking at nm output, the library generated using the current approach prefixes objects with the package name, which would seem to prevent name-clashes, but would lead to a situation where there may be multiple versions of the same code/objects in the single .a. I'm not sure how the linker deals with that.
At least with M-scripts, this situation should not be possible.

Edit: it also helps on platforms/environments with a limit to the maximum command-line length. With many packages, the command-line passed to ar rc can become very long. The M-script circumvents this.

Good point @gavanderhoorn, could you please create a PR with the proposed solution?

I've submitted #574.

Closing as #574 was also closed.


Add Layout mix-in

This brings in a MuchRails::Layout mix-in to support files that
represent HTML rendered in a layout. This also brings in
MuchRails::ViewModels::Breadcrumb.

@nweathersbee minor, but can you update the commit message and PR description. You call MuchRails::ViewModels::Breadcrumb a "mix-in". It isn't a mix-in, though, it is just a class. Thanks.

@nweathersbee thanks for the changes.


Issue with ES module treatment in Next.js environment

Hello! I am currently having an issue when using the Mafs library with Next.js.
The issue appears to be that in package.json of this library the "type" is set to "module". However, Next.js treats .js files as CommonJS Modules which leads to compatibility issues. I have found a temporary fix in my development environment where I edit the package.json to use CommonJS. However, in production, this doesn't work since the node_modules folder is typically not committed. I was wondering how Mafs is typically used with Next.js to fix these errors in production.

Huh, I suppose this should get stripped on publish.

I'm a little confused because I'm not able to reproduce the error you're seeing.  A fresh Next.js installation works fine in dev and prod for me.
In the meantime, I'll publish a version without "type": "module" since it's not really needed.

Okay, 0.18.4 was published without "type": "module"—give it a whirl. I'll close this issue but let me know if you're still encountering issues.

Thank you so much, it's working now! In terms of reprod repo, I'll see what I can do to reproduce the error myself in a different project, but the project it was occurring in is https://github.com/PavlosDefoort/PhotoProX. Perhaps the issue may be in one of the next js config files.


Add support for Vale suggestions

Add support for Vale suggestions.
Closes: https://github.com/SublimeLinter/SublimeLinter-vale/issues/10.

@kaste Could you review this one? I tried your suggested code from https://github.com/SublimeLinter/SublimeLinter-vale/issues/10#issuecomment-1692392062 and it worked well.

Let's go!


minor refactor, to support reading/writing to/from gzip files

Made a tiny refactor, in order to support I/O to gzipped matrixmarket files.
Also changed trait bound to relax ?Sized on BufRead/Write, for
same end-goal.

Thanks!


[fix-3835][ui] When the tenantName contains "<", the tenant drop-down list is blankadd verify tenant name cannot contain special characters.

What is the purpose of the pull request
#3835
When the tenant name contains "<", when creating/editing users and saving workflows, the tenant drop-down list data is blank
Brief change log
add verify tenant name cannot contain special characters.
 let isSpecial = /[~#^$@%&!*()<>《》:;'"{}【】	]/gi
        if (isSpecial.test(this.tenantName)) {
          this.$message.warning(`${i18n.$t('Please enter tenant name without special characters')}`)
          return false
        }

Verify this pull request
This change added tests and can be verified as follows:

Manually verified the change by testing locally.

Codecov Report

Merging #3865 into dev will increase coverage by 0.22%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #3865      +/-   ##
============================================
+ Coverage     40.04%   40.26%   +0.22%
- Complexity     2925     2940      +15
============================================
  Files           459      459
  Lines         21793    21793
  Branches       2652     2652
============================================
+ Hits           8726     8775      +49
+ Misses        12238    12184      -54
- Partials        829      834       +5

Impacted Files
Coverage Δ
Complexity Δ

...inscheduler/service/zk/CuratorZookeeperClient.java
56.75% <0.00%> (-5.41%)
6.00% <0.00%> (-1.00%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.00% <0.00%> (-2.78%)
9.00% <0.00%> (-2.00%)

...dolphinscheduler/remote/future/ResponseFuture.java
79.66% <0.00%> (-1.70%)
17.00% <0.00%> (-1.00%)

...er/master/dispatch/host/assign/RandomSelector.java
83.33% <0.00%> (+5.55%)
4.00% <0.00%> (+1.00%)

...olphinscheduler/server/utils/DependentExecute.java
69.23% <0.00%> (+8.97%)
21.00% <0.00%> (+4.00%)

...ver/master/consumer/TaskPriorityQueueConsumer.java
44.73% <0.00%> (+9.21%)
15.00% <0.00%> (+2.00%)

...rver/master/processor/queue/TaskResponseEvent.java
61.81% <0.00%> (+10.90%)
16.00% <0.00%> (+6.00%)

.../server/master/runner/DependentTaskExecThread.java
70.65% <0.00%> (+17.39%)
15.00% <0.00%> (+5.00%)

...er/master/processor/queue/TaskResponseService.java
55.76% <0.00%> (+23.07%)
6.00% <0.00%> (+1.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 76f6e20...35f667d. Read the comment docs.

can you mention the code in 1.3.3-release

i have reviewed the issue, the key '<script' matches the keywords on the front page, other places such as project names, workflow definition names, and so on have the same problem, so we should consider a more suitable solution.

i have reviewed the issue, the key '<script' matches the keywords on the front page, other places such as project names, workflow definition names, and so on have the same problem, so we should consider a more suitable solution.

tenant is special, not the same with project name and so on


Tutor provided an alternate way of starting a React app, might pursue…

… this or might opt for something more like how we've done it in class. Either way, saving this version

I opted against using this.


question: how to use layout and interct

I'm trying to combine the interact function with custom Box layout.
As  minimial example, let's say I put some widgets in a HBox:
xwid = FloatSlider(min=-1, max=1, description='x', continuous_update=False)
ywid = FloatSlider(min=-1, max=1, description='y', continuous_update=False)
hbox = HBox([xwid, ywid])

I can use interact:
@interact
def g(x: xwid, y: ywid):
    plt.plot(x, y, 'o')
    plt.xlim(-1, 1)
    plt.ylim(-1, 1);

But in this way I cannot specify the HBox container. Is there a way to use interact with widgets contained in a Box?
Thanks.

@gnestor - can you put a link to the duplicate issue?

Duplicate of #826


Further streamline unittests

Rather than having 2 testing scripts:

test_network_api.py
test_network.py

Merge into 1 testing script and iterate over import style:
import spaghetti as spgh

and
from .. import network

Closing this issue for now due to difficulty parameterizing unittest.TestCase classes.


Remove channel from channel list when deleting

Currently, we delete the channel data from redis, but we don't remove the channel id from the channel list.

:+1: when travis is happy.


[New game]:space gun

🎮 Game Request
Shoot all the asteroids while maintaining fuel and live of your spaceship
Point down the features
Game points will be awarded on the basis of hit bonus and accuracy.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @S-ishita !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @S-ishita 👋!
@kunjgit here,
We have this annoucement to make 📢!!
💥 Special Announcement:
It's the Call to all the designers 🔥 🎨
As you all know that GameZone has crossed 100 games 💗 , it's time that we all come up together and make the UI even better!!
We are redesigning the thumbnails, make sure you come up with the aesthetic and cool ideas 🚀 !
You are supposed to share the 4 different templates that can be used. Make sure that the size is: 1280 px X 720 px.
The frame should be such that there is only a single image of the game that's taking up the major portion of the frame. Any kind of text should not be there.
The design should be catchy and aesthetic! 🔥
Note: You are not supposed to create any issue right now for the same.
You have to share different designs right now in Discord  and Project Admin would be selecting one design and would be assigning the issue. After that only, you have to start working on it.

Hey @S-ishita ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


Improvments to ult checking

Made max/min limits for the blob counter larger (need for 1920x1200)
Added and max / min check for the limit of the rectangles we get, this will exclude the bottom hero selected abilities
Added some percentile math to get all the rectangles are are close to each other. The old code was including some 1/2 ult pictures, these then were not matching correctly. I.e 1/2 Wind Ranger was matching to Kunkka
Added a debug mode that take a match id. This makes it easier to run a scenario and debug.

Great idea about taking the match id to run a debug session


Plugin installation stucks on "Optimizing and caching browser bundles..."

Installation of Searchguard Kibana plugin stucks on "Optimizing and caching browser bundles..." messages for hours.
However, the installation seems to work.
I think https://docs.search-guard.com/latest/kibana-plugin-installation should be improved to reference possible kibana-plugin stucks and give some advices.
My version :

Kibana : version 6.3.2
Searchguard Kibana plugin: search-guard-kibana-plugin-6.3.2-14-beta-1.zip

Hereby some advices:
Change Kibana settings (log into a file and disable X-Pack features) :
Start plugin installation
$ cat kibana.yml
...
# log into a file (don't forget to configure logrotate)
logging.dest: /path/to/my/log/file/kibana.log

[...]

# disable X-Pack features
xpack.apm.enabled: false
xpack.graph.enabled: false
xpack.grokdebugger.enabled: false
xpack.ml.enabled: false
xpack.monitoring.enabled: false
xpack.reporting.enabled: false
xpack.searchprofiler.enabled: false
xpack.security.enabled: false

[...]

Check logs plugin installation :
$ tail -f /path/to/my/log/file/kibana.log | sed -r -e 's/^.*"@timestamp":"([^"]+)".*,"message":"(.*)"(,"prevState":.*)$/\1 | \2/g' -e 's/^.*"@timestamp":"([^"]+)".*,"message":"(.*)"}$/\1 | \2/g'
2018-08-03T12:41:19Z | uiSettings.enabled is deprecated and is no longer used
2018-08-03T12:41:30Z | Optimizing and caching bundles for stateSessionStorageRedirect, status_page, timelion, dashboardViewer, searchguard-login, searchguard-customerror, searchguard-multitenancy, searchguard-configuration and kibana. This may take a few minutes
2018-08-03T12:44:02Z | Optimization of bundles for stateSessionStorageRedirect, status_page, timelion, dashboardViewer, searchguard-login, searchguard-customerror, searchguard-multitenancy, searchguard-configuration and kibana complete in 151.97 seconds
2018-08-03T12:44:02Z | Plugin initialization disabled.

Exit the plugin installation script with "Ctrl+C".
Then, check if plugin Searchguard is installed.
$ bin/kibana-plugin list
<EMAIL_ADDRESS>
Finally, start Kibana server and check logs:
$ cat /path/to/my/log/file/kibana.log | sed -r -e 's/^.*"@timestamp":"([^"]+)".*,"message":"(.*)"(,"prevState":.*)$/\1 | \2/g' -e 's/^.*"@timestamp":"([^"]+)".*,"message":"(.*)"}$/\1 | \2/g'
2018-08-03T13:06:13Z | Status changed from uninitialized to green - Ready
2018-08-03T13:06:13Z | Status changed from uninitialized to yellow - Waiting for Elasticsearch
[...]
2018-08-03T13:06:13Z | Status changed from uninitialized to yellow - Initialising Search Guard authentication plugin.
2018-08-03T13:06:13Z | Status changed from yellow to yellow - Search Guard session management enabled.
2018-08-03T13:06:13Z | Status changed from yellow to yellow - Search Guard copy JWT params disabled
2018-08-03T13:06:13Z | Status changed from yellow to yellow - Search Guard multitenancy disabled
2018-08-03T13:06:13Z | Status changed from yellow to yellow - Routes for Search Guard configuration GUI registered. This is an Enterprise feature.
2018-08-03T13:06:13Z | Status changed from yellow to yellow - Search Guard system routes registered.
2018-08-03T13:06:13Z | Status changed from yellow to green - Search Guard plugin initialised.
2018-08-03T13:06:13Z | Status changed from uninitialized to green - Ready
2018-08-03T13:06:13Z | Server running at https://my-kibana-backend-server:5601
2018-08-03T13:06:15Z | Status changed from yellow to green - Ready
2018-08-03T13:06:15Z | Imported license information from Elasticsearch for the [data] cluster: mode: basic | status: active
2018-08-03T13:06:15Z | Status changed from yellow to green - Ready
[...]

I think Searchguard plugin is correctly installed because the login page with searchguard appears on URL https://my-kibana-reverse-proxy-url:5601 (backend server is accessed through a reverse proxy).
Does it exist a way to be sure that all Searchguard Kibana features have been successfully installed?

See also #101.

Hi,
I have the same problem when I remove the plugin
Kibana freezes
{"type":"log","@timestamp":"2018-09-18T09:46:08Z","tags":["info","optimize"],"pid":12295,"message":"Optimizing and caching bundles for stateSessionStorageRedirect, status_page, timelion and kibana. This may take a few minutes"}

Since Kibana 6.5.0 you can also give the --no-optimizeoption:
bin/kibana-plugin install https://url/to/search-guard-kibana-plugin-<version>.zip --no-optimize

(This is especially helpful when installing within a Dockerfile)

Closing this due to inactivity


Allow React 18 in peerPependencies

hi @KATT, I have not done any testing in React 18 yet, have you?

Just did some testing and this is working for me 🙌 , will merge

I have to merge this into my branch for permissions reasons...

@KATT i just publishedv3.3.2 which includes this change. feel free to use it with your react 18 apps!


Github action builds are taking too long

Builds are taking between 30-45 minutes, with a large portion involving installing Pods. Perhaps a cache mechanism should be used?

#108 introduces a basic caching mechanism for CocoaPods and Swift Package dependencies to address this issue. The caching mechanism caches the CocoaPods dependencies using the actions/cache GitHub actions. Unfortunately, adding fastlane to automate the build adds a small overhead that reduces the advancements of the better caching of dependencies.
A long-term solution would be to rely on self-hosted runners that provide way better performance than the GitHub runners that we currently use. GitHub promised to deliver self-hosted runners last quarter (https://github.com/github/roadmap/issues/507), so I hope that they are available very soon.
Most of the time is spent building the dependencies and a small portion on the project itself. A more aggressive build cache for the dependencies might also be an option that we could consider.


Fetching each coordinates from source to destination

need to fetch each coordinates dataset between source to destination (google maps dataset api maybe helpful). The data should be in a form of object such as
ex:
  {

      [
           {
                id: "(give indexing here)"
                lat: "(lat value)"
                long: "(long value)"
            }
       ],
       [
           (arrays will keep repeating till total we get total dataset )
       ]
  }

@nitro56565 ,where can I implement that in backend. mention source file path if possible

Hi @munnavuyyuru , as of now our project is undergoing a shift from react to ionic-react because of that this particular issue is on hold, sorry for that but soon we'll be moving on ionic-react and then you can solve this issue by that time you can research about how can we fetch each coordinates from a given route by google maps API

@nitro56565 ,fine and looking forward to work on


pod error:  panic: open /usr/local/go/lib/time/zoneinfo.zip: no such file or directory

I tried building and deploying the projecto k8s and I get this error in the pod logs:
Starting kube-monkey...
panic: open /usr/local/go/lib/time/zoneinfo.zip: no such file or directory

goroutine 1 [running]:
github.com/asobti/kube-monkey/config.Timezone(0x8)
	/Users/pswens200/dev/gowork/src/github.com/asobti/kube-monkey/config/config.go:77 +0xc5
github.com/asobti/kube-monkey/kubemonkey.Run(0xc420537f68, 0x1)
	/Users/pswens200/dev/gowork/src/github.com/asobti/kube-monkey/kubemonkey/kubemonkey.go:46 +0x5b
main.main()
	/Users/pswens200/dev/gowork/src/github.com/asobti/kube-monkey/main.go:23 +0xa0

Any ideas?

Wherever you are running kube-monkey it seems to need the zoneinfo.zip file in different places -
this appears to be dependant on your GOROOT environment variable setting... this will also be true inside the container - if you're going that far. :-)
Try;
zip /usr/local/go/lib/time/zoneinfo.zip /usr/share/zoneinfo/
Substitute /usr/local/go/lib/time/zoneinfo.zip, above, according to the no such file or directory error.
If you've set the "time_zone" in the /etc/kube-mokey/config.toml file, or via the examples/configmap.yaml, then make sure you pick a TZ that exists in /usr/share/zoneinfo/
HTH

This error is coming from kube-monkey being unable to find the timezone file that LoadLocation in the Go time package needs, since the default timezone is "America/Los Angeles". An alternative to creating the timezone file, is to use either the UTC or Local timezones. Those timezones are natively known.

kube-monkey could default to the local timezone in case of this error, although I feel that's more dangerous as we really don't want to be scheduling pods to be killed at unexpected times. I think panicking in this situation might be the outcome of least surprise.

changing the Dockerfile to FROM golang:1.7.5-alpine seems to resolve the issue.... any reason why this isn't a good solution?

@pswenson What timezone are you using that causes that error?

You may try to set time_zone="UTC" .

I also get stuck on this problem. Here is one solution for me ,maybe can give some help.
1)use "docker run -itd kube-monkey:v0.1.0 /bin/bash" to run a container
2)use "docker ps" to get its containerid
3)use "docker exec -it {$containerid} bash" to enter into the container
4)run "ll /etc |grep localtime" in the container and you will find it links to someplace:
localtime -> /usr/share/zoneinfo/Etc/UTC
5)In my case ,there is no zoneinfo directory under /usr/share/ in my container.
6)use "docker cp /usr/share/zoneinfo/  {$containerid} :/usr/share/" to copy the directory from host
7)use "docker commit {$containerid} kube-monkey:v0.1.1" to form a new image
The problem is solved for me using this new image "kube-monkey:v0.1.1"


Laravel 5.2

Hey @francescomalatesta,
Decided to bring this repo up to date with the current Laravel / Dingo-Api / Jwt / Cors releases.
I then went through the tutorial and everything seems to work.
Good write up btw! 👍
Feel free to review and merge if you like.
Cheers,
Angel

Thank you so much for your contribution :)


Regular Expression Denial of Service in postcss (6.0.11)

Do you want to request a feature, report a bug or ask a question?
Security issue.
What is the current behavior?
The package postcss versions before 7.0.36 or between 8.0.0 and 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern /\s sourceMappingURL=(.*).
<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>via<EMAIL_ADDRESS>Please tell us about your environment:

Node.js version: 16
webpack version: 4
svg-sprite-loader version: 6.0.11
OS type & version: macOS

Did you find a decent fix for this? In the past I managed to override postcss used, but I'm now getting
npm ERR! code EOVERRIDE
npm ERR! Override for<EMAIL_ADDRESS>conflicts with direct dependency

Did you find a decent fix for this? In the past I managed to override postcss used, but I'm now getting
npm ERR! code EOVERRIDE
npm ERR! Override for<EMAIL_ADDRESS>conflicts with direct dependency

No. Unfortunately, I am waiting for a fix.

Hi, any updates here?


file,server: add method for parsing JSON with custom validation

Fixes: https://github.com/moov-io/ach/issues/944

Codecov Report

Merging #950 (5a1343a) into master (53d83f9) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 5a1343a differs from pull request most recent head 953f8f5. Consider uploading reports for the commit 953f8f5 to get more accurate results

@@           Coverage Diff           @@
##           master     #950   +/-   ##
=======================================
  Coverage   91.30%   91.30%
=======================================
  Files          66       66
  Lines        5244     5247    +3
=======================================
+ Hits         4788     4791    +3
  Misses        283      283
  Partials      173      173


Incorrect order of sizes.

Go to any category
Look at 'Size' section

Current:
Incorrect order of sizes: S M L XS XL

Expected:
There should be: XS S M L XL

I'd like to work on this.

@diboy2 ok, go for it :)

Hello @pkarw ,
I don't think I'm able to do this issue since I don't have enough ram to use linux and get mage2vuestorefront running.

@pkarw nvm, I found a fix. https://github.com/DivanteLtd/vue-storefront/pull/1797


Feature/core 381 design settings

Fixes # .
Changes proposed in this PR:

create a tab for the settings options
create a component for general settings
create a component for asset signals
create a component for publisher signals

Not sure of the goal of this PR but this looks out of scope for this repo, so closing.


Date Picker cutting from right side

Hi, you should check your custom css, this seem to be a conflict with your template

Hi, I'll be closing this as there's no feedback from original poster, feel free to re open it if need it.


[cxx-interop] Allow conforming C++ APIs that return IUO to Swift protocols

If a C++ method returns a pointer and is not annotated with returns_nonnull, ClangImporter imports its return type as implicitly unwrapped optional UnsafePointer<T>!. This happens, for example, for begin()/end() methods of C++ collection types.
We would like to be able to conform C++ collections to Swift.Sequence/Swift.Collection/... To make this work, we create Swift protocols that require func begin() -> RawIterator and func end() -> RawIterator where RawIterator is an associated type.
The problem is that currently if RawIterator is UnsafePointer<T>?, begin()/end() methods that return an implicitly unwrapped optional UnsafePointer<T>! won't satisfy the requirements. This change fixes that.

@swift-ci please smoke test

IMHO the right way to fix this is to annotate C++ to be const int * _Nullable returnPointer() { return nullptr; }. That should conform, right?

@hyp ClangImporter currently ignores both _Nullable & _Nonnull, so a _Nullable method would still get imported as IUO. We could add the support for those (and we probably should do that anyway), however I think having to annotate all begin()/end() methods via API notes would be too much work for the user for little benefit. We also can't do that in the short term since API notes don't allow annotating types like std::string, std::vector, etc. This implicit conversion trick already exists for ObjC interop, and I think we could apply it for C++ interop as well.

I see, that makes sense


Docker image - root required

Describe the bug
The Docker image runs on root by default which is both insecure and prevents the container from running in secured environments (like Gitlab CI).
If the user is specified (i.e. by providing --user 1000 flag), the container fails.
Sample
❯ docker container run --user 1000 --rm -ti springcloud/spring-cloud-contract:3.0.2 ./gradlew clean build

ERROR: JAVA_HOME is set to an invalid directory: /root/.sdkman/candidates/java/current/

Please set the JAVA_HOME variable in your environment to match the
location of your Java installation.

@marcingrzejszczak will try to submit a PR today to have it run with a non-privileged user (1000:1000). @szczad specifying an arbitrary user won't work, as the user would need to be created in the docker image first.

Great! I was also thinking whether maybe we shouldn't be using Paketo buildpacks to actually properly build the docker image. WDYT ?

Yeah I could look into that, too. Building the image right now directly, but build packs would be definitely nicer.
On Aug 9, 2021, at 13:51, Marcin Grzejszczak<EMAIL_ADDRESS>wrote:
Great! I was also thinking whether maybe we shouldn't be using Paketo buildpacks to actually properly build the docker image. WDYT ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fspring-cloud%2Fspring-cloud-contract%2Fissues%2F1639%23issuecomment-895159308&data=04|01|bdoetsch%40vmware.com|37f92dcc1b3f43d1d44708d95b2c10c6|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641067089854531|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=21do6w3X0vF65br70GsROEXyH5QYLSnM%2BatQrkUo9Ic%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEZXT2MPCOAA4B2Z2DFH3KLT366NDANCNFSM427GEN3Q&data=04|01|bdoetsch%40vmware.com|37f92dcc1b3f43d1d44708d95b2c10c6|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641067089864486|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=M6B7Hu13j8yV%2FgQNglEaR1xQRUGwhFuAbsvReMJR79U%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|bdoetsch%40vmware.com|37f92dcc1b3f43d1d44708d95b2c10c6|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641067089864486|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=wUV6AQ%2FpvDeipxiQpWN6dfj8fQ%2Fn5xLytoqNp0zdwCY%3D&reserved=0 or Androidhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26utm_campaign%3Dnotification-email&data=04|01|bdoetsch%40vmware.com|37f92dcc1b3f43d1d44708d95b2c10c6|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641067089874443|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=51hkZUb9IBCoIaAtcKVYDUo3nIwkFSnnZPnC2FLel0Q%3D&reserved=0.

I did this in the following way:

Remove the following from spring-cloud-contract-stub-runner-boot/pom.xml:

org.springframework.boot.experimental
spring-boot-thin-layout
${thin-jar.version}

Run:
./mvnw clean spring-boot:build-image -pl spring-cloud-contract-stub-runner-boot

I assume if the kafka and rabbit dependencies are added in their non-thin configurations, that's all that woul be needed?
I also included actuator in my build... It was good to have some endpoints at :8750 to test and also I envision if this is ever run on Kubernetes it might be helpful to have the health endpoints (liveness/readiness). Would be great if all of the stubs registered with the mappings endpoint, but I don't see that happening today.

Actually using the buildpacks may be a breaking change so if we can start with fixing the current docker setup then that would be a good start

I have a version ready on my branch, gotta test it though. It's here: https://github.com/bastiandoetsch/spring-cloud-contract/tree/issue_1639_Docker_image_-_root_required
On Aug 9, 2021, at 20:32, Marcin Grzejszczak<EMAIL_ADDRESS>wrote:
Actually using the buildpacks may be a breaking change so if we can start with fixing the current docker setup then that would be a good start
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fspring-cloud%2Fspring-cloud-contract%2Fissues%2F1639%23issuecomment-895444958&data=04|01|bdoetsch%40vmware.com|99cece1e781047daa76f08d95b63fb86|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641307244529844|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=qJJ%2BtdTZm79CZt8wU2NXpp8X6BcSKXEvVAh9nNP8FJM%3D&reserved=0, or unsubscribehttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEZXT2LPFOMYOTFA3JYD32TT4ANKDANCNFSM427GEN3Q&data=04|01|bdoetsch%40vmware.com|99cece1e781047daa76f08d95b63fb86|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641307244539798|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=bdorhQfo68xtXuNfaI%2B%2FzHWcTPUOR7CzXwj6U1wAJEI%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|bdoetsch%40vmware.com|99cece1e781047daa76f08d95b63fb86|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641307244539798|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=bltNFVOAe5Y3L4rO6sZufoY87VADiS4Y%2FTiqzvIU%2F6g%3D&reserved=0 or Androidhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26utm_campaign%3Dnotification-email&data=04|01|bdoetsch%40vmware.com|99cece1e781047daa76f08d95b63fb86|b39138ca3cee4b4aa4d6cd83d9dd62f0|0|0|637641307244549754|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=z7d0LxNAweuOIOb%2BLDicGHcTTlkrxT9EPnfxPUpDfyU%3D&reserved=0.


Add more spacing in SCM trees between indent guides and icons

VSCode Version: 1.51
OS Version: Windows 10 (19.09?)

Steps to Reproduce:

Open a git repo
Make changes
Set "workbench.tree.renderIndentGuides": "always" in settings.json
Notice how lines overlap or are close to overlapping with icons

Does this issue occur when all extensions are disabled?: Yes

Yeah unfortunately we're closing this as designed. The real indentation to follow is the text indentation. The current default of 8px means that the indent guide might collide with icons. There are a few workarounds: increase indentation via setting and disable icons. Sorry about that!

Thanks @joaomoreno


Add ' ' to $destination that way spaces can be used in path

Currently if your runner path on a self hosted instance has a space, the setup process will fail because Get-FileHash cannot run with ' ' to define the path if your username has a space, seems like an easy fix that would allow TEST CI to work, however if this wouldn't be desired then it would be nice to note somewhere that you have to have a path with 0 spaces.

I am a little confused by how the username would affect the paths used here.  AFAICT, actions/runner should be using the runner temp dir RUNNER_TEMP not the user's TEMP/TMP (https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables).  And, Github recommends installing the runner on Windows in a folder under the root of a drive to avoid long path issues (https://github.com/actions/runner/releases/tag/v2.289.1).  I guess they don't mention not having spaces in that path...

I am a little confused by how the username would affect the paths used here.  AFAICT, actions/runner should be using the runner temp dir RUNNER_TEMP not the user's TEMP/TMP (https://docs.github.com/en/actions/learn-github-actions/environment-variables#default-environment-variables).  And, Github recommends installing the runner on Windows in a folder under the root of a drive to avoid long path issues (https://github.com/actions/runner/releases/tag/v2.289.1).  I guess they don't mention not having spaces in that path...

I wasn't necessarily understanding what the issue was in the first place because the error was so vague, however the glaring problem at hand was the lack of ' ' in the pathing, changing my file path to include 0 spaces fixed the issue, however I thought this as just a minor oversight, considering it's mostly used for github virtual environments

for self hosted CI, could we make the msys2 path changes permanent, that way we wouldn't have to reinstall it everytime? It's just a major pain to do

I found the same.  What I do in that case is install msys2 myself into C:\msys64, and use release: false option.

@MasonT8198 as @jeremyd2019 suggested, you can use release: false to avoid installing MSYS2 from scratch in each run.
Furthermore, we might enhance location (https://github.com/msys2/setup-msys2#location) to be used in https://github.com/msys2/setup-msys2/blob/main/main.js#L231, if that's something you need.

@MasonT8198 as @jeremyd2019 suggested, you can use release: false to avoid installing MSYS2 from scratch in each run.
Furthermore, we might enhance location (https://github.com/msys2/setup-msys2#location) to be used in https://github.com/msys2/setup-msys2/blob/main/main.js#L231, if that's something you need.

Sorry this is a really late reply, I think it would be useful if I could store my msys2 build on a shared drive or the non c drive. however not necessarily necessary.
I'll go ahead and close this issue as my original issue has been resolved which I'm very thankful for!


Fix typeable dates with custom format (non-US)

As we were having problems in our project with typeable dates, we did this modification to make custom (non-US) dates parseable for Date.Parse.
We have added function, based on Kooiinc's generic method to parse dates with different formats, to convert dates with custom format to generic format that can be parsed.

Coverage remained the same at 100.0% when pulling 25bb4824f0f75864bdfd83726b6868068b0cf1d8 on barbosaalr:master into bf28bcaa4453f66572e3af496dfb2ffc801a9cee on charliekassel:master.

Hello, I'm struggling from the same issue.
Is this fix in npm already?

Hello, I'm struggling from the same issue.
Is this fix in npm already?

Nope, not yet...

I'd love to see this PR accepted!

@charliekassel This PR is a life saver. Could you please merge it?

@charliekassel could you look at this pr, would be nice to know if it will get merged or not?

@barbosaalr This PR cover case when format option is a function?
@tdmitriiv Maybe a good idea is to implement something like that:
https://bootstrap-datepicker.readthedocs.io/en/latest/options.html#format
... Or, only allow format options as string, not function.

Btw. this won't work inside safari because it can't parse the timezone.

Hello! Is there a quick way to implement this changes? Should I just edit the files in the node installation directly? Thank you!

Just came across this issue, any update for this?

any news??????

Facing this issue as well! Please approve!

Any news on this yet?! Could really use with this merge

I have the same issue.

I have same issue too, Has this bug been fixed yet? type in 1/6/2020 to mean 1st June 2020. But the pop-up locks to 6th Jan 2020.

This won't be fixed.
The issues an PR's are pilling up. You should move to another repo, there are forks of this repo that fix a lot of issues


Integrated terminal doesn't open

Issue Type: Bug
The terminal window flashes and then closes, whether I open it via View -> Terminal (or the corresponding shortcut), or by trying to run any script.
This issue was present in older versions of VS code (#42711, #42627), and it is happening again in the latest one.
VS Code version: Code 1.54.1 (f30a9b73e8ffc278e71575118b6bf568f04587c8, 2021-03-04T22:38:31.419Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: enabledrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.82GB (9.94GB free)

Process Argv
--crash-reporter-id d44b3eb0-31b0-412e-b0dd-9c4832b3c9a6

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
dockersubset:30265998
pythontbcf:30265426
vspre833cf:30267465

Any issues in dev tools?

Any errors in dev tools?

I'm not familiar with dev tools, but I can see this error:

The terminal now opens, after enabling compatibility mode (right click on Code.exe -> Properties -> Compatibility -> check Run this program in compatibility mode for Windows 8).
The issue now is that the terminal is blank, whether I run any script or try to type something in it. It happens with all shells (PowerShell, cmd, bash).

Problem solved. I moved the VS Code folder from C:\Users(YourUser)\AppData\Local\Programs to C:\Program Files. I also removed it form PATH. Now it works perfectly.


Simplify app settings

I realise that people get confused when having a lot of options to set in the app settings, therefore a way to overcome this is by showing just the basic parameters:

IP or hostname
Username
Password

And the remaining options should be handle in another "advanced"  window.

Done!


Factor out low-level http server concerns

Right now, Tide defines several general-purpose data types (like Body) and mucks around with futures-compat layers for using Hyper. These things aren't Tide-specific, and should be factored out as a separate crate that layers on top of Hyper, so that others can use them more easily.

FYI: I'm working on this issue.

@aturon there is also a new Actix-http http library, I find.

The refactor in https://github.com/rust-net-web/tide/pull/139 took a major step in this direction, but we'll ultimately want to move out the shim code into its own crate and make Tide truly modular in this respect.

There is also actix-http, It support HTTP1/2 Server/Client and Websocket Server/Client.

This is done as of #140!


docs: Update README to include changes to variables

The variable cluster_security_group_id was removed from the module, but the README still included it.
Description
Documentation update to fix an example.
Motivation and Context
The example in the documentation contained a variable that was removed.
Breaking Changes
No breaking changes.
How Has This Been Tested?
Tested this locally when trying to use the module.

This PR is included in version 19.7.0 :tada: