Https error (Forbidden 403) in some plesk hoting areas

Hello sirs and thank you for your great work,
I'm using your application since almost a year, but had to move the update files to another hosting area, in that area I kept getting "Forbidden 403-Access denied" error despite that the directory listing is working and Json file is accessible from the browser.
That took me three days until I accidentally found someone talking about the "user-agent" header (see this link : https://stackoverflow.com/a/2794346 ), so I decided to clone your code and debug it my self.
then I changed couple places:
1- file: "nUpdate.Shared\Updating\UpdateConfiguration.cs"
Method :
public static IEnumerable Download(Uri configFileUri, NetworkCredential credentials, WebProxy proxy, int timeout = 10000)
Changed this code:
wc.Encoding = Encoding.UTF8;
if (credentials != null)
    wc.Credentials = credentials;
if (proxy != null)
    wc.Proxy = proxy;

to this:
wc.Encoding = Encoding.UTF8;
if (credentials != null)
    wc.Credentials = credentials;
wc.Headers.Add("user-agent", "Only a test!");
if (proxy != null)
    wc.Proxy = proxy;

2- file "nUpdate.ProvideTAP\Updating\UpdateConfiguration.cs",
Method:
public static async Task<IEnumerable> DownloadAsync(Uri configFileUri, NetworkCredential credentials, WebProxy proxy, CancellationTokenSource cancellationTokenSource = null, int timeout = 10000)
change this code:
// Check for SSL and ignore it
ServicePointManager.ServerCertificateValidationCallback += delegate { return true; };
var request = (HttpWebRequest)WebRequest.Create(configFileUri);
request.Timeout = timeout;

To this:
// Check for SSL and ignore it
ServicePointManager.ServerCertificateValidationCallback += delegate { return true; };

var request = (HttpWebRequest)WebRequest.Create(configFileUri);

request.UserAgent = "Only a test!";
request.Timeout = timeout;

then the issue is gone from the administration application..
So I suggest that you add an option to specify the request headers and also allow the user to specify custom client for the request and setting a default "user-agent" header for the administration and all parts of the application.
The version I'm using is v3.5.0
Thank you for your effort

Hi,
I will see when I will have time to do so.
If you want you may also add this feature and provide a pull request.
Best,
Dominic

A default user-agent header is now available (thanks to @FireEmerald) with the newest develop-v3 commit. I will have a look at when I will be able to release a new version. Until then one may build the solution as-is and use this version.
Best,
Dominic


Enable off-main-thread rendering on macOS

In https://github.com/servo/webrender/issues/1640 we discussed how Firefox
(and probably also other browsers) have a compositor thread, which is not the
main thread, that does all their OpenGL calls. In glutin this kind of
architecture doesn't seem to be possible right now since it's not possible to
split the GlWindow into the window and the context, and the Context
doesn't implement Send on macOS.
The following two changes allow such architectures:

Implement Send for Context on macOS. The Apple docs suggest that this is correct.
Add a split method to GlWindow that allows obtaining an owned Window and Context.

cc @mitchmindtree @mstange @glennw

I don't like this change as it is, because destroying the Window before the Context (which you could do with this split method) is a really bad idea.

Interesting, that makes sense. I'll see if I can think of some way to use the borrow checker to fix that, if possible.

Okay here's a sketch of my new idea, I'm not sure when or if I'll get around to fully implementing it though:
trait RenderThread {
    type Message;
    type State;

    // these are both called only on the render thread

    /// sets up state that needs the context, and probably sets context as active for this thread
    fn init(ctx: &Context) -> State;
    /// called by render thread event loop on getting an mpsc message
    fn got_message(ctx: &Context, state: &mut State, msg: Message);
}

struct ConcurrentGlWindow<R: RenderThread> { ... }

enum RenderThreadMsg<T> {
    // handled by the thread's loop, drops the context and shuts down the thread
    Close,
    // calls got_message with the contained message
    Inner(T),
}

impl<R: RenderThread> ConcurrentGlWindow<R> {
    // this is the main loop of the render thread, called from a thread::spawn somewhere
    pub render_thread_loop(render_thread: R, ctx: Context, rcv: mpsc::Receiver<RenderThreadMsg<R::Message>>) {
        // 1. do context initialization that has to be done on the render thread, if any
        ctx.do_setup_stuff();

        let mut state = render_thread.init(&ctx);

        for msg in rcv.into_iter() {
            match msg {
                RenderThreadMsg::Close => break,
                RenderThreadMsg::Inner(m) => render_thread.got_message(&ctx, &mut state, m),
            }
        }
    }

    // enable the main thread to send messages to render, like new frame data
    pub fn sender(&self) -> &mpsc::Sender<RenderThreadMsg<R::Message>> { ... }
    // on platforms that don't support off-main-thread rendering, this manually ticks the render thread event loop on the main thread. When there is a separate thread, it does nothing.
    pub fn tick(&self) { ... }

    pub fn window(&self) -> &Window { ... }
}

impl Deref for ConcurrentGlWindow { type Target = Window; ... }

impl Drop for ConcurrentGlWindow {
    fn drop(&mut self) {
      self.sender.send(RenderThreadMsg::Close);
      self.thread_join_handle.join();
    }
}

Thoughts?

Theoretically, the correct and easiest fix would be to implement Sync on Context and !Sync on Window, so that the reference grabbed by calling gl_window.context() can be sent to another thread.
However you are probably going to run into lifetime issues when trying to use this design in practice.

@tomaka implementing Sync on Context would be partially correct, but I don't think it would be fully correct.
On macOS, each thread has its own OpenGL context, and you are only supposed to do calls on that context from one thread at a time. You can do it from multiple threads, but only if you synchronize them. If Context was Sync you could activate it on multiple threads and do concurrent OpenGL calls with nothing stopping you. With ConcurrentGLWindow you can only ever activate the OpenGL context on the render thread, which stops you from doing unsynchronized OpenGL calls.
Also the ConcurrentGLWindow approach works on both platforms that do and don't support off-main-thread OpenGL with the same code, as long as you call .tick() in your event loop.

On macOS, each thread has its own OpenGL context, and you are only supposed to do calls on that context from one thread at a time. You can do it from multiple threads, but only if you synchronize them. If Context was Sync you could activate it on multiple threads and do concurrent OpenGL calls with nothing stopping you. With ConcurrentGLWindow you can only ever activate the OpenGL context on the render thread, which stops you from doing unsynchronized OpenGL calls.

That's the reason why the methods on the GlContext trait and the OpenGL functions themselves are both unsafe. Glutin will never protect you against this one-context-per-thread thing.


time.Parse: why not literals?

This is rather a feature request.
New to GO I'm just wondering why go is using this crazy time literal "2006-01-02 15:04:05" instead of "yyyy-mm-dd HH:MM:SS" for parsing time objects? Nobody can remember this date string bu everybody understands immediately the character based pattern.
Also it would be nice to implement to the encoding/json and encoding xml for the  xml:"mytimestamp,attr" for DecodeElement like this: xml:"mytimestamp,attr,format:yyyy-mm-dd HH:MM:SS"

For questions about Go, see https://golang.org/wiki/Questions
For a proposal to change encoding/json and encoding/xml, please file a separate issue to describe this proposal.

I've just been bitten by the date format, it really does need revisiting.
The bug I had was "2006-1-2" means yyyy-dd-mm but I wanted "2006-2-1" (yyyy-mm-dd)
The fact that I need to represent the desired date in the yyyy mm dd format to clarify to readers should be a big hint as to why I had a bug.
I honestly cannot believe magic numbers is the right way to go.
Given that Go is 10+ years old, is there a possibility of having a sister representation, so developers can choose whichever they prefer.

@shane-howearth This issue has been closed for a while.  Commenting here has no effect.
You may be interested in packages like https://pkg.go.dev/github.com/jehiah/go-strftime?tab=doc (I don't know anything about that package other than the docs).
Providing a separate representation in the standard library would require going through the proposal process: https://golang.org/s/proposal.


backbone_dir

when I want to test this model ,there is a question,i guess that is I don't have the pretained model,can you give the download path to me ?

https://github.com/SwinTransformer/storage/releases/download/v1.0.0/swin_large_patch4_window12_384_22k.pth

thank you very much

A little busy the last few days.When I need to download this,there is a problem,may I get this permission?

https://github.com/SwinTransformer/storage/releases/download/v1.0.0/swin_large_patch4_window12_384_22k.pth

This download link is restricted, I hope to be able to give a permission. thanks.


Spanish Translation

Work In Progress!
planned completion before 04/01/2017 (dd/mm/yy)

Sorry about all the commits. I didn't know it would do that.

Date for planned completion should read 1/4/2017 (dd/mm/yy)  not 4/1/2017. Pardon my noobness.


os/signal: TestStop flaky on DragonFly

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.10
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
DragonflyBSD amd64
The builder sporadically fails with this message:
ok  	net/url	0.021s
ok  	os	2.430s
ok  	os/exec	1.919s
--- FAIL: TestStop (1.98s)
signal_test.go:32: timeout waiting for window size changes
FAIL
FAIL	os/signal	10.420s
ok  	os/user	0.009s
ok  	path	0.008s
2018/04/25 07:54:09 Failed: exit status 1
If this is indicative of an OS bug, I need to know what this test is doing so I can report it to the OS team.

According to greplogs the failures are all quite new, although the test has been there since 2013.
2018-04-21T20:20:37-20c98dc/dragonfly-amd64
2018-04-22T17:30:54-15095be/dragonfly-amd64
2018-04-23T18:18:01-0cd0dc9/dragonfly-amd64
2018-04-24T18:58:45-5d4267e/dragonfly-amd64
2018-04-24T21:49:40-011f6c5/dragonfly-amd64
2018-04-25T15:24:07-01a7487/dragonfly-amd64
2018-04-25T16:06:54-25813f9/dragonfly-amd64
2018-04-25T17:08:07-f2df0ec/dragonfly-amd64
2018-04-25T20:19:19-9e0e698/dragonfly-amd64
2018-04-25T20:22:06-932794c/dragonfly-amd64
2018-04-25T21:34:15-c5f0104/dragonfly-amd64

findflakes says
First observed 20c98dc 21 Apr 20:20 2018 (54 commits ago)
Last observed  c5f0104 25 Apr 21:34 2018 (0 commits ago)
100% chance failure is still happening
19% failure probability (11 of 55 commits)
Likely culprits:
   19% 20c98dc cmd/link: skip TestRuntimeTypeAttr to fix build
   15% 0a129db misc/cgo/testcshared: use file descriptor 30 for TestUnexportedSymbols
   12% dfb1b69 os/signal: add func Ignored(sig Signal) bool
   10% 37dd7cd runtime: use sys.PtrSize in growslice
    8% 566e3e0 cmd/compile: avoid runtime call during switch string(byteslice)
    7% f6ca6ed net: document caveats for (*syscall.RawConn).Write on Windows
    5% d487488 cmd/internal/obj/x86: disallow PC/FP/SB scaled index
    4% dd71e3f cmd/compile: refactor how declarations are imported
    4% 514018c cmd/internal/obj/x86: ifelse->switch, named const for cap=6
    3% 21fa148 cmd/internal/obj/x86: add named consts for Prog.Back flags
No known past failures

Presumably the new failures are somehow due to https://golang.org/cl/108376, which added two new tests that run before TestStop.  The new test  TestIgnored does fiddle with SIGWINCH.  It resets the handling of the signal, but perhaps something goes wrong with that somewhere.  It is definitely odd that we're only seeing a problem on DragonFly, but it's possible that there is some bug in the  DragonFly support in the runtime package.

You can probably make this fail 1 out of 10 times or so by running
go test -c os/signal
./signal.test -test.run='TestStop|TestDetectNohup'

If that works for you--that is, if the test fails--could you attach the DragonFly equivalent of strace -f output for a failed run, so we can see what system calls the test is making?  Thanks.

Possibly related to the race in https://github.com/golang/go/issues/20748?

@ianlancetaylor I tried to run the test you suggested, but where is "signal.test"? Does something generate that?

where is "signal.test"? Does something generate that?

signal.test is the output generated by go test -c os/signal. I believe it is written to your current working directory.
(See https://golang.org/cmd/go/#hdr-Test_packages for more detail.)

@bcmills I forgot the -c option, thanks. Attached is the ktrace from a TestStop failure.
ktrace.zip

Interesting, I can't get this failure to occur if I run this test on a single CPU VM, but it readily happens on a dual CPU VM.

Adding human-readable format of ktrace.
ktrace_dump.txt

The builder is running dragonfly release 5.2.0, but I've confirmed that the flakiness in this test also happens on the most recent development branch. I can't recall for sure, but the appearance of this failure might very well coincide with switching the builder from a single CPU to a dual CPU VM a month or so ago.

Thanks for the ktrace output.  Unfortunately I don't see anything unusual in it.  The SIGWINCH signal is being delivered twice, as expected.  The first one is being ignored, as expected.  For some reason the second one is not being sent on the channel.

Thanks, if you can give me a description of what this test does, I can run it by the dev team.

I'm not sure that description will help, as most of the activity is in the Go signal handler.
That said, the failing test is TestStop in os/signal/signal_test.go.  It raises SIGWINCH signal which will be caught and discarded.  Then it calls signal.Notify to ask for notifications of SIGWINCH signals.  Then it raises SIGWINCH again.  The signal is caught again and, this time, the Go runtime should set a bit in sig.mask (in runtime/sigqueue.go) and wake up the goroutine sleeping in signal_recv (same file).  The latter goroutine should observe the signal in sig.mask and send a notification on the channel.  The test goroutine should receive that notification and carry on.  The ktrace shows that the second SIGWINCH is delivered and caught.  Something after that is going wrong, but I don't know what.  As you can there are several steps involved.

I played around some with signal_test.go and discovered that if I increase the timeout in waitSig to 1900 * time.Millisecond, then I can no longer get it to fail by repeatedly running signal.test.

I know what's happening. See this commit:
http://gitweb.dragonflybsd.org/dragonfly.git/commit/afd7f1247cb20d5b03f8ccddb470de6a55afc530
Note that the default cap on the timeout for umtx_sleep() is 2 seconds and notice the time in the FAIL: TestStop message - 1.99s. If I increase sysctl kern.umtx_timeout_max to 3 seconds, then the FAIL message time changes to 2.99s. So, the question is what's causing umtx_sleep to hit its max timeout.

Thanks for the tip.  I can recreate the problem.  As far as I can tell, there is sometimes an unreasonably long period of time between a call to umtx_wakeup and the time that the thread that has called umtx_sleep starts running.  So I agree that this seems clearly related to the kernel change.
I see that the kernel changes discusses fork.  I can see the problem consistently when I run both TestDetectNohup and TestStop, but I do not see the problem when I run only TestStop.  One interesting thing about TestDetectNohup is that it uses the os/exec package to run another program, which of course uses fork.
The sequence is

signal_recv calls umtx_sleep
TestDetectNoHup calls fork, twice
TestStop triggers a signal
the signal handler calls umtx_wakeup
occasionally the umtx_sleep called by signal_recv fails to wake up immediately

So if fork is somehow disassociating the umtx_wakeup from the previous umtx_sleep, that could cause the problem we are seeing.
Both the umtx_wakeup and umtx_sleep calls are using the address &sig.note, where sig is a package-scope variable defined in runtime/sigqueue.go.

If either fork is executed in TestDetectNohup, then the test is flaky. When I remove both, it passes every time.

It sounds like you've demonstrated that this is a bug in the DragonFly kernel, so I guess we should just skip the test on DragonFly.

I'm awaiting clarification from the dev team

Dragonfly has found the issue and will fix the timing window in the kernel. I'll be testing a patch soon.

Great, thanks!

The fix has been committed to the master branch and I've cherry picked it for the builder:
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/efbd013239d66d591bfbc71ed58d36141e70b76c
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/6481baf48ca2078fc4844f9814bc9aeda81a8f5d

@tdfbsd Thanks!


The LOCK file is not being removed

When using db.close() it is not removing the LOCK file in the database folder.

This is as expected. The LOCK file will not be deleted on db.close(). LOCK file does not work by removing or adding a file. See https://stackoverflow.com/questions/575328/fcntl-lockf-which-is-better-to-use-for-file-locking for detail.


Bitburner optimization

Adds a greedy numerical approximation function to guide commodity purchasing decisions for Corporation gameplay in the game "Bitburner."


Initial generation locking

Ensuring a lock is present on initial generation
Making sure both expire and lock keys have cleanup TTLs

:accept:


Wiki?

If time allows, I think it would be cool to add a wiki that goes over the variables and how they work, just something like "xBool is set to true when y and is set to false when z"

Hi there,
Thanks for your suggestion. EliteVA can output tens of thousands of variables in a session, making it challenging to cover each one comprehensively. One of the key features of EliteVA is that the plugin is prone to future Elite Dangerous versions, meaning that in the case of events being added or changed in the future the plugin still functions as expended and picks up on these changes without hiccup. This dynamic way of detecting and generating VoiceAttack variables makes it harder to write documentation on specific variables or events.
However, there are some excellent resources available to help players understand these variables better:

Elite Dangerous Official Journal Manual
The Elite Dangerous developers have put together a comprehensive manual that covers most of the game's events, when they are triggered, and what their contents are. You can find this manual at https://hosting.zaonce.net/community/journal/v37/Journal_Manual_v37.pdf.

Live Tools
You can also check out EliteVA's 'live tools' feature, which provides information about variables set by the plugin. You can find it on my documentation website here https://docs.somfic.dev/projects/eliteva/live. The Variables section provides a list of variables which are currently set. The Records section you can find a list of variables that could potentially be set. Note that the EliteVA plugin needs to be running locally for these tools to function.

Firey Toad's tutorials
Twitch streamer Firey Toad has made a set of tutorial videos which can be found here https://www.youtube.com/watch?v=wkdpLXa1eqo&list=PLALj9exX2tHXdjsd6hx5fahOAqxGaArsD. These videos can help people get started with the plugin and give them inspiration for macros they could create with the plugin.

In many cases, variable names are self-explanatory, which can make it easier to understand their purpose.
However, if you have specific questions or need clarification on certain variables or groups of variables, I can offer to elaborate on them and add the explanations to the documentation website, let me know! I'm happy to answer questions :)

First off this was a very detailed response to such a short suggestion, thank you. I don't currently have questions on a particular variable, so I think I will close this now, I was mostly looking for somewhere that had all of them in case there were any that I didn't see yet. Thank you for the links btw, I will be checking them out


Fix random crashes

Fixed random crashes due to elements not being initialized when trying to use library elements on hooks/functions.

Thanks!


i have an issue just cloned the repo, but it is loading forever

I think that your code is running on CPU. You must change the device variable to 'cuda' to run it. If you are using Google colab, you must change the runtime to GPU

hello, yeah sure @Kabanosk


More concrete type annotations

Preliminary Checks

[X] I've searched Google & GitHub for similar requests and found none.
[X] I've reviewed the confluent intro page and the confluent kafka python docs and believe this feature is missing from the typings.
[X] I understand that this repository is specifically for type annotations of the Kafka client. If my request is about Kafka client features or functionalities, I need to raise it in the Confluent Kafka Python repo.

Feature Details
Add more specific type annotations to be used with tools like pyright in strict mode.
Pyright in strict mode requires that all generic types be fully specified. Because of this, some method calls, although appearing to be valid, produce an error:
def report_delivery(error: KafkaError | None, msg: Message) -> None:
    if error is not None:
        print(error)

producer.produce(topic, value, on_delivery=report_delivery)
# error: Type of "produce" is partially unknown
#    Type of "produce" is "(topic: str, value: str | bytes | None = None, key: str | bytes | None = None, partition: int | None = None, on_delivery: ((...) -> Unknown) | None = None, timestamp: int = 0, headers: dict[str, str | bytes] | list[tuple[str, str | bytes]] | None = None) -> None" (reportUnknownMemberType)

Please take a look at #159

Hello @navoyan, thanks for the feedback and PR!
I will take a look this weekend.


build fail for stable rust

error[E0658]: arbitrary expressions in key-value attributes are unstable
--> /Users/simon/.cargo/git/checkouts/async-raft-c411f5c0ea29c115/ca6ba30/async-raft/src/lib.rs:1:10
|
1 | #![doc = include_str!("../README.md")]
|          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #78835 https://github.com/rust-lang/rust/issues/78835 for more information
error: aborting due to previous error
For more information about this error, try rustc --explain E0658.
error: could not compile async-raft
To learn more, run the command again with --verbose.

I had this issue for another project, and fixed it by updating to rust 1.55. See if that fixes this for you.

Thank you @Frederik-Baetens


[Question] How to enable editing of existing token?

Once a user has created tokens, is there a way to enable editing of a created token?
E.g. if the user has created these tokens: [Swift], [Visual Basic], [Objective C] set, how can the change the token in place by:

tapping on the token, then
typing the new input e.g. [Swift language] (without deleting any tokens)

After the edit to the token, the resulting tokens will be [Swift language], [Visual Basic], [Objective C]

Currently, there is no way to edit a token. It can be deleted, but edited for now.


Modifications for multi testcases handling, fixing some bugs

Optional parameter added to function createTestRun: Reduces run to only tests in parameter array (fix for all testcases staying 'InProgress' https://github.com/gianlucamangiapelo/wdio-azure-devops-service/issues/8, but needs adaptions in service as well )
Added continuiation token in testCasesPoints: with old function maximum 200 testcases were extracted
Changed version from wrong 0.0.6 to last git version(0.0.8) plus 1 =0.0.9
Followin needed for multiple automated tests matching on one manual test:
-- Set failed result to dominant result (failed+passed=> failed)
-- Testcase comment also included and adapted for multiple testcases

maybe you can also have a look if the package runs well. i am not able to run it properly because husky is throwing an error. maybe updating packages?
terminal: npm i gianlucamangiapelo/azuredevops-test-reporter#pull/1/head
npm ERR! command failed
npm ERR! command sh -c -- husky install
npm ERR! .git can't be found (see https://git.io/Jc3F9)

i commited a workaround to suppress the husky error, but please still have a look at it

Hi @HolKowal thanks for your contribution.
I appreciate 🚀
During the weekend I'll review the PR and let you know!
Thanks

hey @gianlucamangiapelo have you found the time to check?
i also have another PR of your wdio service in queue https://github.com/HolKowal/wdio-azure-devops-service/tree/feat/multiTestCaseHandling , but need this package updated first

Hello, @gianlucamangiapelo
Could you please get it merged?
Thanks

@taninnazar do you need the service for yourself? or are you also a maintainer of the package?

@HolKowal I need it for myself. It's very cool enhancement which I really need

Hi @HolKowal thanks for your contribution.
I've translated and merged your intention in that PR #1


Frog Coin Shop Item Entry

I have no idea if it's possible, but it would be nice if there was a repeatable shop entry for a Frog Coin so that you could turn extra Coins into Frog Coins quickly if you happened to have an excess.
I don't know if there's an exploit this might open up, but considering Frog Coins are farmable already, I can't imagine it would be too much of an issue. There is the Land's End fortune that makes this potentially quite easy to cheese, but surely that could be randomized / "fixed" with an option as well.
This idea comes about because I was having a hard time in a run and the last thing I saw that might help me out was an item in tadpole pond for an expensive 60 Frog Coins.
As far as I know the koopa jumping minigame used to farm Frog Coins isn't there (or I just don't know how to activate it) so it would have been nice to be able to turn my 2105 or so coins at the time into a bunch of Frog Coins to at least get me closer to that item.

The Troopa Climb is absolutely there, and is the fastest method to farm frog coins.  There are no plans to introduce alternate methods of farming frog coins.


Issue in IOS

Invariant Violation: Native module cannot be null.[Mon Jul 05 2021 21:07:01.759]  ERROR    Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)[Mon Jul 05 2021 21:07:02.849]  ERROR    Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
Getting this error while  running on IOS

@YsnKsy Would you be willing to look into this?
@darshanksexathought the following (ugly) workaround works for me:
Instead of:
import { AppState, Platform } from 'react-native';
[..All other imports..]
import LocationEnabler from "react-native-location-enabler";

do:
import { AppState, Platform } from 'react-native';
[..All other imports..]
var LocationEnabler = (Platform.OS === 'android') ? require('react-native-location-enabler') : null;

Does not look like author is going to merge my PR. Feel free to use my fork though :)

Thanks a bunch Jurpp! For anyone reading this in the future, you'll also need to add this to your project's Podfile:
pod 'react-native-location-enabler', :path => '../node_modules/react-native-location-enabler/ios'

Thanks a bunch Jurpp! For anyone reading this in the future, you'll also need to add this to your project's Podfile: pod 'react-native-location-enabler', :path => '../node_modules/react-native-location-enabler/ios'

there is no iOS folder in package

Hi @dhairyasenjaliya , I was referring to Jurpp's fork at the time. However it looks like the devs have patched this issue so there's no need for either!

@Jurpp
I used 4.1.1 the same issue happened in iOS so I used your fork
The issue still persists can you please identify what the code changes have to be done for iOS
import LocationEnabler from 'react-native-location-enabler'

const {
    useLocationSettings,
    PRIORITIES: { HIGH_ACCURACY },
  } = LocationEnabler
const [enabled, requestResolution] =  useLocationSettings({
    priority: HIGH_ACCURACY, // optional: default BALANCED_POWER_ACCURACY
    alwaysShow: true, // optional: default false
    needBle: true, // optional: default false
})

still happening

figured out!
after use this var LocationEnabler = (Platform.OS === 'android') ? require('react-native-location-enabler') : null; I got HIGH_ACCURACY has undefined value, so there is default object to destruct the properties, see the code as follow:
const {     PRIORITIES: { HIGH_ACCURACY },     useLocationSettings,   } = LocationEnabler.default;

@YsnKsy Would you be willing to look into this? @darshanksexathought the following (ugly) workaround works for me: Instead of:
import { AppState, Platform } from 'react-native';
[..All other imports..]
import LocationEnabler from "react-native-location-enabler";

do:
import { AppState, Platform } from 'react-native';
[..All other imports..]
var LocationEnabler = (Platform.OS === 'android') ? require('react-native-location-enabler') : null;

Update: This workaround doesn't behave as expected either.
Update2: This seemed like a fun way to learn some more React Native so I started implementing this myself: https://github.com/Jurpp/react-native-location-enabler I will submit a PR when its finished.

figured out!
after use this solution
var LocationEnabler = (Platform.OS === 'android') ? require('react-native-location-enabler') : null;
I got HIGH_ACCURACY has undefined value on Android, so I console.log() the value,
there is default object to destruct the properties, see the code as follow:
const {
    PRIORITIES: { HIGH_ACCURACY },
    useLocationSettings,
  } = LocationEnabler.default;

@YsnKsy Would you be willing to look into this? @darshanksexathought the following (ugly) workaround works for me: Instead of:
import { AppState, Platform } from 'react-native';
[..All other imports..]
import LocationEnabler from "react-native-location-enabler";

do:
import { AppState, Platform } from 'react-native';
[..All other imports..]
var LocationEnabler = (Platform.OS === 'android') ? require('react-native-location-enabler') : null;

Update: This workaround doesn't behave as expected either.
Update2: This seemed like a fun way to learn some more React Native so I started implementing this myself: https://github.com/Jurpp/react-native-location-enabler I will submit a PR when its finished.


extremetuxracer: use up-to-date libpng

Description of changes
Seems to build and run fine with the current version of libpng, the override has been removed.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

Sorry, didn't see this already existed when merging #270174.

No problem, I did not see that #259879 existed


Replacing 'resumeApp' name to 'posts'

Changing the 'resumeApp' app name to 'posts' in order to match Django's app naming convention.
Adding some profile pics and resumes for default users
fix #24

Please squash your commits

done 👍


[BUG] Import xlsx with macros

🐛 Bug Report
I'm having trouble trying to import an .xlsx file with macros. I am working on a general import and when trying to import a spreadsheet with macro, simply the library then in an infinite loop.
Lib version: ^4.2.0
Steps To Reproduce

Import a spreadsheet containing macros
Use a load function as below

return new Promise((resolve, reject) => workbook.xlsx.load(file)
        .then(readFile => {
        ...
}

The expected behaviour:

With what release was this issue resolved? @Siemienik

It's not fixed yet. I closed all inactive issues to make cleaner point of view over issues.

Join our Discord: https://discord.gg/siema

I just discovered this issue today.  My code:
const workbook = new Workbook();
const buffer = this.getBuffer(body); // body is S3 bucket object body, returns Buffer
await workbook.xlsx.load(buffer);

I don't know what it is about the workbook that I'm trying to load that might be causing the infinite loop. The workbook doesn't have any macros.  It has three worksheets and some formulas, but nothing too crazy.

I dug into what was causing the failure of our file and found some valuable info.
Background
We are running a document processor in AWS Lambda by pulling the file data from S3 and parsing xlsx files with ExcelJS.
const workbook = new Workbook();
const buffer = this.getBuffer(body); // body is S3 bucket object body, returns Buffer
await workbook.xlsx.load(buffer);

We had no issue loading some xlsx files but then would fail to load others.  Failure in our context meant either hitting our Lambda execution time or memory limits (even at a memory limit of 10,240MB!).
Discovery
I found that our particular file was failing when we were parsing the dataValidations for one of the worksheets of the file we uploaded, particularly when a data validation was being applied to each address in range:
// exceljs/lib/xlsx/xform/sheet/data-validations-xform.js line: 217
// ... on closing name = 'dataValidation'
  parseClose(name) {
    switch (name) {
      case 'dataValidations':
        return false;
      case 'dataValidation': {
        if (!this._dataValidation.formulae || !this._dataValidation.formulae.length) {
          delete this._dataValidation.formulae;
          delete this._dataValidation.operator;
        }
        // The four known cases: 1. E4:L9 N4:U9  2.E4 L9  3. N4:U9  4. E4
        const list = this._address.split(/\s+/g) || [];
        list.forEach(addr => {
          if (addr.includes(':')) {
            const range = new Range(addr);
            range.forEachAddress(address => {
              this.model[address] = this._dataValidation;
            });
          } else {
            this.model[addr] = this._dataValidation;
          }
        });
        return true;
      }
      // ...
  }

Addresses for us when we were failing were (console.log('this._address', this._address);):
this._address O145:R176 V512 O539:U539 T449:U450 S437:V439 T448:V448 O299:R299 S451:V451 O500:V500 V393 S540:U564 O392:R392 S430:V430 V427 O532:R532 O1:U48 S565:V568 O452:U499 V527:V564 T431:U433 O394:R429 V597 O597:R597 O440:S450 T440:U447 T434:V434 T435:U436 O275:R297 O302:R302 O307:R307 O311:R312 O314:R316 O318:R318 O323:R324 O327:R328 O330:R332 O337:R338 O340:R341 O344:R344 O349:R349 O351:R351 O364:R364 O373:R374 O379:R379 O385:R385 O389:R389 O431:S436 S527:U538 O584:V584 O501:U526 O562:R568 S566:U583 V1:V274 O659:R669 V736:V737 O719:R719 O736:R739 T672:V672 T730:V730 T673:U729 O824:R828 O828:U828 T829:V829 R869:R875 O911:Q911 O923:Q926 S844:U875 T830:U843 O600:R611 V600:V604 S49:U429 O355:R356 T603:U671 S603:S843 O965:Q965 O996:Q999 O921:Q921 O989:Q990 O971:Q972 O956:Q957 T965:V965 V971 T966:U988 T989:V989 T990:U995 T996:V996 T999:V999 T997:U998 T1015:V1015 O1006:Q1007 O1009:Q1009 O1011:Q1012 V1007 T1000:U1008 T1009:V1009 T1010:U1010 T1011:V1012 T1013:U1014 T876:U964 O1015:Q1015 O1018:Q1018 T1016:U1017 T1018:V1018 O1037:Q1037 O1056:Q1057 T1037:V1037 T1019:U1036 O1072:Q1073 O1076:Q1076 T1078:V1078 T1079:U1080 T1081:V1081 T1082:U1082 T1083:V1083 T1084:U1084 T1085:V1085 T1086:U1097 T1098:V1098 T1099:U1106 R1107:U1112 T1130:V1130 T1113:U1129 R1113:S1133 T1131:U1134 S1134 T731:U828 O1206:Q1206 O1208:Q1208 O1210:Q1212 O1214:Q1215 S1250:U1267 T1247:V1247 O1247:S1249 T1248:U1249 O1218:Q1225 AJ1320:AJ1048576 O1299:Q1299 O1279:U1280 O1250:R1280 O1191:Q1204 V1255:V1264 R1250:S1264 O1098:Q1127 O1130:Q1134 S585:U602 O678:V678 T1345:V1346 R1278:U1318 R1320:U1337 R1338:S1350 T1338:U1344 T1347:U1350 R1135:U1246 O1350:U1350 O1379:Q1379 O1392:U1392 O1422:V1422 O1393:V1395 R1351:U1391 U1056 R876:S1106 T1038:U1055 T1057:U1077 O1396:Q1427 S1268:V1277 O1433:Q1435 T1435:U1435 T1433:V1434 R1396:S1435 T1396:U1432 S1437:V1438 S1436:U1436 O1348:V1349 S1439:U1048576 AJ1:AJ1318 Q1436:R1048576 O1436:P1446 O1458:P1048576

What stood out to me were a few ranges like Q1436:R1048576 and O1458:P1048576, where each cell in the range is assigned the dataValidation via a Javascript object map.  With so many cells in these ranges, our function memory (and runtime) get blown through the roof.
Once I cleared out all of the data validation on the worksheet, we were able to parse the file without issue.
Discussion
It seems to me that ranges like these are created in Excel when entire columns are set to have particular data validation, and then later on, row inserts, copy/pastes, or fills override the data validation for a subset of the cells in those columns, forcing Excel to break the once contiguous range of A:A for example into separate A1:A10 and A12:A[infinity] ranges, except Excel uses 10^20 (1048576) instead of "infinity."  Because Excel instead saves the separate ranges that are so large, it causes ExcelJS to go nuclear with memory usage when loading the file in situations where it is creating a Javascript object map entry for each cell.
I don't have a solution to this problem.  My only thoughts are perhaps to recognize when a range is going to "infinity" in situations where you might try to allocate memory for all cells in the range and to have the option to prevent that from happening.  Ideally, ExcelJS might be able to figure out where the last row/column contains "real" information and be able to stop "infinite ranges" from going beyond that row or column or some offset from that row or column.  I'm open to discussion.
NOTE: I don't know if this is the same problem the OP is dealing with.  I can move this post if you think it belongs elsewhere.


Flutter/Firebase

My project where work perfectly, but when I add the Firebase and start work on it the I could not open it agin in the simulator
the output which I resive
Launching lib/main.dart on iPhone 11 Pro in debug mode...
Running Xcode build...
Xcode build done.                                           19.6s
Configuring the default Firebase app...
Connecting to the VM Service is taking longer than expected...
Still attempting to connect to the VM Service...
If you do NOT see the Flutter application running, it might have crashed. The device logs (e.g. from adb or XCode) might have more details.
If you do see the Flutter application running on the device, try re-running with --host-vmservice-port to use a specific port known to be available.
Exception attempting to connect to the VM Service: SocketException: OS Error: Connection refused, errno = 61, address = <IP_ADDRESS>, port = 60093
This was attempt #50. Will retry in 0:00:01.600000.
Exception attempting to connect to the VM Service: SocketException: OS Error: Connection refused, errno = 61, address = <IP_ADDRESS>, port = 60230
This was attempt #100. Will retry in 0:00:01.600000.
my flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.20.0-1.0.pre.157, on Mac OS X 10.15.5 19F101,
locale en-SA)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)
• No issues found!
MBPalkhasbSara:~ saraalrabiah$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.20.0-1.0.pre.157, on Mac OS X 10.15.5 19F101,
locale en-SA)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)
• No issues found!

Same problem here...
... and no issues found on flutter doctor!

@Saraalr
Make sure you are adding GoogleService-Info.plist through XCode too. You cannot simply copy this into the ios/Runner directory.

Place the GoogleService-Info.plist on ios/Runner folder.
Add the file through XCode (right click on Runner and then Add Files...).

@liveplugin
I add it and new error occur
Error massage :
Launching lib/main.dart on iPhone SE (2nd generation) in debug mode...
Running Xcode build...
Xcode build done.                                           13.9s
Failed to build iOS app
Could not build the application for the simulator.
Error launching application on iPhone SE (2nd generation).
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
/Users/PC/Desktop/flutter/.pub-cache/hosted/pub.dartlang.org/cloud_firestore-0.12.11/ios/Classes/CloudFirestorePlugin.m:764:16: warning: 'timestampsInSnapshotsEnabled' is deprecated [-Wdeprecated-declarations]
settings.timestampsInSnapshotsEnabled = (bool)call.arguments[@"timestampsInSnapshotsEnabled"];
^
In module 'FirebaseFirestore' imported from /Users/PC/Desktop/aproject/ios/Pods/Headers/Public/Firebase/Firebase.h:49:
/Users/PC/Desktop/aproject/ios/Pods/FirebaseFirestore/Firestore/Source/Public/FIRFirestoreSettings.h:69:20: note: 'timestampsInSnapshotsEnabled' has been explicitly marked deprecated here
attribute((deprecated));
^
1 warning generated.
error: Build input file cannot be found: '/Users/saraalrabiah/Downloads/GoogleService-Info-4.plist' (in target 'Runner' from project 'Runner')
gRPC-C++-dwownretmfyzotdyvoofqfkgmjun
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
finally, I think the problem related to firebase because I test my project before it and it is work, but I don't  know exactly  what is it.

@Saraalr
error: Build input file cannot be found: '/Users/saraalrabiah/Downloads/GoogleService-Info-4.plist' (in target 'Runner' from project 'Runner')
You import the plistfile directly from Downloads folder...
Place the file on your ios/Runner folder and import through XCode.

@liveplugin you mean i have to open ios in xcode then place it under runner?

@Saraalr
Yes.

Open ios folder on XCode.
Right click on Runner and then Add Files...

@liveplugin
I have done the following steps but in Xcode I face this :

and in android studio :
Launching lib/main.dart on iPhone SE (2nd generation) in debug mode...
Running pod install...
Running Xcode build...
Xcode build done.                                           11.7s
Failed to build iOS app
Could not build the application for the simulator.
Error launching application on iPhone SE (2nd generation).
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
/Users/PC/Desktop/aproject/build/ios/Debug-iphonesimulator/nanopb/nanopb.framework: resource fork, Finder information, or similar detritus not allowed
Command CodeSign failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
also in  android studio I can't see the plist file is it okay? I mean it doesn't appear under iOS/runner

@Saraalr

it is still not running with this error :
Launching lib/main.dart on iPhone SE (2nd generation) in debug mode...
Running pod install...
Running Xcode build...
Xcode build done.                                           12.5s
Failed to build iOS app
Could not build the application for the simulator.
Error launching application on iPhone SE (2nd generation).
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
/Users/PC/Desktop/aproject/build/ios/Debug-iphonesimulator/nanopb/nanopb.framework: resource fork, Finder information, or similar detritus not allowed
Command CodeSign failed with a nonzero exit code
/Users/PC/Desktop/aproject/build/ios/Debug-iphonesimulator/gRPC-C++/gRPCCertificates-Cpp.bundle: replacing existing signature
/Users/PC/Desktop/aproject/build/ios/Debug-iphonesimulator/gRPC-C++/gRPCCertificates-Cpp.bundle: resource fork, Finder information, or similar detritus not allowed
Command CodeSign failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description

@liveplugin

@Saraalr
Perhaps, now, the problem is the outdated simulator you are using (Phone SE)...
Try another more updated.

@liveplugin
android studio error
/Users/PC/Desktop/aproject/build/ios/Debug-iphonesimulator/nanopb/nanopb.framework: resource fork, Finder information, or similar detritus not allowed
Command CodeSign failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
and this is Xcode error :
2020-06-26 08:59:11.415553+0300 Runner[22597:159953] Configuring the default Firebase app...
2020-06-26 08:59:11.442836+0300 Runner[22597:160561] 6.27.0 - [Firebase/Core][I-COR000004] App with name __FIRAPP_DEFAULT does not exist.
2020-06-26 08:59:11.443059+0300 Runner[22597:160561] 6.27.0 - [Firebase/Core][I-COR000012] Could not locate configuration file: 'GoogleService-Info.plist'.
2020-06-26 08:59:11.451800+0300 Runner[22597:160625] flutter: Observatory listening on http://<IP_ADDRESS>:52548/7Q61n4uqGuE=/
2020-06-26 08:59:11.480883+0300 Runner[22597:159953] *** Terminating app due to uncaught exception 'com.firebase.core', reason: '[FIRApp configure]; (FirebaseApp.configure() in Swift) could not find a valid GoogleService-Info.plist in your project. Please download one from https://console.firebase.google.com/.'
*** First throw call stack:
(
0   CoreFoundation                      0x00007fff23e3cf0e __exceptionPreprocess + 350
1   libobjc.A.dylib                     0x00007fff50ba89b2 objc_exception_throw + 48
2   CoreFoundation                      0x00007fff23e3cd4c +[NSException raise:format:] + 188
3   Runner                              0x00000001037898b2 +[FIRApp configure] + 130
4   Runner                              0x0000000103cdff59 -[FLTCloudFirestorePlugin init] + 217
5   Runner                              0x0000000103cdfd66 +[FLTCloudFirestorePlugin registerWithRegistrar:] + 262
6   Runner                              0x0000000103724fc3 +[GeneratedPluginRegistrant registerWithRegistry:] + 115
7   Runner                              0x0000000103725150 $s6Runner11AppDelegateC11application_29didFinishLaunchingWithOptionsSbSo13UIApplicationC_SDySo0j6LaunchI3KeyaypGSgtF + 176
8   Runner                              0x0000000103725483 $s6Runner11AppDelegateC11application_29didFinishLaunchingWithOptionsSbSo13UIApplicationC_SDySo0j6LaunchI3KeyaypGSgtFTo + 211
9   UIKitCore                           0x00007fff48c82698 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 232
10  UIKitCore                           0x00007fff48c84037 -[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:] + 3985
11  UIKitCore                           0x00007fff48c89bf9 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1226
12  UIKitCore                           0x00007fff4839225d -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 122
13  UIKitCore                           0x00007fff4889dcc1 _UIScenePerformActionsWithLifecycleActionMask + 83
14  UIKitCore                           0x00007fff48392d6f __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke + 198
15  UIKitCore                           0x00007fff4839277e -[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:] + 296
16  UIKitCore                           0x00007fff48392b9c -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:] + 818
17  UIKitCore                           0x00007fff48392431 -[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:] + 345
18  UIKitCore                           0x00007fff48396a22 __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke_2 + 178
19  UIKitCore                           0x00007fff487b3dad +[BSAnimationSettings(UIKit) tryAnimatingWithSettings:actions:completion:] + 852
20  UIKitCore                           0x00007fff488bc41e _UISceneSettingsDiffActionPerformChangesWithTransitionContext + 240
21  UIKitCore                           0x00007fff4839673d __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke + 153
22  UIKitCore                           0x00007fff488bc321 _UISceneSettingsDiffActionPerformActionsWithDelayForTransitionContext + 84
23  UIKitCore                           0x00007fff483965ab -[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:] + 381
24  UIKitCore                           0x00007fff481eafa8 __64-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]_block_invoke + 657
25  UIKitCore                           0x00007fff481e9b67 -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 253
26  UIKitCore                           0x00007fff481eacd2 -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 210
27  UIKitCore                           0x00007fff48c88141 -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 512
28  UIKitCore                           0x00007fff487da8dc -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 361
29  FrontBoardServices                  0x00007fff36cacd2e -[FBSSceneImpl _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 419
30  FrontBoardServices                  0x00007fff36cd2dc1 __86-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]_block_invoke.154 + 102
31  FrontBoardServices                  0x00007fff36cb7757 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 220
32  FrontBoardServices                  0x00007fff36cd2a52 __86-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]_block_invoke + 355
33  libdispatch.dylib                   0x00000001095ece8e _dispatch_client_callout + 8
34  libdispatch.dylib                   0x00000001095efda2 _dispatch_block_invoke_direct + 300
35  FrontBoardServices                  0x00007fff36cf86e9 FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK + 30
36  FrontBoardServices                  0x00007fff36cf83d7 -[FBSSerialQueue _queue_performNextIfPossible] + 441
37  FrontBoardServices                  0x00007fff36cf88e6 -[FBSSerialQueue _performNextFromRunLoopSource] + 22
38  CoreFoundation                      0x00007fff23da0d31 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
39  CoreFoundation                      0x00007fff23da0c5c __CFRunLoopDoSource0 + 76
40  CoreFoundation                      0x00007fff23da0434 __CFRunLoopDoSources0 + 180
41  CoreFoundation                      0x00007fff23d9b02e __CFRunLoopRun + 974
42  CoreFoundation                      0x00007fff23d9a944 CFRunLoopRunSpecific + 404
43  GraphicsServices                    0x00007fff38ba6c1a GSEventRunModal + 139
44  UIKitCore                           0x00007fff48c8b9ec UIApplicationMain + 1605
45  Runner                              0x000000010372562b main + 75
46  libdyld.dylib                       0x00007fff51a231fd start + 1
47  ???                                 0x0000000000000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
(lldb)
it says that I didn't download plist but I did it following your steps

@Saraalr
Well, in this error I don't know how to help.
I suggest you continue researching until you can get around this problem.
Good luck!

@Saraalr
I can notice you don't have Firebase in your AppDelegate.swift
Please add this
import UIKit
import Flutter
import Firebase

@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
  override func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
  ) -> Bool {
    FirebaseApp.configure()
    GeneratedPluginRegistrant.register(with: self)
    return super.application(application, didFinishLaunchingWithOptions: launchOptions)
  }
}

flutter doctor -v
[✓] Flutter (Channel dev, 1.20.0-1.0.pre, on Mac OS X 10.15.5 19F101, locale
    en-GB)
    • Flutter version 1.20.0-1.0.pre at /Users/tahatesser/Code/flutter_dev
    • Framework revision f73f498da1 (8 days ago), 2020-06-18 08:23:22 -0700
    • Engine revision c0d52b98d1
    • Dart version 2.9.0 (build 2.9.0-16.0.dev 2b917f5b6a)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.46.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.11.0

[✓] Connected device (6 available)
    • SM M305F      • 32003c30dc19668f                     • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPhone • 00008020-001059882212002E            • ios            •
      iOS 13.5.1
    • iPhone 11     • 0EC80516-8F99-4A0C-89ED-2273579862F9 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
    • macOS         • macOS                                • darwin-x64     •
      Mac OS X 10.15.5 19F101
    • Web Server    • web-server                           • web-javascript •
      Flutter Tools
    • Chrome        • chrome                               • web-javascript •
      Google Chrome 83.0.4103.116

• No issues found!

If the problem persist after adding this,
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you

@TahaTesser
I can't import firebase, it gives me this error -could not build Opjective-C modulo " Firebase"-

@TahaTesser
this is occurs in Xcode :
2020-06-26 18:27:17.987427+0300 Runner[12496:114464] flutter: Observatory listening on http://<IP_ADDRESS>:52939/mxWUloO6HVI=/
2020-06-26 18:27:18.030714+0300 Runner[12496:114422] 6.27.0 - [Firebase/Analytics][I-ACS031025] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2020-06-26 18:27:18.030872+0300 Runner[12496:114422] 6.27.0 - [Firebase/Analytics][I-ACS023007] Analytics v.60601000 started
2020-06-26 18:27:18.031027+0300 Runner[12496:114422] 6.27.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2020-06-26 18:27:18.235238+0300 Runner[12496:114425] 6.27.0 - [Firebase/Analytics][I-ACS800023] No pending snapshot to activate. SDK name: app_measurement
2020-06-26 18:27:18.422243+0300 Runner[12496:114447] flutter: ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
2020-06-26 18:27:18.422422+0300 Runner[12496:114447] flutter: The following ProviderNotFoundError was thrown building Wapper(dirty):
2020-06-26 18:27:18.422568+0300 Runner[12496:114447] flutter: Error: Could not find the correct Provider above this Wapper Widget
2020-06-26 18:27:18.422706+0300 Runner[12496:114447] flutter:
2020-06-26 18:27:18.422836+0300 Runner[12496:114447] flutter: To fix, please:
2020-06-26 18:27:18.422958+0300 Runner[12496:114447] flutter:
2020-06-26 18:27:18.423082+0300 Runner[12496:114447] flutter:   * Ensure the Provider is an ancestor to this Wapper Widget
2020-06-26 18:27:18.423207+0300 Runner[12496:114447] flutter:   * Provide types to Provider
2020-06-26 18:27:18.423326+0300 Runner[12496:114447] flutter:   * Provide types to Consumer
2020-06-26 18:27:18.423455+0300 Runner[12496:114447] flutter:   * Provide types to Provider.of()
2020-06-26 18:27:18.423586+0300 Runner[12496:114447] flutter:   * Always use package imports. Ex: import 'package:my_app/my_code.dart'; 2020-06-26 18:27:18.423739+0300 Runner[12496:114447] flutter:   * Ensure the correct context` is being used.
2020-06-26 18:27:18.423860+0300 Runner[12496:114447] flutter:
2020-06-26 18:27:18.425281+0300 Runner[12496:114447] flutter: If none of these solutions work, please file a bug at:
2020-06-26 18:27:18.425458+0300 Runner[12496:114447] flutter: https://github.com/rrousselGit/provider/issues
2020-06-26 18:27:18.425618+0300 Runner[12496:114447] flutter:
2020-06-26 18:27:18.425743+0300 Runner[12496:114447] flutter: The relevant error-causing widget was:
2020-06-26 18:27:18.425877+0300 Runner[12496:114447] flutter:   Wapper file:///Users/saraalrabiah/Desktop/aproject/lib/main.dart:17:12
2020-06-26 18:27:18.426010+0300 Runner[12496:114447] flutter:
2020-06-26 18:27:18.426141+0300 Runner[12496:114447] flutter: When the exception was thrown, this was the stack:
2020-06-26 18:27:18.426261+0300 Runner[12496:114447] flutter: #0      Provider.of (package:provider/src/provider.dart:264:7)
2020-06-26 18:27:18.426404+0300 Runner[12496:114447] flutter: #1      Wapper.build (package:aproject/general/home.dart:13:27)
2020-06-26 18:27:18.426524+0300 Runner[12496:114447] flutter: #2      StatelessElement.build (package:flutter/src/widgets/framework.dart:4620:28)
2020-06-26 18:27:18.426669+0300 Runner[12496:114447] flutter: #3      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4546:15)
2020-06-26 18:27:18.426778+0300 Runner[12496:114447] flutter: #4      Element.rebuild (package:flutter/src/widgets/framework.dart:4262:5)
2020-06-26 18:27:18.426915+0300 Runner[12496:114447] flutter: #5      ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4525:5)
2020-06-26 18:27:18.427039+0300 Runner[12496:114447] flutter: #6      ComponentElement.mount (package:flutter/src/widgets/framework.dart:4520:5)
2020-06-26 18:27:18.427189+0300 Runner[12496:114447] flutter: ...     Normal element mounting (7 frames)
2020-06-26 18:27:18.427336+0300 Runner[12496:114447] flutter: #13     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3490:14)
2020-06-26 18:27:18.427450+0300 Runner[12496:114447] flutter: #14     Element.updateChild (package:flutter/src/widgets/framework.dart:3258:18)
2020-06-26 18:27:18.427568+0300 Runner[12496:114447] flutter: #15     RenderObjectToWidgetElement._rebuild (package:flutter/src/widgets/binding.dart:1134:16)
2020-06-26 18:27:18.427687+0300 Runner[12496:114447] flutter: #16     RenderObjectToWidgetElement.mount (package:flutter/src/widgets/binding.dart:1105:5)
2020-06-26 18:27:18.427824+0300 Runner[12496:114447] flutter: #17     RenderObjectToWidgetAdapter.attachToRenderTree. (package:flutter/src/widgets/binding.dart:1047:17)
2020-06-26 18:27:18.427954+0300 Runner[12496:114447] flutter: #18     BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2620:19)
2020-06-26 18:27:18.428145+0300 Runner[12496:114447] flutter: #19     RenderObjectToWidgetAdapter.attachToRenderTree (package:flutter/src/widgets/binding.dart:1046:13)
2020-06-26 18:27:18.428371+0300 Runner[12496:114447] flutter: #20     WidgetsBinding.attachRootWidget (package:flutter/src/widgets/binding.dart:927:7)
2020-06-26 18:27:18.428578+0300 Runner[12496:114447] flutter: #21     WidgetsBinding.scheduleAttachRootWidget. (package:flutter/src/widgets/binding.dart:908:7)
2020-06-26 18:27:18.428742+0300 Runner[12496:114447] flutter: (elided 11 frames from class _RawReceivePortImpl, class _Timer, dart:async, and dart:async-patch)
2020-06-26 18:27:18.428938+0300 Runner[12496:114447] flutter:
2020-06-26 18:27:18.429102+0300 Runner[12496:114447] flutter: ════════════════════════════════════════════════════════════════════════════════════════════════════
2020-06-26 18:27:18.480024+0300 Runner[12496:114473] 6.27.0 - [Firebase/Analytics][I-ACS023012] Analytics collection enabled
and in the simulator:

and in android studio it is remain the same error .

@Saraalr
Error in the screenshot and logs are not related flutterfire, it's an issue with your code for provider
This platform is not meant for assistance on personal code. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with flutterfire itself. If you disagree, please write in the comments and I will reopen it.
Thank you


include is_control in satellite v1 measurements

add is_control_ip field in satellite v1 and v2, determined by which file the measurement comes from. This is answers_control.json in v1 and responses_control.json in v2.1.
What is the right way to determine this for v2.2?
Also fill out the is_control field for all satellite measurements. Depending on whether the domain is a control.
This only happens in v2. And the only control I'm checking is a.root-servers.net. Are there other control domains I'm missing here?
We should probably change the name of is_control to is_control_domain, but that affects the hyperquack pipeline, so I'm leaving it out here.
Also refactor partition_satellite_input to enumerate all possible filename matches instead of matching on partial strings.

Substantially changed this and updated the description.

Also possibly we should name this field is_control_ip instead of is_ip_control, and then in the future use the name is_control_domain?

We've used the same 5 control resolvers for all versions of Satellite, so hardcoding them is probably the best solution for v2.2.

I know one is <IP_ADDRESS>, but what are the the other 4?

We've used the same 5 control resolvers for all versions of Satellite, so hardcoding them is probably the best solution for v2.2.

I know one is <IP_ADDRESS>, but what are the the other 4?

<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>

We've used the same 5 control resolvers for all versions of Satellite, so hardcoding them is probably the best solution for v2.2.

I know one is <IP_ADDRESS>, but what are the the other 4?

<IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>

Great. Added an is_control_ip test against these 5.


Keybind info needs added to page description

I updated to the latest version in 1.20.4 when I saw you added the alternative pvp logic, (thanks again for that!) and when setting it up I was having trouble remembering what the keybind for toggling pvp on and off was, couldn't get anything to work and resorted to digging through the source code to find the keybind since you don't list it on the mod description page.
It turned out I installed it on the server but not the client which is why it wasn't working, but still might be a good idea to note the keybind in the mod description.

Yeah, sorry! I'll add it shortly!


WIP remove unused compilation result sub classes

ref #7

Coverage increased (+1.3%) to 77.504% when pulling 08c5e4e1bbe216c82f3a00692738b12d06d41236 on feature/javac_api into eceb8c3a43f594d85c9edccf70a998d0a2e06317 on master.


PD Toolkit

http://github.com/shamansir/rpd-puredata

Now, it turned out to be meta issue for #222 and #223

and #271


Cannot read directory "../../../../../../..": Access is denied.

Describe the bug
Hi All, im getting weird issue. Not able to run the application getting below error.

Node - 20.15.1
npm - 10.8.2
Reproduction
npm create vite@latest
Steps to reproduce
No response
System Info
Windows 10

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Not able to reproduce it in StackBlitz :(


Question around how to use persp-kill

  ;; Need to skip doing anything if last perspective and last window.
  ;; And also get persp-kill to kill the current perspective instead of forcing interaction.
  (defun delete-perspective-or-window()
    "Delete perspective if last window left but delete window if more than one."
    (interactive)
    (if (eq (count-windows) 1)
        (persp-kill nil) ;; (persp-kill persp-curr)
      (delete-window)))

I'm trying to write a wrapper method to selectively call persp-kill or delete-window depending on the window count. (persp-kill nil) works but brings up interaction. I'd prefer (persp-kill) to automatically end kill the perspective.
Also wondering if perspective is exposing another variable to check the number of perspectives currently up.
Thanks!

persp-kill will only bring up an interactive prompt if you don't pass an explicit name.

Also wondering if perspective is exposing another variable to check the number of perspectives currently up.

You can inspect the perspectives-hash variable to see the total number of perspectives in the current frame.

Thanks.


Microsoft Edge label is using MAU

MAU has been deprecated for Microsoft Edge for a while, but the label is still using the updateTool.
Edge is using the EdgeUpdater tool now, and I don't think it can be run manually using scripts.
https://learn.microsoft.com/en-us/deployedge/edge-learnmore-edgeupdater-for-macos

Believe fixed in Installomator 10.6


Need list_port() + show_port()

Currently, we have list_{projects/nodes,...}. To help the admin, we also need list_port and show_port.
We should also include the port in show_node.
All of this should only be available for admins, since regular users don't manage ports.

Since I am working on #567 and show_port() is already implemented by @kylehogan . I will take list_port() as well.

Addressed by #767


Drop Sphinx compatibility to < 5

Sphinx 5.0 is dropping jQuery support, which we have historically piggybacked off of. Removing jQuery support here (and in RTD) is totally valid and a good goal as well, we're not doing anything with jQuery that we couldn't do by hand. But to start, we should squeak out a release that pins our Sphinx < 5 so we don't risk a theme version that doesn't have jQuery underneath.
We can discuss a few options for removing jQuery, including porting code and async loading of jQuery when it doesn't exist through webpack (we use this feature in our new site templates).

But to start, we should squeak out a release that pins our Sphinx < 5 so we don't risk a theme version that doesn't have jQuery underneath.

Indeed!

As Sphinx 5.0 is released, do I read this correct that currently rtd_theme is not compatible with it?


Allow setting the exposed port to use

We are running on port 9200. We should make that a setting and set the default value to it.

Now that the project moved to testcontainers as a module, I'm not planning to add more commits as the project will be living here now: https://github.com/testcontainers/testcontainers-java/tree/master/modules/elasticsearch.


Make it a taskwarrior & timewarrior web client!

I've recently discovered that taskwarrior cli is fantastic and it a big community that standardized todo/task tracking on  OS level. I'm currently learning timewarrior , it is not as intuitive to use however all the foundations/standardization is now there for operating systems.
This could be a great web client for taskwarrior and timewarrior ;)

Hi @izelnakri! Thank you for suggestion! Really neat tools! I think it's possible to at least add support for timewarrior data import.
To clarify scope of this app - it's kinda pet-projects to battle-test https://github.com/lifeart/glimmer-next and spot real-usage problems.
Here is a list of apps I made: https://github.com/lifeart/template-gxt/issues/1


Change banstick config to direct people to /r/CivMC's modmail instead of /r/Devoted's

Oh thanks, so many little things like this


Release more recent version

hello,
I experienced a bug with mux only to find that it was fixed already in the iron branch. The released version is quite old:
root@logi-XMG-CORE-REN-M20:/code# apt install ros-iron-topic-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ros-iron-topic-tools is already the newest version (1.0.0-3jammy.20230908.173839).

The 1.0.0 tag is from March 2022.
Can you please release a more recent tag? Thanks

There is a 1.1.0 tag for Iron and Rolling https://github.com/ros-tooling/topic_tools/commit/66b7d126aaa6cdd87860744a3459f6a28292b4a0, but it was indeed not released in any distro. I cannot do the release myself since I don't have access to the release repo, but @emersonknapp or @MichaelOrlov might be able to do it. This is somewhat related to #62.

Ok. no worries, we will wait for it. Meanwhile we will clone the iron branch.
However, it would be nice to have the release soon, since we didn't modify any feature of the package when we are just using it for our application. So it doesn't make much sense to clone the whole branch to use features of the package.
Thanks for the insight anyways, we will wait for the release.

@christophebedard before doing a new relases for iron and humble it would be great to backport the new commits from main branch

https://github.com/ros-tooling/topic_tools/pull/75
https://github.com/ros-tooling/topic_tools/pull/77
https://github.com/ros-tooling/topic_tools/pull/78
https://github.com/ros-tooling/topic_tools/pull/82

Perhaps we can do it with help from mergify bot.

@christophebedard FYI, I've made backports with the help from the mergify bot.

Here are the rosdistro PRs for the new releases:

Humble: https://github.com/ros/rosdistro/pull/39101
Iron: https://github.com/ros/rosdistro/pull/39102
Rolling: https://github.com/ros/rosdistro/pull/39103

The rosdistro PRs have been merged. We just have to wait for availability in the testing repo and then in the normal repo after the next sync, so I'll close this.


COLLATE ci on embedded collection

I'm using v2.1, I tried to set COLLATE ci on the EMBEDDEDLIST string property.
It was a mistake thought, its behavior was quite wired, look at this:
create class test extends V
// assume that the cluster is #12
create property test.categories EMBEDDEDLIST string
create vertex test set categories=['a','b'] // #12:0

select from test where 'a' in categories
// [OK] record #12:0 found

alter property test.categories COLLATE ci  // <-- mistake, but it applied without error
create vertex test set categories=['Math','English']  // #12:1
create vertex test set categories=['a','b','c']  // #12:2

select from test where 'a' in categories
// [OK] record #12:0, #12:2 found

select from test where 'Math' in categories
// [NOT OK] no records. expected #12:1.

alter property test.categories COLLATE null  // <-- remove the cause of problem.
select from test where 'Math' in categories
// [OK] record #12:1 found as expected

It seems that to set COLLATE ci on the EMBEDDEDLIST(or SET), makes IN operator dysfunctional. It looks like a bug which is pretty hard to figure out.

This is still broken in 2.1.5 and is really annoying. Any ETA on when it will be fixed?

Hey guys, I was wondering if this issue can get any love in the newest 2.1.x release by any chance. This is causing lots of :cry: and :disappointed: for my project.

Hi guys, I'm taking a look at it, I'll give you a feedback in short
Thanks
Luigi

Hi guys,
I have a fix for this (that is also an enhancement, because it extends collate strategies to collections).
I'm running all the tests, I'll push the fix as soon as all is green
Thanks
Luigi

Fix pushed on 2.1.x branch, now I'm porting it to 2.2

Ok, fixed, I'm closing this issue, please reopen if you experience any problems
Thanks
Luigi


security requirements of the container-native operators

#https://issues.redhat.com/browse/CNFCERT-882?filter=-1
Recommended security requirements of the container-native operators split to be 4 tests:
testOperatorRunAsUserID(): This test verifies that no pods managed by operators run with the root user ID (UID) of 0, which could introduce security vulnerabilities.It iterates through each operator, we find all pods managed by a specific operator within a given test environment (it iterates through each pod in the environment, checking if its owner references match those of the operator's Cluster Service Version (CSV). If a match is found, the pod is added to the list of found pods). Once we have the list of pods, it loops through each pods and then If a pod's UID is 0, it's marked as non-compliant. otherwise, it's marked as compliant. This test enforces security best practices and prevents the deployment of pods with elevated privileges.
testOperatorRunAsNonRoot(): This test ensures that pods managed by operators adhere to security best practices by running as non-root users. It iterates through each operator, we find all pods managed by a specific operator within a given test environment (it iterates through each pod in the environment, checking if its owner references match those of the operator's Cluster Service Version (CSV). If a match is found, the pod is added to the list of found pods). Once we have the list of pods, checks their user ID. Pods running with non-root user IDs are marked as compliant, while those running as the root user are marked as non-compliant. By avoiding elevated privileges, this test contributes to a more secure deployment environment.
testOperatorAutomountTokens(): This test evaluates the configuration of automount service tokens in pods managed by operators. It iterates through each operator, we find all pods managed by a specific operator within a given test environment (it iterates through each pod in the environment, checking if its owner references match those of the operator's Cluster Service Version (CSV). If a match is found, the pod is added to the list of found pods). Once we have the list of pods, Pods with automount service tokens set to false are marked as compliant, while those with tokens set to true or any evaluation errors are marked as non-compliant. This test ensures secure pod configurations, enhancing the overall security of the deployment environment.
testOperatorReadOnlyFilesystem(): This test verifies whether containers within pods managed by operators have a read-only root filesystem, enhancing security by preventing unauthorized modifications. It iterates through each operator, we find all pods managed by a specific operator within a given test environment (it iterates through each pod in the environment, checking if its owner references match those of the operator's Cluster Service Version (CSV). If a match is found, the pod is added to the list of found pods). Once we have the list of pods, we loop through each container and then container with a read-only root filesystem are marked as compliant, while those with a writable root filesystem are marked as non-compliant. Ensuring read-only root filesystems where appropriate contributes to a more secure deployment environment.
In addition, the 'rbac' folder moved into the 'common' folder because it is used by functions in many places in the code, and we want to avoid duplicating code.

@shimritproj could you add this new test to the CATALOG.md? Thanks

The current PR description is undesirably verbose.
Please change the PR description to something relevant that describes the changes you made in this PR and optionally how.

from change #1967:

SUCCESS https://www.distributed-ci.io/jobs/54276bb8-3f43-4c76-ae9b-108f7d651f53/jobStates

Don't know if it's expected, but the four new tests added in this change are all skipped in this DCI job.

@shimritproj Could you please move the description of the functions as code comments?

from change #1967:

SUCCESS https://www.distributed-ci.io/jobs/54276bb8-3f43-4c76-ae9b-108f7d651f53/jobStates

Don't know if it's expected, but the four new tests added in this change are all skipped in this DCI job. Are they behaving properly?

I am aware of the issue and actively working on it. This is why I indicated that the PR is still a work in progress and not yet ready for review. @ramperher

testOperatorContainersReadOnlyFilesystem(): This test verifies whether containers within pods managed by operators have a read-only root filesystem, enhancing security by preventing unauthorized modifications.

I see last job failed because the condition above made match:
TASK [redhatci.ocp.verify_tests : Fail if not all test results are as expected for cnf-certification-tests_junit.xml]
... 'actual_result': {'testcase': 'operator-read-only-file-system', 'passed': False}}]"}

And from the test details:
{"CompliantObjectsOut":null,"NonCompliantObjectsOut":[{"ObjectType":"Pod","ObjectFieldsKeys":["Reason For Non Compliance","Namespace","Pod Name"],"ObjectFieldsValues":["Pod has been found read not only root file system","test-cnf","mongodb-enterprise-operator-65cfdf-72phr"]}]}

I guess we need to start taking this into account in our pipeline right? Thanks!

@manurodriguez Correct.  We seem to be hitting the same-ish problem with our operator we install as part of our smoke tests where it doesn't pass the tests now.  So it's possible that the mongodb operator used in your tests is also failing for the same reasons.

@manurodriguez Correct. We seem to be hitting the same-ish problem with our operator we install as part of our smoke tests where it doesn't pass the tests now. So it's possible that the mongodb operator used in your tests is also failing for the same reasons.

Thanks for the clarification @sebrandon1, then because we do not control the mongodb operator definitions, I think we can create a PR to ignore the  operator-read-only-file-system test failure in the pipeline and only use it as a dependency to test this PR cnf-certification-test#1967
Once the test operator-read-only-file-system be part of an official TNF release, then we can decide if ignoring the test can be part of the official fix in our pipeline or think of another solution, wdyt?

That's where we're at with the hazelcast operator in the smoke tests.  We don't control the definitions so we will have to just handle it as an expected error.

@shimritproj , if the change is WIP, could you add the dci-disable label to avoid launching DCI jobs? (which are mainly failing right now)

/dci-rerun

@ramperher Does this mean that if we rekick the DCI job the error is handled now as an expected failure?

@ramperher Does this mean that if we rekick the DCI job the error is handled now as an expected failure?

Exactly, we're running an operator that is not under our control, so I assume the tests that were failing before must be considered as exceptions.

/dci-rerun


Add awesome-canvas

Good start, but some things could be improved.
First read: https://github.com/sindresorhus/awesome/blob/master/contributing.md and https://github.com/sindresorhus/awesome/blob/master/awesome.md
MIT is not a good license for this type of content. Creative Commons is a better choice. All the Examples need description. You also say it's "best examples of canvas", description for each item should also say why. The Twitter section is just a list of links without any context. Each item needs arguments for why I would want to follow that person.

Leave it to me! I'll notify when finished :)

@sindresorhus I made the changes. Can you check? :)

Good stuff :)

Would be awesome if you would add the awesome badge: https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge

Badge Added! Thanks :)


Adding new items from HathiTrust broken for some items

There are two separate issues. For some IDs, it is failing to sync data (uc1.b3514895; uc1.b3514895; FYI, other uc1 IDs worked). Others generated 500 error and then appear in database but without record ID and source URL (mdp.39015043572422; mdp.39015060430082; FYI, other mdp IDs worked).
testing notes

[x] test mdp.39015060430082 or others that were resulting in 500 error to see if import works now

dev notes

[x] handle type error on pubdate conversion to integer when it is not set
[ ] investigate rsync error

pub date conversion error stack trace from logs in qa on attempted import of mdp.39015060430082:
    field_data["pub_date"] = int(pubdate)
TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'

According to the logs, the 500 error on mdp.39015060430082 is because the publication date is not an integer and we're trying to treat it as one. Looking at the marc record for that one, I think it's coming back as None, which indeed can't be converted to an integer. I can add error handling for that case; kind of surprised it hasn't come up before!
It looks like the bib api for this record has a publication date in the simple JSON record, I wonder why there isn't one in the MARC record?
https://catalog.hathitrust.org/api/volumes/full/htid/mdp.39015060430082.json

I suppressed and deleted mdp.39015043572422 and mdp.39015060430082 to get them out of the database, and then I was able to successfully reimport them. No 500 error, and the metadata imported successfully, so I guess these cases are fixed!

@rlskoeser I think these are fixed, too, right, so we can close this issue? I'm not sure if the rsync issue was the same as we had in #481, but uc1.b3514895 is successfully in the database.

@mnaydan I know we fixed one of the problems before; maybe it was the same rsync error and I just didn't know. If you don't have any other records you need to import that are causing problems, seems like we can go ahead and close.
How nice to see that the migration resolved some of these problems!


Switching from Sequence mode to Snake mode and back shifts visible area of canvas beyond visible frame. Forever.

Steps to Reproduce

Go to Macromolecules - Flex mode <---Important!
Load from file:
Switching from Sequence mode to Snake mode and back shifts visible area of canvas beyond visible frame.zip

Switch view to Sequence mode
Switch back to Snake mode

Actual behavior
Canvas forever shifted to the left and down partially beyond visisbility frame

Expected behavior
No shifting

Environment details:

Ketcher Version 2.23.0-rc.2 Build at 2024-07-10; 19:39:22
Indigo Toolkit Version 1.22.0-rc.2.0-ga21fb5d8f-wasm32-wasm-clang-19.0.0
Windows 10 Pro
Chrome Version 126.0.6478.127 (Official Build) (64-bit)

Issue found while testing - https://github.com/epam/ketcher/issues/3532

Maybe this will help developers understand the cause of bug: when I pressed zoom 100%, structure was centered.
https://github.com/epam/ketcher/assets/62464241/4185e12a-2f9c-43fe-9380-5d54b3eaccfb

Verified.

Ketcher Version 2.23.0-rc.3 Build at 2024-07-14; 20:34:10
Indigo Toolkit Version 1.22.0-rc.3.0-gbb5c51fc2-wasm32-wasm-clang-19.0.0
Windows 10 Pro
Chrome Version 126.0.6478.127 (Official Build) (64-bit)


Update design of query editor tab

Closes #379
Todo:

[x] Fixup mobile design

Mid width:

Mobile:

Also updated repl to use tree/table switcher:

James, any way you can generate a preview link? I’ll be able to test this next week otherwise.

Yep: https://nebula-ui-git-sql-updates-edgedb.vercel.app/
(Ignore that the SQL bit doesn't work right, I need to hide that stuff in cloud for <6.0 server versions)

Can't login to your preview link :/

Can't login to your preview link :/

It seems to work for me now. @1st1 Is it still broken for you?


feat(new construct): aws-openapigateway-lambda

Issue #, if available: #840
Description of changes:
Putting the README in place for the openapi-based apigateway-to-lambda construct.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: bf70adbddd15f128ed32cfb1fc4fda9725a007ee
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 23ecefe0d53c2f541f2325c4a452615b49eda0a5
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: b391da803958b78c0d160f130608be22b8710907
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 93d05bd31a96cfb203d81f6ab70523416e4c31b5
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0a622f768211ab3ffce3989263e67f27a8390f92
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 987b2fced37da50493d1eb4c9f801bd87c2ab457
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 79caa769e8b663b2cfb1fe5b97b84308e7f523b7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 6cff5b866f66565d031da06c7782e5238e9f9f49
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: fa7921db0b15e28b4e4abb1b2f71ad6d5fb819b7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 52e5a0ba5dafa21f9e652fdd9b968c2a1d40579d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: ca2fc49c87d5c4b15210eaec65f82d181b342864
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 88bdb00fecca3327e45c10688f72924e536a0b01
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e93b071ce6412d5cc0b098e2426780bf55b3745a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e46a15f3caf9521db28c72712bb6c6558973bfa9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: f2749ee009b6f51a69ef6ba1368870228997e5b6
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: f09acc78d2fa133cc3303df4e65c487baf89c6b3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 02da2e1e432717afd2fc733ae041a70def727119
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: a260a8e4347cdc31e446a6614fbdc2ebe4f5d360
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 56364dedc1d76fa2af678f42a8a973c973f0ce26
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 5cc005245f8803a4e455e7a985d84322617b999f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: d2c0a09dd1e3aeca3190e1c295f96647ffe376c0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: c600aac11db97286033535645aab58e7412b354d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 4c33302d1b60e4579a802d8b7d4deeb2dd187d85
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: b1d6b9daa6f4622b0b81c2bfb2d3f77c5dfd639c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0027bec107c46d9d29ad3217129759c1916d2aa1
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 704ddd9f615bdaf6cad5eee41956b6a054bf9b6f
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0ff749ad8fe13f829a585eddb05c976704501a1d
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 75386c534aa50dbaafa4f08e1c891d8c3a4827a3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 252963cb1b0d2ce2a8130870f692567d24bdc793
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID:<PHONE_NUMBER>fa27edeb8a3ff0671b367e804ef936
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 59d97741d6bd5974c5c61d2b8a68cd39ca0259a9
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 6e16923fac48d8a45fb7fd9862a7c8a7d6275a10
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: e74b89c7d5e689617fd6362c66045ce1b7683a41
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 2a91311b86c6e67877303eb66beefdcfe3793a4f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: c2ba30552d537519435f6df8d5115d0f165f3408
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: f742c9201fab0e6fefadaa6900277ad816cd3284
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 87a88ebbaa83f3dbfdaff0554f64c59154fb9771
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 1ed9b84a6fdff28e4b17dee816e93336ec117d71
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 43cd6993a0a6a22dfc1652c276e9f0d8fecd48c0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Update to current keystone structure

Hey,
I'm new to keystone and wonder if there is any motivation of updating this repository to the current (file) structure of the keystone-enclave/keystone. I think, since the keystone main repository holds all the other projects, like sm and sdk, the structure changed and now uses more CMakeLists than build scripts.
Trying to build a test eapp I got as far as running vault.sh but I cannot find the correct build script pointing to the eyrie runtime.
Maybe there is a way to make this run with the most recent keystone repo, I would not like to use an outdated keystone.

Hi,
Unfortunately this tool is not supported at all any more. We should have deprecated this repository a few years back.
Edge calls are manually generated right now. (If we want automatic generation we probably should write a new tool, rather than update this one.)
Please feel free to use issues on the main Keystone repo if you run into problems with any edgecall stuff!


does react native support indexeddb

i am refactoring a web app with RN, and web app is using IndexedDB as the storage, now the RN app can not work properly when disable the debug model, i would like to know whether RN support IndexedDB? any suggestion if the answer is not.

This issue looks like a question that would be best asked on StackOverflow.
StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.
Will close this as this is really a question that should be asked on StackOverflow.

Considering this is the authoritative repository, it would make sense to answer with two questions:
Does React Native, either implicitly or explicitly, support Indexed DB?
If no, are there plans to support Indexed DB in the future?
Punting this question really shouldn't be done without at least an authoritative answer to those two questions.


Perform periodic flush of ManagedCursor mark-delete posistions

Motivation
The updates on the managed cursor are (by default) rate limited to avoid generating a lot of write operations when consumers are acknowledging messages.
Due to the nature of the rate limiting, if the traffic on topic suddenly stops, the last updates to the cursor position are kept only in memory and they would be flushed only in 2 conditions, either:

The traffic resumes and the consumer acks again
The topic is gracefully closed

If the topic is not gracefully closed, the cursor will be rolled back to the last persisted position.
That will trigger re-delivery of potentially very old messages. Instead we should have a time-bound period after which we ensure that all cursor updates are flushed on disk.

#15031 and #15067 are needed to fix some race conditions caused by the periodic flushing.