refactor NbBlock to use OOP (hierarchy of objects / inheritance)

in the past we were not fan of OOP but that was probably not a good take
indeed we now think that for NbBlock it could make a lot of sense to have a base object and a hierarchy of objects that inherit from it
still need to make some experience in using OOP stuff (maybe in a nimib not related lib)

One problem we discussed in a past Speaking Hour is the fact that we must be able to serialize all our objects to JSON. The problem being that we don't have static knowledge of the exact type of each block. If we use the dynamic dispatch functionality of Nim, we can create a dumpHook for the base type and then call a method that returns the string of the specific type:
import jsony

type
  Nimib = ref object of RootObj
    a, b, c: int
  NimibChild = ref object of Nimib
    d, e: float

method dump(n: Nimib): string =
  n[].toJson()

method dump(n: NimibChild): string =
  n[].toJson()

method dumpHook*(s: var string, v: Nimib) =
  s.add v.dump()

let n1: Nimib = Nimib(a: 1, b: 2, c: 3)
let n2: Nimib = NimibChild(d: 3.14, e: 4.56)

echo n1.toJson()
echo n2.toJson()

The next problem then becomes how we parse the JSON again without losing the type information...

And here the template version is:
import jsony, tables

type
  Nimib = ref object of RootObj
    a, b, c: int
    typename: string
  NimibChild = ref object of Nimib
    d, e: float

var parseDefs: Table[string, proc (s: string, i: var int): Nimib]

template registerBlock(typename: untyped) =
  parseDefs[$typename] =
    proc (s: string, i: var int): Nimib =
      var v: typename
      new v
      parseHook(s, i, v[])
      result = v

  method dump(n: typename): string =
    n[].toJson()

# neccecary to avoid compile error
method dump(n: Nimib): string =
    n[].toJson()

proc dumpHook*(s: var string, v: Nimib) =
  s.add v.dump()

proc parseHook*(s: string, i: var int, v: var Nimib) =
  # First parse the typename
  var n: Nimib = Nimib()
  let current_i = i
  parseHook(s, i, n[])
  # Reset i
  i = current_i
  # Parse the correct type
  let typename = n.typename
  v = parseDefs[typename](s, i)

registerBlock(Nimib)
registerBlock(NimibChild)

let n1: Nimib = Nimib(a: 1, b: 2, c: 3, typename: "Nimib")
let n2: Nimib = NimibChild(a: 100, d: 3.14, e: 4.56, typename: "NimibChild")

echo n1.toJson()
echo n2.toJson()

let s = n2.toJson().fromJson(Nimib)
echo s.toJson()

It's just one extra line of code for a block developer with this approach.

With this, I think we might actually be able to start working for real on a refactoring of Nimib.

Wow this looks very interesting, thanks a lot! I will have to look at it more closely and try it out! Will let you know my thoughts!

some discussion here: https://github.com/nimib-land/nblog/issues/20


Add YouTube URL to Podcast Description

Using this tool I came across a bug when a YouTube video has no description it will fail to save the  episode.
This is because anchor.fm requires one to put a description into the podcast and it won't let you press save till you do so.
One solution is to offer an env flag to add the YouTube URL to the bottom of the description, thereby when set to true it guarantees to always have a description.

I should note that I ran two successful local runs one with the flag and one without it


DBC 9.0.X

Can update to support the 9.0.X Version?

SL DBC is now supported thanks to funjoker contribution :)


Option for manually split /unsplit variable store

Neither validFieldsOnly nor allOffsets setting for load /store splitting does not effect the example code below. I believe that there will be some cases like below where manually split /unsplit option would be useful.
void init_proxy_ctx()

00410d50  init_wsa_ctx(&proxy_ctx.local_wsa)
00410d5a  init_wsa_ctx(&proxy_ctx.remote_wsa)
00410d67  proxy_ctx.local_thread.o = zx.o(0)
00410d6e  InitializeCriticalSection(&proxy_ctx.lock)

proxy_ctx structure:
struct proxy_ctx
{
    int32_t waiting;
    struct wsa_ctx local_wsa;
    int32_t field_1e0;
    struct wsa_ctx remote_wsa;
    int32_t field_3c0;
    HANDLE local_thread;
    int32_t field_3c8;
    HANDLE remote_thread;
    int32_t field_3d0;
    struct cc_handler* cc_handler;
    struct RTL_CRITICAL_SECTION lock;
};

Database shared in private with us. Anyone from vector35 should search "16260762028509746446" for it


Indicate that account gets created via linkdrop

When opening linkdrop in the wallet, there is no way to learn what is actually happening.
Specifically, would be good to show that:

This is a link drop
How much funds / assets are dropped via it

If already have an account it, it should show "Accept " and button OK instead of "Create Account" screen.

Closing as issue is outdated


Keep records of deleted ServiceUploads

Right now our app is fully CRUD for ServiceUploads. That's not a good architecture because we always need to have an audit trail for user actions. Instead of removing deleted ServiceUploads from our database, we should record the deleted status on a database field and also log the IDs of the services we deleted. Does that sound about right @kevinrobinson?

@alexsoble Yeah we could handle this by adding fields to the ServiceUpload model, or alternately we could make a new model called Logs and then just log a JSON object that has the data about this particular action (or any other thing where we want a durable audit trail).
It seems like the second might be simpler for developers: "hey, want to do something sort of destructive?  just log it as JSON!" rather than mixing in this concern in with product features.  If it's needed for the product (like a service being discontinued) then it should go on the model proper but if not just log it (like this case here).

@kevinrobinson That works for me! Logs!


Update documentation

Add documentation for #2730 #2731 and cleanup defined macros.

Coverage remained the same at 99.982% when pulling d0ab2b86c34368f8f470c807041cefa6e2ff7a03 on docs into 8a29a6ecf4d228b5d7807a2df5ac352806da8ae8 on develop.


Cannot add library

I add this library by this line:
    implementation 'com.github.shaon2016:ProPicker:1.0.4'
But when I try to run app this error occurs:
Could not GET 'https://jitpack.io/com/github/florent37/inline-activity-result-kotlin/1.0.4/inline-activity-result-kotlin-1.0.4.pom'. Received status code 401 from server: Unauthorized
and if I remove library, everything is ok

Yes


update alert manager configuration fix typo

slack_config is an error in alert manager, it should be slack_configs

The docs are correct, it's describing a single slack config.

relevant YAML:
receivers:

name: 'mattermost'
slack_config:

api_url: 'http://blahblah'
channel: '#Town Square'

21:08 docker/3f250690b399[737]: time="2016-07-07T05:21:08Z" level=error msg="Loading configuration file failed: unknown fields in receiver config: slack_config" file="/etc/alertmanager/config.yml" source

Yes, that's what the docs say.

Sorry I'm confused.  The docs as I read them say use 'slack_config' (i.e. no s at the end).  however, alertmanager, the code seems to want the s at the end.  That's why I made this pull request, to add the s at the end.

So at the very least, the documentation is confusing (at least to me).  I think we can at least agree, the YAML file needs the s at the end, since that's the only way the code runs.... yes?
Are the docs not confusing to anyone else?

￼> the YAML file needs the s at the end, since that's the only way the code runs.... yes?
Yes, which is documented at https://prometheus.io/docs/alerting/configuration/#receiver-

OK, I spent some time re-reading the documentation, since you kept saying that slack_configs is documented..  First I apologize this was definitely a drive-by patch, and I clearly didn't read the docs correctly.  You are correct, the word slack_configs does indeed show up, exactly once, in a block quote. the word slack_config however shows up 3 times, despite it not showing up in the YAML file at all, and is merely a placeholder for the actual config.
Overall I want the documentation to be easier to parse, when you are just trying to make it work.  Right now, you are correct, it IS documented, but it's pretty obtuse, with the slack_config (and all the other _config words on that page, it's very easy(at least for me) to assume that's the word you put in the YAML file....
If I spent some actual time re-working that whole page, adding in some words, and giving examples, and removing the word 'slack_config' (and replacing it with say... Slack Config (no _) so it's clear it's not tied to what you actually put in the YAML, would that be better looked upon?
If not that's fine, I was just trying to make other people's lives easier. Either way, let's get rid of this pull request, since it's also clearly incorrect with the rest of the documentation.

The thing is that above we call it slack_config so calling it anything else (particularly with spaces) will cause ambiguity when you consider how it's a list, and then we'd get to repeat the list semantics in each receiver type - which is also messy.
This is reference documentation, it's not the place for examples.


Rename default branch and check phrasing codebase

As per intended BCP Knodel & ten Oever and changed GitHub standards, we should rename the default branch to main.
Additionally, check if our codebase(s) unintentionally uses outdated phrasing.

Fixed with the open-sourcing and in https://github.com/Inter-Actief/amelie-private/pull/603


Installed google-cloud-cpp w/ OpenTelemetry usable from make(1)

If google-cloud-cpp is compiled and installed with OpenTelemetry, we need to make sure the proper Cflags are present in the package config for the library.
OpenTelemetry does not generate a package config file, so we will have to include their Cflags as well, or install a *.pc file for them.

Still blocked on OTel, but they are making progress.


Xref keyref resolves to wrong link text when using key definitions inside a chapter reference

I'm attaching a small DITA project file. If I publish it to a PDF, the "Cross-references" topic at the end of the PDF has two links in it. The link texts are wrong. They should be:
The AES latency is given in Latency of AES on page 3.
The SAES latency is given in Latency of SAES on page 5.

but they end up being:
The AES latency is given in AES48.
The SAES latency is given in SAES250.
Cross-references-test.zip

In the "KeyrefPaser" class there is this code which gathers keywords, but it goes very deep:
                      final List<Element> keywords = toList(elem.getElementsByTagName(TOPIC_KEYWORD.localName));
                    final List<Element> keywordsInKeywords = keywords.stream()
                            .filter(item -> TOPIC_KEYWORDS.matches(item.getParentNode()))
                            .collect(Collectors.toList());

for example when the keywords are gathered from this chapter:
 <chapter href="Latency.dita" keyscope="SAES" keys="saes">
    <ditavalref format="xml" href="SAES.ditaval"/>
    <keydef keys="IP_name">
        <topicmeta>
            <keywords>
                <keyword>SAES</keyword>
            </keywords>
        </topicmeta>
    </keydef>

the code returns the keywords which actually belong to its child "keydefs".
As a possible fix I replaced the code "item -> TOPIC_KEYWORDS.matches(item.getParentNode())" with a method which also checks that the closest topicref to the defined keywords is the topicref from which we want to obtain the keywords:
/**
 * @param item The element.
 * @return true if the keyword is a proper descendent of the initial element.
 */
private boolean isDescendentKeyWord(Element item, Element initialElement) {
	Node itemParent = item.getParentNode();
	if(TOPIC_KEYWORDS.matches(itemParent)) {
		Element closestParentTopicRef = null;
		while(itemParent != null) {
			if(itemParent instanceof Element) {
				if(((Element)itemParent).getAttribute(DITAConstants.CLASS_ATTR_NAME).contains(DITAConstants.TOPIC_REF_CLASS)) {
					closestParentTopicRef = (Element) itemParent;
					break;
				}
			}
			itemParent = itemParent.getParentNode();
		}
		if(closestParentTopicRef != null && closestParentTopicRef != initialElement) {
			return false;
		}
		return true;
	}
	return false;
}


Use Go build cache in uptest runs

Description of your changes

This PR proposes to add Go build cache to uptest to speed up uptest runs.
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/test-examples="examples/ec2/vpc.yaml"

/test-examples="examples/ec2/vpc.yaml"

/test-examples="examples/ec2/vpc.yaml"

Go build caching successfully observed here:
https://github.com/upbound/provider-aws/actions/runs/3837465081/jobs/6532806915
Closing this PR as we are consuming upbound/uptest main HEAD for running uptest.
Something we may further discuss is dependency pinning for reusable workflows:
https://github.com/upbound/team-extensions/issues/77

Go build caching successfully observed here:
https://github.com/upbound/provider-aws/actions/runs/3837465081/jobs/6532806915
Closing this PR as we are consuming upbound/uptest main HEAD for running uptest.
Something we may further discuss is dependency pinning for reusable workflows:
https://github.com/upbound/team-extensions/issues/77


flip-link error

windows os: 11
I use https://github.com/knurling-rs/app-template generate project
add
cortex-m-rtic = { version = "1.1.3" }

error: linking with `flip-link` failed: exit code: 1
  |
  = note: "flip-link" "-flavor" "gnu" "C:\\Users\\zhaobo\\AppData\\Local\\Temp\\rustck3K05Z\\symbols.o" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\main-11049d013bb1904c.main.2fc7ea03-cgu.0.rcgu.o" "--as-needed" "-L" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps" "-L" "D:\\projects\\embeed\\app\\target\\debug\\deps" "-L" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\build\\cortex-m-5817308009678109\\out" "-L" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\build\\cortex-m-rt-4199a1caeb388d95\\out" "-L" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\build\\defmt-d86b0063a8a3b56a\\out" "-L" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\build\\stm32f1-14b8b2830e44275e\\out" "-L" "D:\\software\\rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7m-none-eabi\\lib" "-Bstatic" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libstm32f1xx_hal-8051c863c3ad98b5.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libfugit_timer-fe7d59127748e96a.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libbxcan-e9e7ad35b16a23e4.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libstm32_usbd-ed785f6b86adbff3.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libusb_device-a233a87681d50602.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libfugit-6c4bc25732b1db27.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libgcd-4197544a75179d12.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libembedded_dma-d8fa02c1119216ed.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libstm32f1-b31ddd66260981cf.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libcortex_m_rt-c1a6a9ab4f0cfe1e.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\librtic-34882a4391d40282.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libheapless-3a2e6cf7174401b1.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libstable_deref_trait-b94e8061351ccd46.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libhash32-2ef9212d208b60d7.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libbyteorder-90345a976a4d83d8.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libbare_metal-7b4e9559ea5371a8.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\librtic_monotonic-8232f0df63c185a6.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\librtic_core-fbd27b968ff823cf.rlib" "--start-group" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libpanic_probe-a9b08e11c9fb609a.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libdefmt-d4cf8a2ca51cf9ce.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libbitflags-5351597746fc1950.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libcortex_m-f44fc0a28245896b.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libembedded_hal-0f940bf2e1d93e1f.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libvoid-b7e1daec3a29df70.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libnb-9a0f1077e9087fcc.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libnb-89e12803df9a6252.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libvolatile_register-1ef2fbeaac4c48e3.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libvcell-894f713cc598d2e9.rlib" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\libbare_metal-392c59e661be3df0.rlib" "D:\\software\\rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7m-none-eabi\\lib\\librustc_std_workspace_core-d708ca894357bb88.rlib" "D:\\software\\rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7m-none-eabi\\lib\\libcore-7279b5ba9f24caff.rlib" "--end-group" "D:\\software\\rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7m-none-eabi\\lib\\libcompiler_builtins-25380e8375a00138.rlib" "-Bdynamic" "--eh-frame-hdr" "-znoexecstack" "-L" "D:\\software\\rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7m-none-eabi\\lib" "-o" "D:\\projects\\embeed\\app\\target\\thumbv7m-none-eabi\\debug\\deps\\main-11049d013bb1904c" "--gc-sections" "-O1" "-Tlink.x" "-Tdefmt.x" "--nmagic"
  = note: rust-lld: error: undefined symbol: _defmt_acquire
          >>> referenced by mod.rs:55 (D:\software\cargo\registry\src\rsproxy.cn-8f6827c7555bfaf8\defmt-0.3.2\src\export\mod.rs:55)
          >>>               panic_probe-a9b08e11c9fb609a.panic_probe.02df55b0-cgu.0.rcgu.o:(rust_begin_unwind) in archive D:\projects\embeed\app\target\thumbv7m-none-eabi\debug\deps\libpanic_probe-a9b08e11c9fb609a.rlib

          rust-lld: error: undefined symbol: _defmt_release
          >>> referenced by mod.rs:71 (D:\software\cargo\registry\src\rsproxy.cn-8f6827c7555bfaf8\defmt-0.3.2\src\export\mod.rs:71)
          >>>               panic_probe-a9b08e11c9fb609a.panic_probe.02df55b0-cgu.0.rcgu.o:(rust_begin_unwind) in archive D:\projects\embeed\app\target\thumbv7m-none-eabi\debug\deps\libpanic_probe-a9b08e11c9fb609a.rlib

          rust-lld: error: undefined symbol: _defmt_write
          >>> referenced by mod.rs:85 (src\export\mod.rs:85)
          >>>               defmt-d4cf8a2ca51cf9ce.defmt.d14e61bb-cgu.0.rcgu.o:(_$LT$$RF$mut$u20$W$u20$as$u20$core..fmt..Write$GT$::write_char::hbf1e7cda46151703) in archive D:\projects\embeed\app\target\thumbv7m-none-eabi\debug\deps\libdefmt-d4cf8a2ca51cf9ce.rlib
          >>> referenced by mod.rs:85 (src\export\mod.rs:85)
          >>>               defmt-d4cf8a2ca51cf9ce.defmt.d14e61bb-cgu.0.rcgu.o:(_$LT$$RF$mut$u20$W$u20$as$u20$core..fmt..Write$GT$::write_str::h9be493d4997977cf) in archive D:\projects\embeed\app\target\thumbv7m-none-eabi\debug\deps\libdefmt-d4cf8a2ca51cf9ce.rlib
          >>> referenced by mod.rs:85 (src\export\mod.rs:85)
          >>>               defmt-d4cf8a2ca51cf9ce.defmt.d14e61bb-cgu.0.rcgu.o:(defmt::export::istr::hf51bfc040acfc767) in archive D:\projects\embeed\app\target\thumbv7m-none-eabi\debug\deps\libdefmt-d4cf8a2ca51cf9ce.rlib
          >>> referenced 2 more times

          flip-link: the native linker failed to link the program normally; please check your project configuration and linker scripts

warning: `app` (bin "main") generated 3 warnings
error: could not compile `app` due to previous error; 3 warnings emitted

I am not able to reproduce the error. I added cortex-m-rtic to a the app-template, but the bins still compiles just fine for me.
The error says error: undefined symbol: _defmt_release and the same for _defmt_release and _defmt_write. Do you have defmt-rtt in your list of dependencies? (It should be there by default).
What happens if you remove "-C", "linker=flip-link", from the rustflags in .cargo/config.toml? This will skip flip-link and just invoke the native linker.
rustflags = [
-  "-C", "linker=flip-link",
  "-C", "link-arg=-Tlink.x",
  "-C", "link-arg=-Tdefmt.x",
  # This is needed if your flash or ram addresses are not aligned to 0x10000 in memory.x
  # See https://github.com/rust-embedded/cortex-m-quickstart/pull/95
  "-C", "link-arg=--nmagic",
]

I'm running into the same issue, however when I remove the line in config.toml I get this:
error: linking with `rust-lld` failed: exit code: 1
  |
  = note: "rust-lld" "-flavor" "gnu" "C:\\Users\\Ragarnoy\\AppData\\Local\\Temp\\rustc5b0jk9\\symbols.o" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\deps\\hello-8229623d76740f1f.hello.f932f36f-cgu.0.rcgu.o" "--as-needed" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\deps" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\debug\\deps" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\build\\cortex-m-c452bec137310b55\\out" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\build\\cortex-m-rt-be4f982373b21b56\\out" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\build\\defmt-7fb01f6acebd88d4\\out" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\build\\dk-54fd7126418f8b29\\out" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\build\\nrf52840-hal-19cebceb665df9d9\\out" "-L" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\build\\nrf52840-pac-e7d0e23c12afa921\\out" "-L" "C:\\Users\\Ragarnoy\\.rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7em-none-eabihf\\lib" "-Bstatic" "C:\\Users\\Ragarnoy\\AppData\\Local\\Temp\\rustc5b0jk9\\libcortex_m-3b1a265280aea223.rlib" "C:\\Users\\Ragarnoy\\.rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7em-none-eabihf\\lib\\libcompiler_builtins-1f7e7d1541f43b6f.rlib" "-Bdynamic" "--eh-frame-hdr" "-znoexecstack" "-L" "C:\\Users\\Ragarnoy\\.rustup\\toolchains\\stable-x86_64-pc-windows-msvc\\lib\\rustlib\\thumbv7em-none-eabihf\\lib" "-o" "C:\\Users\\Ragarnoy\\embedded-trainings-2020\\beginner\\apps\\target\\thumbv7em-none-eabihf\\debug\\deps\\hello-8229623d76740f1f" "--gc-sections" "-Tlink.x" "-Tdefmt.x"
  = note: rust-lld: warning: section type mismatch for .uninit.defmt-rtt.BUFFER
          >>> C:\Users\Ragarnoy\embedded-trainings-2020\beginner\apps\target\thumbv7em-none-eabihf\debug\deps\hello-8229623d76740f1f.hello.f932f36f-cgu.0.rcgu.o:(.uninit.defmt-rtt.BUFFER): SHT_PROGBITS
          >>> output section .uninit: SHT_NOBITS

          rust-lld: warning: section type mismatch for .got
          >>> <internal>:(.got): SHT_PROGBITS
          >>> output section .got: SHT_NOBITS

          rust-lld: warning: section type mismatch for .got.plt
          >>> <internal>:(.got.plt): SHT_PROGBITS
          >>> output section .got: SHT_NOBITS

          rust-lld: warning: section type mismatch for .got
          >>> <internal>:(.got): SHT_PROGBITS
          >>> output section .got: SHT_NOBITS

          rust-lld: error: undefined symbol: _critical_section_1_0_acquire
          >>>               C:\Users\Ragarnoy\embedded-trainings-2020\beginner\apps\target\thumbv7em-none-eabihf\debug\deps\hello-8229623d76740f1f.hello.f932f36f-cgu.0.rcgu.o:(_defmt_acquire)

          rust-lld: error: undefined symbol: _critical_section_1_0_release
          >>> referenced by lib.rs:45 (C:\Users\Ragarnoy\.cargo\registry\src\github.com-1ecc6299db9ec823\critical-section-0.2.8\src\lib.rs:45)
          >>>               C:\Users\Ragarnoy\embedded-trainings-2020\beginner\apps\target\thumbv7em-none-eabihf\debug\deps\hello-8229623d76740f1f.hello.f932f36f-cgu.0.rcgu.o:(_defmt_release)

error: could not compile `apps` due to previous error

That's caused by an update to critical-section and isn't a flip-link bug. The update resolves an unsoundness bug, but requires you to opt-in to a trait implementation from somewhere (or write your own) - if you don't, you are missing those two symbols.
See https://docs.rs/critical-section/latest/critical_section/#usage-in-no-std-binaries.

That's caused by an update to critical-section and isn't a flip-link bug (although perhaps we need to bump some dependencies in our example project). The update resolves an unsoundness bug, but requires you to opt-in to a trait implementation from somewhere (or write your own) - if you don't, you are missing those two symbols.
See https://docs.rs/critical-section/latest/critical_section/#usage-in-no-std-binaries.

tyvm!

Please see our blog post on the issue for how to fix it and how it happened: https://ferrous-systems.com/blog/defmt-rtt-linker-error/


auto reconnect when connection dropped [feature request]

By nature, the majority of individual nodes in Mysterium are not as stable as a commercial VPN. If for no other reason, this is because the node operators need to update their software occasionally, and the instructions for doing so on the web site ensure that any connections will be dropped when this occurs. Thus, it is necessary to have some kind of feature to automatically reconnect when the connection drops.
Three possibilities are the following:

Auto reconnect to same node. This assumes that the node will come back online in a couple minutes, most likely a result of an update/reboot/power-outage.
Auto reconnect to another node in the same country.
Auto reconnect to any node in a different country.

It will be nice to have this feature. Specially on MacOSes when entered in sleep mode all net is shutted off.
When the OS wake up I always need to reconnect manually.

How is this feature request still not being worked on? Almost every competitor has this feature...

Thanks guys! MysteriumVPN team completely agrees with you guys. I am gonna go ahead and move this to our our DVPN ideas/backlog (prioritized list of functionality requests) so we can implement it ASAP.

Thanks guys! MysteriumVPN team completely agrees with you. I am gonna go ahead and move this to our our DVPN ideas/backlog (prioritized list of functionality requests) so we can implement it ASAP.

Any news on this? Whisout this feature the VPN is unfortunatly completly useless for me


chore(cliff.toml): replace date_order with topo_order

Description

To adapt the interface of https://github.com/orhun/git-cliff/releases/tag/v1.0.0.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

# Changelog

All notable changes to this project will be documented in this file.

## [0.1.0] - 2022-12-26

### Features

- V0.1.0

<!-- generated by git-cliff -->
Previous HEAD position was a055c3f feat: v0.1.0
HEAD is now at 4f6ec75 fix: v0.1.1
------
v0.1.1
 WARN  git_cliff > "cliff.toml" is not found, using the default configuration.
# Changelog

All notable changes to this project will be documented in this file.

## [0.1.1] - 2022-12-26

### Bug Fixes

- V0.1.1

<!-- generated by git-cliff -->
Previous HEAD position was 4f6ec75 fix: v0.1.1
HEAD is now at 4308fa9 feat: v0.2.0
------
v0.2.0
 WARN  git_cliff > "cliff.toml" is not found, using the default configuration.
# Changelog

All notable changes to this project will be documented in this file.

## [0.2.0] - 2022-12-26

### Features

- V0.2.0

<!-- generated by git-cliff -->
Previous HEAD position was 4308fa9 feat: v0.2.0
HEAD is now at 13a75a3 feat: v0.3.0
------
v0.3.0
 WARN  git_cliff > "cliff.toml" is not found, using the default configuration.
# Changelog

All notable changes to this project will be documented in this file.

## [0.3.0] - 2022-12-26

### Features

- V0.3.0

<!-- generated by git-cliff -->

Without --topo-order (v0.3.0 is wrong):
------
v0.1.0
 WARN  git_cliff > "cliff.toml" is not found, using the default configuration.
# Changelog

All notable changes to this project will be documented in this file.

## [0.1.0] - 2022-12-26

### Features

- V0.1.0

<!-- generated by git-cliff -->
Previous HEAD position was faf9a6f feat: v0.1.0
HEAD is now at d737797 fix: v0.1.1
------
v0.1.1
 WARN  git_cliff > "cliff.toml" is not found, using the default configuration.
# Changelog

All notable changes to this project will be documented in this file.

## [0.1.1] - 2022-12-26

### Bug Fixes

- V0.1.1

<!-- generated by git-cliff -->
Previous HEAD position was d737797 fix: v0.1.1
HEAD is now at 1f9e4d9 feat: v0.2.0
------
v0.2.0
 WARN  git_cliff > "cliff.toml" is not found, using the default configuration.
# Changelog

All notable changes to this project will be documented in this file.

## [0.2.0] - 2022-12-26

### Features

- V0.2.0

<!-- generated by git-cliff -->
Previous HEAD position was 1f9e4d9 feat: v0.2.0
HEAD is now at 35df5dd feat: v0.3.0
------
v0.3.0
 WARN  git_cliff > "cliff.toml" is not found, using the default configuration.
# Changelog

All notable changes to this project will be documented in this file.

## [0.3.0] - 2022-12-26

### Features

- V0.3.0

## [0.2.0] - 2022-12-26

### Features

- V0.2.0

<!-- generated by git-cliff -->

Memo: git tag v0.0.0 was necessary when --topo-order and current_tag_index == 1.


Missing release / license / dependency to psalm

Hi Fabien, nice looking package!
I'd like to try this out, but it's missing a few things:

an initial release
a reasonable dependency to a psalm version (it currently requires "vimeo/psalm": "dev-master")
a License

It would be great if you can pick this up after the two years that passed since your last commit.
Of course I understand that everyone in our area is busy and that you might have moved on to other things.
Regards, Clemens

Hello,
Thank you!
I added an explicit file for the license (it was set in composer.json already). I updated psalm dependency and I just did an initial release.
I'll close this issue but let me know if you have any other issue.
Cheers


Unblock modules and improve guest path resolution

This PR fixes issues #11 and #12 where path resolution of the main DSC manifest was broken when provided a relative path in manifests_path or configuration_file (in particular when the path contains a '../' part) or when a module_path is not provided.
It improves the process by converting paths to absolute URLs on the guest.
Secondly, it addresses a valid, albeit unlikely scenario, highlighted by the intentions of PR #10, where DSC modules need to be explicitly 'unblocked' before they can be run.

Coverage remained the same when pulling cd1fd45d2395c0448dac52755bbe89963f906a5e on bugfix/issue11 into 7cf22fd2ffb22b252c7755e8b5fce4d9f6ee2377 on master.


fix(config): remove SecTmpDir directive, unsupported in v3

Fixes #61.
Signed-off-by: Felipe Zipitria<EMAIL_ADDRESS>

Probably need to rebase after #70 gets merged.

It's still mandatory for v2, isn't it?
We're only removing it in v3, that's good, but doesn't the recommended file affect both versions?

Reviewing the documentation, it is indeed needed for v2. So I think it makes sense to do nothing here. Will close this one and comment on the issue.


Add Madgrad

preferably the modified version with weight decay from here https://github.com/lessw2020/Best-Deep-Learning-Optimizers ?

Hi, I will look into it.


Feature/package updates

Some security patches involving updating libraries and removal of deprecated and unused libraries.
Eliminates most warnings on Linux yarn installations
Eliminates most warnings on Mac env yarn installations
Precludes dependabot automatic updates by committing newer lockfile that include higher versions to eliminate security vulnerabilities.

Dependabot PRs that will be closed:
Bump diff from 3.3.1 to 3.5.0  dependencies
#379 opened yesterday by dependabot bot

Bump bl from 1.2.2 to 1.2.3  dependencies
#378 opened yesterday by dependabot bot

Bump hosted-git-info from 2.8.8 to 2.8.9  dependencies
#375 opened on May 9 by dependabot bot
 1

Bump lodash from 4.17.15 to 4.17.21  dependencies
#374 opened on May 8 by dependabot bot
 1

Bump handlebars from 4.7.6 to 4.7.7  dependencies
#373 opened on May 7 by dependabot bot
 1

Bump ssri from 6.0.1 to 6.0.2  dependencies
#369 opened on Apr 29 by dependabot bot

Verification that newer versions are taken in yarn.lock:
USER@CPSC-W-USER ubccpsc-tech-classy % yarn why diff
yarn why v1.10.1
[1/4] 🤔  Why do we have the module "diff"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "diff"
info Reasons this module exists
   - "workspace-aggregator-99c568b0-cc20-4a5c-9f30-143252534ec1" depends on it
   - Hoisted from "_project_#ts-node#diff"
   - Hoisted from "_project_#autotest#ts-node#diff"
   - Hoisted from "_project_#portal-backend#ts-node#diff"
info Disk size without dependencies: "680KB"
info Disk size with unique dependencies: "680KB"
info Disk size with transitive dependencies: "680KB"
info Number of shared dependencies: 0
=> Found<EMAIL_ADDRESS>info This module exists because "_project_#mocha" depends on it.
info Disk size without dependencies: "440KB"
info Disk size with unique dependencies: "440KB"
info Disk size with transitive dependencies: "440KB"
info Number of shared dependencies: 0
=> Found<EMAIL_ADDRESS>info This module exists because "_project_#tslint" depends on it.
info Disk size without dependencies: "416KB"
info Disk size with unique dependencies: "416KB"
info Disk size with transitive dependencies: "416KB"
info Number of shared dependencies: 0
✨  Done in 0.41s.
USER@CPSC-W-USER ubccpsc-tech-classy % yarn why bl
yarn why v1.10.1
[1/4] 🤔  Why do we have the module "bl"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "_project_#mongodb" depends on it
   - Hoisted from "_project_#mongodb#bl"
info Disk size without dependencies: "80KB"
info Disk size with unique dependencies: "344KB"
info Disk size with transitive dependencies: "560KB"
info Number of shared dependencies: 7
=> Found<EMAIL_ADDRESS>info This module exists because "_project_#autotest#dockerode#tar-fs#tar-stream" depends on it.
info Disk size without dependencies: "60KB"
info Disk size with unique dependencies: "324KB"
info Disk size with transitive dependencies: "540KB"
info Number of shared dependencies: 7
✨  Done in 0.39s.
USER@CPSC-W-USER ubccpsc-tech-classy % yarn why hosted-git-info
yarn why v1.10.1
[1/4] 🤔  Why do we have the module "hosted-git-info"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
error We couldn't find a match!
✨  Done in 0.35s.
USER@CPSC-W-USER ubccpsc-tech-classy % yarn why hosted-git-info
USER@CPSC-W-USER ubccpsc-tech-classy % yarn why lodash
yarn why v1.10.1
[1/4] 🤔  Why do we have the module "lodash"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "_project_#restify" depends on it
   - Hoisted from "_project_#restify#lodash"
   - Hoisted from "_project_#restify#restify-errors#lodash"
   - Hoisted from "_project_#restify#restify-errors#@netflix#nerror#lodash"
   - Hoisted from "_project_#portal-backend#source-map-loader#async#lodash"
info Disk size without dependencies: "4.88MB"
info Disk size with unique dependencies: "4.88MB"
info Disk size with transitive dependencies: "4.88MB"
info Number of shared dependencies: 0
✨  Done in 0.40s.
USER@CPSC-W-USER ubccpsc-tech-classy % yarn why handlebars
yarn why v1.10.1
[1/4] 🤔  Why do we have the module "handlebars"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "_project_#autotest#xunit-viewer" depends on it
   - Hoisted from "_project_#autotest#xunit-viewer#handlebars"
info Disk size without dependencies: "2.95MB"
info Disk size with unique dependencies: "4.66MB"
info Disk size with transitive dependencies: "4.66MB"
info Number of shared dependencies: 4
✨  Done in 0.37s.
USER@CPSC-W-USER ubccpsc-tech-classy % yarn why ssri
yarn why v1.10.1
[1/4] 🤔  Why do we have the module "ssri"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "_project_#portal-frontend#copy-webpack-plugin#cacache" depends on it
   - Hoisted from "_project_#portal-frontend#copy-webpack-plugin#cacache#ssri"
info Disk size without dependencies: "56KB"
info Disk size with unique dependencies: "104KB"
info Disk size with transitive dependencies: "136KB"
info Number of shared dependencies: 2
✨  Done in 0.34s.
USER@CPSC-W-USER ubccpsc-tech-classy %

@winstan Please note that some warnings still exist because their upstream libraries have not had the proper fixes implemented and there is no appropriate new version to include.

This has been manually QAed and I see no issues.

I found a bug with Webpack. I will have to take a deeper look at this.

Webpack issue has been fixed.


feat(api-key-service): add api-keys table

#230  👈
main

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

Join @jakim929 and the rest of your teammates on  Graphite


X-AUTH-* deprecated

The X-AUTH-* authorization, see https://www.kimai.org/documentation/2.13.0/user-api.html, is deprecated and does not work on our on-premise-installation of current Kimai, although it works on the current Kimai Demo.
Correct authorization scheme is Authorization: Bearer, see https://www.kimai.org/documentation/user-api.html.
I'll make a pull request.

Side note: I saw, X-AUTH-* probably still works (didn't try), when setting and using an API password instead of a token, see https://demo-stable.kimai.org/de/profile/susan_super/api-token. But anyway, also there it's marked as deprecated.


Issue with moving files from hca-util-upload area to annotare

Description of the task:
Attempting to move files from the hca-util-upload-area 4777804d-1b93-4bbf-955f-1c5083e2c504 to a specific ftp location: lftp ftp-private-2.ebi.ac.uk/kwkrk75w-3u4pe7e6pe9mc/
I am attempting to do this via moving specific files from the hca-util upload area to the data/wteh/ folder in the EC2, and then moving from the data/wteh/ folder to the ftp location.
The issue here is with moving from the hca-util upload area to the data/wteh/ folder.
hca-util download -f 5478STDY7698210_S1_L001_I1_001.fastq.gz 5478STDY7698210_S1_L001_R1_001.fastq.gz 5478STDY7698210_S1_L001_R2_001.fastq.gz 5698STDY7839908_S1_L001_I1_001.fastq.gz 5698STDY7839908_S1_L001_R1_001.fastq.gz 5698STDY7839908_S1_L001_R2_001.fastq.gz 5698STDY7839910_S1_L001_I1_001.fastq.gz 5698STDY7839910_S1_L001_R1_001.fastq.gz 5698STDY7839910_S1_L001_R2_001.fastq.gz 5698STDY7839918_S1_L001_I1_001.fastq.gz 5698STDY7839918_S1_L001_R1_001.fastq.gz 5698STDY7839918_S1_L001_R2_001.fastq.gz 5891STDY8062349_S1_L001_I1_001.fastq.gz 5891STDY8062349_S1_L001_R1_001.fastq.gz 5891STDY8062349_S1_L001_R2_001.fastq.gz 5891STDY8062350_S1_L001_I1_001.fastq.gz 5891STDY8062350_S1_L001_R1_001.fastq.gz 5891STDY8062350_S1_L001_R2_001.fastq.gz 5891STDY8062351_S1_L001_I1_001.fastq.gz 5891STDY8062351_S1_L001_R1_001.fastq.gz 5891STDY8062351_S1_L001_R2_001.fastq.gz 5891STDY8062352_S1_L001_I1_001.fastq.gz 5891STDY8062352_S1_L001_R1_001.fastq.gz 5891STDY8062352_S1_L001_R2_001.fastq.gz 5891STDY8062353_S1_L001_I1_001.fastq.gz 5891STDY8062353_S1_L001_R1_001.fastq.gz 5891STDY8062353_S1_L001_R2_001.fastq.gz 5891STDY8062354_S1_L001_I1_001.fastq.gz 5891STDY8062354_S1_L001_R1_001.fastq.gz 5891STDY8062354_S1_L001_R2_001.fastq.gz 5891STDY8062355_S1_L001_I1_001.fastq.gz 5891STDY8062355_S1_L001_R1_001.fastq.gz 5891STDY8062355_S1_L001_R2_001.fastq.gz 5891STDY8062356_S1_L001_I1_001.fastq.gz 5891STDY8062356_S1_L001_R1_001.fastq.gz 5891STDY8062356_S1_L001_R2_001.fastq.gz WSSS8011222_S1_L001_I1_001.fastq.gz WSSS8011222_S1_L001_R1_001.fastq.gz WSSS8011222_S1_L001_R2_001.fastq.gz WSSS8012016_S1_L001_I1_001.fastq.gz WSSS8012016_S1_L001_R1_001.fastq.gz WSSS8012016_S1_L001_R2_001.fastq.gz 5891STDY9030806_S1_L001_I1_001.fastq.gz 5891STDY9030806_S1_L001_R1_001.fastq.gz 5891STDY9030806_S1_L001_R2_001.fastq.gz 5891STDY9030807_S1_L001_I1_001.fastq.gz 5891STDY9030807_S1_L001_R1_001.fastq.gz 5891STDY9030807_S1_L001_R2_001.fastq.gz 5891STDY9030808_S1_L001_I1_001.fastq.gz 5891STDY9030808_S1_L001_R1_001.fastq.gz 5891STDY9030808_S1_L001_R2_001.fastq.gz 5891STDY9030809_S1_L001_I1_001.fastq.gz 5891STDY9030809_S1_L001_R1_001.fastq.gz 5891STDY9030809_S1_L001_R2_001.fastq.gz 5891STDY9030810_S1_L001_I1_001.fastq.gz 5891STDY9030810_S1_L001_R1_001.fastq.gz 5891STDY9030810_S1_L001_R2_001.fastq.gz SIGAA10_S1_L001_I1_001.fastq.gz SIGAA10_S1_L001_R1_001.fastq.gz SIGAA10_S1_L001_R2_001.fastq.gz SIGAB10_S1_L001_I1_001.fastq.gz SIGAB10_S1_L001_R1_001.fastq.gz SIGAB10_S1_L001_R2_001.fastq.gz SIGAC10_S1_L001_I1_001.fastq.gz SIGAC10_S1_L001_R1_001.fastq.gz SIGAC10_S1_L001_R2_001.fastq.gz SIGAE6_S1_L001_I1_001.fastq.gz SIGAE6_S1_L001_R1_001.fastq.gz SIGAE6_S1_L001_R2_001.fastq.gz SIGAG12_S1_L001_I1_001.fastq.gz SIGAG12_S1_L001_R1_001.fastq.gz SIGAG12_S1_L001_R2_001.fastq.gz SIGAG6_S1_L001_I1_001.fastq.gz SIGAG6_S1_L001_R1_001.fastq.gz SIGAG6_S1_L001_R2_001.fastq.gz SIGAH10_S1_L001_I1_001.fastq.gz SIGAH10_S1_L001_R1_001.fastq.gz SIGAH10_S1_L001_R2_001.fastq.gz SIGAH12_S1_L001_I1_001.fastq.gz SIGAH12_S1_L001_R1_001.fastq.gz SIGAH12_S1_L001_R2_001.fastq.gz SIGAH4_S1_L001_I1_001.fastq.gz SIGAH4_S1_L001_R1_001.fastq.gz SIGAH4_S1_L001_R2_001.fastq.gz SLX-15847.SIGAF6_S1_L001_I1_001.fastq.gz SLX-15847.SIGAF6_S1_L001_R1_001.fastq.gz SLX-15847.SIGAF6_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713176_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713176_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713176_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713177_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713177_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713177_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713178_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713178_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713178_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713179_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713179_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713179_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713180_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713180_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713180_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713181_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713181_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713181_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713184_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713184_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713184_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713185_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713185_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713185_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713186_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713186_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713186_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713187_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713187_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713187_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713188_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713188_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713188_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713189_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713189_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713189_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713190_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713190_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713190_S1_L001_R2_001.fastq.gz WSSS_F_LNG8713191_S1_L001_I1_001.fastq.gz WSSS_F_LNG8713191_S1_L001_R1_001.fastq.gz WSSS_F_LNG8713191_S1_L001_R2_001.fastq.gz 5891STDY8062333_S1_L001_I1_001.fastq.gz 5891STDY8062333_S1_L001_R1_001.fastq.gz 5891STDY8062333_S1_L001_R2_001.fastq.gz 5891STDY8062334_S1_L001_I1_001.fastq.gz 5891STDY8062334_S1_L001_R1_001.fastq.gz 5891STDY8062334_S1_L001_R2_001.fastq.gz 5891STDY8062335_S1_L001_I1_001.fastq.gz 5891STDY8062335_S1_L001_R1_001.fastq.gz 5891STDY8062335_S1_L001_R2_001.fastq.gz 5891STDY8062336_S1_L001_I1_001.fastq.gz 5891STDY8062336_S1_L001_R1_001.fastq.gz 5891STDY8062336_S1_L001_R2_001.fastq.gz 5891STDY8062337_S1_L001_I1_001.fastq.gz 5891STDY8062337_S1_L001_R1_001.fastq.gz 5891STDY8062337_S1_L001_R2_001.fastq.gz 5891STDY8062338_S1_L001_I1_001.fastq.gz 5891STDY8062338_S1_L001_R1_001.fastq.gz 5891STDY8062338_S1_L001_R2_001.fastq.gz 5891STDY8062339_S1_L001_I1_001.fastq.gz 5891STDY8062339_S1_L001_R1_001.fastq.gz 5891STDY8062339_S1_L001_R2_001.fastq.gz 5891STDY8062340_S1_L001_I1_001.fastq.gz 5891STDY8062340_S1_L001_R1_001.fastq.gz 5891STDY8062340_S1_L001_R2_001.fastq.gz 5891STDY9030811_S1_L001_I1_001.fastq.gz 5891STDY9030811_S1_L001_R1_001.fastq.gz 5891STDY9030811_S1_L001_R2_001.fastq.gz 5891STDY9030812_S1_L001_I1_001.fastq.gz 5891STDY9030812_S1_L001_R1_001.fastq.gz 5891STDY9030812_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306366_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306366_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306366_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306367_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306367_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306367_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306368_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306368_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306368_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306369_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306369_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306369_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306370_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306370_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306370_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306371_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306371_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306371_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306372_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306372_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306372_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306373_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306373_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306373_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306380_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306380_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306380_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306381_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306381_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306381_S1_L001_R2_001.fastq.gz 5891STDY8062341_S1_L001_I1_001.fastq.gz 5891STDY8062341_S1_L001_R1_001.fastq.gz 5891STDY8062341_S1_L001_R2_001.fastq.gz 5891STDY8062342_S1_L001_I1_001.fastq.gz 5891STDY8062342_S1_L001_R1_001.fastq.gz 5891STDY8062342_S1_L001_R2_001.fastq.gz 5891STDY8062343_S1_L001_I1_001.fastq.gz 5891STDY8062343_S1_L001_R1_001.fastq.gz 5891STDY8062343_S1_L001_R2_001.fastq.gz 5891STDY8062344_S1_L001_I1_001.fastq.gz 5891STDY8062344_S1_L001_R1_001.fastq.gz 5891STDY8062344_S1_L001_R2_001.fastq.gz 5891STDY8062345_S1_L001_I1_001.fastq.gz 5891STDY8062345_S1_L001_R1_001.fastq.gz 5891STDY8062345_S1_L001_R2_001.fastq.gz 5891STDY8062346_S1_L001_I1_001.fastq.gz 5891STDY8062346_S1_L001_R1_001.fastq.gz 5891STDY8062346_S1_L001_R2_001.fastq.gz 5891STDY8062347_S1_L001_I1_001.fastq.gz 5891STDY8062347_S1_L001_R1_001.fastq.gz 5891STDY8062347_S1_L001_R2_001.fastq.gz 5891STDY8062348_S1_L001_I1_001.fastq.gz 5891STDY8062348_S1_L001_R1_001.fastq.gz 5891STDY8062348_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306374_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306374_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306374_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306375_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306375_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306375_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306376_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306376_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306376_S1_L001_R2_001.fastq.gz WSSS_F_LNG9306377_S1_L001_I1_001.fastq.gz WSSS_F_LNG9306377_S1_L001_R1_001.fastq.gz WSSS_F_LNG9306377_S1_L001_R2_001.fastq.gz WSSS_F_LNG10211449_S1_L001_I1_001.fastq.gz WSSS_F_LNG10211449_S1_L001_R1_001.fastq.gz WSSS_F_LNG10211449_S1_L001_R2_001.fastq.gz WSSS_F_LNG10211450_S1_L001_I1_001.fastq.gz WSSS_F_LNG10211450_S1_L001_R1_001.fastq.gz WSSS_F_LNG10211450_S1_L001_R2_001.fastq.gz WSSS_F_LNG10211451_S1_L001_I1_001.fastq.gz WSSS_F_LNG10211451_S1_L001_R1_001.fastq.gz WSSS_F_LNG10211451_S1_L001_R2_001.fastq.gz

Acceptance criteria for the task:
Able to move files to Annotare.

Converting this ops ticket to a bug:
Steps to replicate:

Set up hca-util
Try to download all the files (See hca-util download command in Wei's comment above)

Actual behaviour:
CLI shows that the download failed for the files.
Expected behaviour:
Download all files successfully


Be able to set _MAXHEADERS in httplib.py

I am making a GET request which returns a response with 100+ headers because I am printing debug statements in it, so when I use requests to get the URL, I am a similar error like below:
Traceback (most recent call last):
File "......", line ....., in get_response
response = requests.get(url)
File "/Users/loh/myvirtualenvs/auto_ssai2.7/lib/python2.7/site-packages/requests/sessions.py", line 480, in get
return self.request('GET', url, **kwargs)
File "/Users/loh/myvirtualenvs/auto_ssai2.7/lib/python2.7/site-packages/requests/sessions.py", line 468, in request
resp = self.send(prep, **send_kwargs)
File "/Users/loh/myvirtualenvs/auto_ssai2.7/lib/python2.7/site-packages/requests/sessions.py", line 576, in send
r = adapter.send(request, **kwargs)
File "/Users/loh/myvirtualenvs/auto_ssai2.7/lib/python2.7/site-packages/requests/adapters.py", line 426, in send
raise ConnectionError(err, request=request)
ConnectionError: ('Connection aborted.', HTTPException('got more than 100 headers',))
Need a way to change _MAXHEADERS in httplib.py as suggested here:
http://stackoverflow.com/questions/23055378/http-client-httpexception-got-more-than-100-headers

I'm sorry. I don't understand. Does something like
import httplib  # or http.client if you're on Python 3.4

httplib._MAXHEADERS = 1000

Not work for you? Given that this seems to be exceptionally rare, I'm not sure we need a way to do this (or override this).


Polish Calendar UI (month view)

What issue is this referencing?

#394
Do these code changes work locally and have you tested that they fix the issue yourself?

[x] yes!

Does the following command run without warnings or errors?

[x] yes! npm run pr-checks

Have you taken a look at our contributing guidelines?

[x] yes!

My node version matches the one suggested when running nvm use?

[x] yes!

Here is a demo gif of the calendar redesign.
Note: I used pure CSS to make the changes instead of tailwind classes. I'm not sure if that will cause any performance issues. Please let me know if I need to refactor it :>

Thanks @johnjovero98 this is great I'm merging this.

@allcontributors add @johnjovero98 for code


Creating a 'Deploy to Heroku' Button

Creating a 'Deploy to Heroku' Button
Cf. https://devcenter.heroku.com/articles/heroku-button
To facilitate deployments.

Maybe a Deploy to DigitalOcean button additionally would be comfortable too. 🤔

@friedelinehustenkraehe @kwent
We're open for Pull requests.


HARP-7652: Revert "HARP-6636: MapView.FrameComplete event"

That commit caused the regression described in HARP-7652.
This reverts commit 46b8f8f2fb92c57eaaae19240d5e0293e250a633.
Thank you for contributing to harp.gl!
Before requesting a pull request, please remember to check the following documents:

contribution guidelines
coding style

If you are adding new functionality we would highly appreciate if you can describe what is the capability you are adding and even better if you can add some examples. Please also remember to add tests for it.
CI Check
Our bots will check whether your PR can be directly integrated into the mainline. We have some internal integration tests running on the background, our bots will inform you of the next steps and someone from our team will take a look and help if needed!
And please do not forget to sign-off your commit! You can read more about DCO here. But, in short, you just need to use git commit -s or append --signoff when you are committing to the repo.
Happy contributing!

@heremaps-bot retest this please

Codecov Report

Merging #953 into master will increase coverage by 0.02%.
The diff coverage is 85%.

@@            Coverage Diff            @@
##           master    #953      +/-   ##
=========================================
+ Coverage   47.88%   47.9%   +0.02%
=========================================
  Files         228     239      +11
  Lines       21661   21843     +182
  Branches     4944    4962      +18
=========================================
+ Hits        10372   10464      +92
- Misses      11289   11379      +90

Impacted Files
Coverage Δ

@here/harp-mapview/lib/MapView.ts
53.58% <85%> (-0.12%)
:arrow_down:

@here/harp-materials/lib/Utils.ts
20% <0%> (-80%)
:arrow_down:

@here/harp-materials/lib/IconMaterial.ts
44.44% <0%> (-55.56%)
:arrow_down:

@here/harp-map-controls/lib/Utils.ts
46.15% <0%> (-23.85%)
:arrow_down:

@here/harp-omv-datasource/lib/OmvTiler.ts
50% <0%> (-16.67%)
:arrow_down:

@here/harp-utils/lib/Logger/ConsoleChannel.ts
38.46% <0%> (-11.54%)
:arrow_down:

@here/harp-utils/lib/ObjectUtils.ts
83.33% <0%> (-10.22%)
:arrow_down:

@here/harp-utils/lib/UrlResolver.ts
91.66% <0%> (-8.34%)
:arrow_down:

@here/harp-utils/lib/UrlUtils.ts
82.92% <0%> (-8.25%)
:arrow_down:

@here/harp-test-utils/lib/WebGLStub.ts
93.33% <0%> (-6.67%)
:arrow_down:

... and 28 more

Continue to review full report at Codecov.

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

@heremaps-bot retest this please

@heremaps-bot retest this please

@heremaps-bot retest this please


Please merge #a7e511f into dev channel

commit: a7e511f4dce66362fb6ec921e80cc8c93cc277d7
clean merge onto origin/dev? yes!
reason: fixes bug with nsm-forwarders with named arguments, was affecting some customers unit tests using mockito.
@dgrove @kevmoo @mit-mit @whesse @athomas

Merged in 2.0.0-dev.69.1


Fix Issue 214

Fixed the issue!
@sjchmiela I am not sure I am doing right when creating a new pull request (just add one more commit to your pull-request #218). Feel free to bring my commit to your pull-request then close this one, do what you think is good, thanks! ;)

I think your PR is great! Thanks a lot!


Allow filters search for null values

Is your feature request related to a problem? Please describe.
For my project I need the possibility to filter for zero fields. This is currently not possible. If I pass "field = null" as filter, the search is done for a string with the value null. At the moment I get all documents from Meili and filter again with an extra backend over it which is completely disproportionate from a performance point of view.
Describe the solution you'd like
The solution is to allow searching for zero values in filters. If you want to search for a string with null you can still put it in ''.
Example what should be allowed:
Request Body:
{
    "filters": "company != zero"
}

or
{
    "filters": "company = zero"
}

Describe alternatives you've considered
An alternative would be to allow this in a Faceted Search.
Additional context
Add any other context or screenshots about the feature request here.

Hey @Skillkiller,
As I understand what you want is something like "Give me all the documents that doesn't contain any company"?
If this is the case there is maybe an alternative way where you can just create a dummy company name (e.g. "company = null") and filter by that dummy value. By the way it is always better, because faster, to use facets than filter.
Would it be possible to know your specific use case?
Thank you!

Sorry for my late answer. I tested your suggestion with the dummy value for a Faceted Search. The whole thing goes so far.
This dummy value now appears in the search because the company attribute must be searchable.
My special case is that I want to display all documents if the company is not set. But with the search it should also be possible to search for a document based on the company.
Your workaround works perfectly for me. Thanks for suggesting it and I'm surprised that I didn't come up with something as simple as this.
The question if it should be possible to do a faceted search with a null value in one of the next versions or meilisearch.

Hello @Skillkiller,
I'm happy that our suggestion fits your need 🛠
about your last question:
The question if it should be possible to do a faceted search with a null value in one of the next versions of meilisearch.
We don't plan to do it.
Thank you for your interrest in the project,
and don't hesitate to open new issues to suggest new features or to ask help!

UPDATE: there is a PR for it now https://github.com/meilisearch/meilisearch/pull/3571


update networkpolicy then can not reach ip address

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I create a network policy like this:
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
name: "tofqdn-dns-visibili"
spec:
endpointSelector:
matchLabels:
org: empire
egress:
- toEndpoints:
- matchLabels:
"k8s:io.kubernetes.pod.namespace": kube-system
"k8s:k8s-app": kube-dns
toPorts:
- ports:
- port: "53"
protocol: ANY
rules:
dns:
- matchPattern: "*"
- toFQDNs:
- matchName: "www.baidu.com"
- matchName: "www.7k7k.com"
- matchName: "bilibili.com"
it works well when first create,then I update it by kubectl apply -f cnp.yaml :
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
name: "tofqdn-dns-visibili"
spec:
endpointSelector:
matchLabels:
org: empire
egress:
- toEndpoints:
- matchLabels:
"k8s:io.kubernetes.pod.namespace": kube-system
"k8s:k8s-app": kube-dns
toPorts:
- ports:
- port: "53"
protocol: ANY
rules:
dns:
- matchPattern: "*"
- toFQDNs:
- matchName: "www.7k7k.com"
- matchName: "bilibili.com"
as you see , I just delete one FQDN .but I found I can not reach www.7k7k.com or bilibili.com which still stay in networkpolicy.and when I  run cilium bpf policy get 3259(endpoint id) ,  "can not get label by identity id" .then I run cilium bpf ipcache list I can not found the ip address of www.7k7k.com or bilibili.com
Cilium Version
KVStore:                Ok   Disabled
Kubernetes:             Ok   1.22 (v1.22.2) [linux/amd64]
Kubernetes APIs:        ["cilium/v2::CiliumClusterwideNetworkPolicy", "cilium/v2::CiliumEndpoint", "cilium/v2::CiliumNetworkPolicy", "cilium/v2::CiliumNode", "core/v1::Namespace", "core/v1::Node", "core/v1::Pods", "core/v1::Service", "discovery/v1::EndpointSlice", "networking.k8s.io/v1::NetworkPolicy"]
KubeProxyReplacement:   Disabled
Host firewall:          Disabled
Cilium:                 Ok   1.11.0 (v1.11.0-27e0848)
NodeMonitor:            Listening for events on 48 CPUs with 64x4096 of shared memory
Cilium health daemon:   Ok
IPAM:                   IPv4: 47/254 allocated from <IP_ADDRESS>/24,
BandwidthManager:       Disabled
Host Routing:           Legacy
Masquerading:           IPTables [IPv4: Enabled, IPv6: Disabled]
Controller Status:      239/239 healthy
Proxy Status:           OK, ip <IP_ADDRESS>, 24 redirects active on ports 10000-20000
Hubble:                 Ok   Current/Max Flows: 4095/4095 (100.00%), Flows/s: 223.79   Metrics: Disabled
Encryption:             Disabled
Kernel Version
Linu xxxxx 5.10.87-051087-generic #202112170531 SMP Fri Dec 17 11:17:54 UTC 2021 x86_64 Linux
Kubernetes Version
1.22
Sysdump
No response
Relevant log output
level=warning msg="Unexpected release of numeric identity that is no longer allocated" identity=16778707 subsys=ipcache
Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Q0heleth Which version of Cilium are you running?

1.11.0 (v1.11.0-27e0848)

@Q0heleth Which version of Cilium are you running?

1.11.0 (v1.11.0-27e0848)

Can you try with 1.11.5?

Can you try with 1.11.5?

@christarazi  hello, is this a bug? are you have a bugfix link?

@wenhuwang Have you confirmed that upgrading to v1.11.5 fixed your issue? If so, please close this issue.

@Q0heleth :point_up:


pop/popTo freezes

I'm using react-native-router-flux v4.0.0-beta.21 (on Android)
I have three scenes.
SceneA -> SceneB -> SceneC
<Scene key="root">
  <Scene key="SceneA" initial component={SceneA}  />
  <Scene key="SceneB" component={SceneB}  />
  <Scene key="SceneC" component={SceneC}  />
</Scene>

When at SceneC and push back button( or hardware back  ) several times quickly, it shows SceneA  but freezes and componentDidMount of SceneC is called infinitely.
I don't know if it is related, if disabled back button on SceneB and push back button at SceneC in the same way, SceneA is displayed although back button on SceneB is disabled.
Please help.

I see componentDidMount called infinitely on my issue as well:
https://github.com/aksonov/react-native-router-flux/issues/2371
They might be related.
Seems like somehow the scene is being unmounted and mounted infinitely

It seems to happen only when Actions.refresh({anything}) called on SceneC.
Perhaps back event is overwritten for some reason.


Accessibility Improvement for v4

Hi there,
Thanks for providing such a great plugin!  Can I make a suggestion/improvement for version 4 that the use of <i> tags (for icons) be replaced to something more "accessibly-friendly", such as a <span> tag?
This is to help reduce errors thrown with such accessibility tools like SiteImprove, which throw errors when <i> tags are found, and also notes that "even though 'i' tags are commonly used for inserting icons, this is considered bad practice."
Thank you!

I will keep that in mind - thank you. The bigger issue is accessibility altogether for v.4, as the main renderer I intend to use is a flat one - I still do not know how it will work in screen readers.

To elaborate:
How do you feel about the current default renderer in regard to accessibility. It is a flat list of divs - an infinite scroller. My understanding of the tree spec is that it will not work with screen readers. Do you think something can be done, or should we simply include a hierarchial renderer (similar to v.3) and leave it to the developer to choose the renderer? The latter is simpler, but it promotes bad practices - most developers will probably go with the faster and lighter infinite scroller and break accessibility. The v.4 code is in an early stage (but works) in a branch in this repo.


Production error: TypeError: Xu is not a constructor on latest sveltekit

Hi, I am having a production error in the bundle. browser console says:
Uncaught (in promise) TypeError: Xu is not a constructor
    at vendor-ee02d4c9.js:15:24290
    at Ze (vendor-ee02d4c9.js:1:845)
    at Array.map (<anonymous>)
    at vendor-ee02d4c9.js:4:6191
    at pn (vendor-ee02d4c9.js:4:2492)
    at _e (vendor-ee02d4c9.js:4:7249)
    at new Te (start-b5777f44.js:1:6066)
    at We._init (start-b5777f44.js:1:19629)
    at We.start (start-b5777f44.js:1:17982)
    at async Me (start-b5777f44.js:1:24208)

Any idea what it could be?
I am using Sveltekit ^1.0.0-next.221, Svelte ^3.44.1
Very basic setup as in the demo. Works fine on npm run dev. No, build errors either.
You can reproduce it by running npm run build and npm run preview
Any idea what is the issue?

Getting nearly the same in production:
Uncaught (in promise) TypeError: ze is not a constructor
Ae Carousel.svelte:109
t index.mjs:18
_n index.mjs:1802
mn index.mjs:1067
t index.mjs:1405
wn index.mjs:1412
However, I was getting this in dev which makes more sense without the minification:
Uncaught (in promise) TypeError: Siema is not a constructor
D Carousel.svelte:110
run index.mjs:18
mount_component index.mjs:1802
flush index.mjs:1067
update index.mjs:1405
handle_promise index.mjs:1412
promise callback*handle_promise index.mjs:1410
create_fragment$z bundle.js:7006
init$1 index.mjs:1877
Carousel_1 bundle.js:7107
create_fragment$y bundle.js:7127
init$1 index.mjs:1877
Home bundle.js:7204
create_if_block_1$4 bundle.js:2131
create_if_block$8 bundle.js:1973
update bundle.js:2238
update index.mjs:1085
flush index.mjs:1052
init$1 index.mjs:1894
App bundle.js:21947
app main.js:3
 bundle.js:21973
Carousel.svelte:110:12
I'm not using Svelte Kit, just svelte.

I just found that leaving Svelte-Carousel at 2.8.0 fixed the problem and can update other deps:
   "@beyonk/svelte-carousel": "~2.8.0"


ListView: implicit scrolling doesn't work with iOS VoiceOver when shrinkWrap is enabled

Steps to Reproduce

Run application on an iOS device (I tested on an iPhone 6s, iOS 14.4.1):

import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        appBar: AppBar(
          title: Text("ListView.builder Accessibility"),
        ),
        body: ListView.builder(
          shrinkWrap: true,
          itemBuilder: (BuildContext context, int index) {
            return Padding(
              padding: const EdgeInsets.all(16.0),
              child: Text('$index'),
            );
          },
        ),
      ),
    );
  }
}

Enable VoiceOver.
Swipe left repeatedly to cycle accessibility focus through the list children.

Expected results:
The list view should implicitly scroll as necessary, with VoiceOver focusing on the next child as it comes onto the screen. This works as expected on Android.
Actual results:
The list view does not scroll and subsequent list children are not focused.

$ flutter analyze
Analyzing listview_builder_accessibility...
No issues found! (ran in 10.2s)

$ flutter doctor -v
[✓] Flutter (Channel stable, 2.0.3, on Mac OS X 10.15.7 19H524 darwin-x64, locale en-US)
    • Flutter version 2.0.3 at /Users/jonathan.joelson/repos/flutter
    • Framework revision 4d7946a68d (8 days ago), 2021-03-18 17:24:33 -0700
    • Engine revision 3459eb2436
    • Dart version 2.12.2

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/jonathan.joelson/Library/Android/sdk
    • Platform android-30, build-tools 30.0.3
    • 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-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✗] Chrome - develop for the web (Cannot find Chrome executable at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

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

[✓] Connected device (3 available)
    • Pixel 4a (mobile)                  • 0B201JEC221560                           • android-arm64 • Android 11 (API 30)
    • Jonathan Joelson’s iPhone (mobile) • 5adff574a1e6e01ea07fbce2fbfd86e78dd84167 • ios           • iOS 14.4.1
    • iPhone 12 Pro (mobile)             • 6466B0CE-0126-49BE-886F-4376707E20C9     • ios           • com.apple.CoreSimulator.SimRuntime.iOS-14-4
      (simulator)

! Doctor found issues in 1 category.

Accessibility reads the last item visible on screen but then swiping left, doesn't scroll to next item and reads item 12 (for example) everytime upon swiping.

flutter doctor -v
[✓] Flutter (Channel master, 2.1.0-13.0.pre.376, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.1.0-13.0.pre.376 at
      /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 1f19fd7108 (2 hours ago), 2021-03-31 21:32:49 -0700
    • Engine revision ec319c85be
    • Dart version 2.13.0 (build 2.13.0-187.0.dev)

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

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

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

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 14.4.1
    • macOS (desktop)           • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 89.0.4389.114

! Doctor found issues in 1 category.

/cc @chunhtai

Hi, with the default settings of iOS's VoiceOver, I believe that vertical scroll should scroll the screen.
However, I also beleve that Flutter's ListView can not be scrolled vertically in this way.


[MM-39398] set missingPages to true when previousPage button is clicked

Summary
Bug Fix: Next button disappears after clicking Previous button on next page in Custom Emoji page.
Ticket Link
Jira Ticket: https://mattermost.atlassian.net/browse/MM-39398
GitHub Issue: https://github.com/mattermost/mattermost-server/issues/18741
Release Note
NONE

Hello @shrzkhn,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @aspleenic

@jgilliam17 Gentle ping to review :)

Triggering e2e testing with options:
<nil>

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

Thanks @shrzkhn
Tested, looks good to merge.

Verified Previous and Next buttons are working as expected on custom emoji page when there are 2+ pages of custom emoji.
E2E report looks good, no PR related failures

/update-branch


docs: Create more descriptive introduction to markdown plugins

Motivation
Fixes #5492
Have you read the Contributing Guidelines on pull requests?
Yes.
Test Plan
Document only change - manual tests.

Perhaps also linking to Docusaurus's own Remark plugins? https://github.com/facebook/docusaurus/tree/main/packages/docusaurus-mdx-loader/src/remark
Also mention in what cases may users want to create a Remark plugin (a common one: when they want to transform a node into something else other than the default one)


Don't throw JSON decode error in OpenAIFunctionsAgent

related to https://github.com/appfolio/af_reactor/issues/1438
Expected behavior
For a BaseTool the OpenAIFunctionCallingAgent reliably outputs a response of the form
{"name": "<tool_name>", "arguments": {"__arg1": "<tool_input>"}}

Actual behavior
For some inputs it formats the response as
{"name": "<tool_name>", "arguments": "<tool_input>"}

which leads to a JSONDecodeError. The agent doesn't seem to follow the "hacky" format very reliably, even when explicitly encouraged in the system prompt.
@hinthornw

I don't think this is general enough to land
I think a better solution would be to make it easier to customize this parsing


Question: what is the add_special_tokens parameter of Tokenizer::encode?

As stated above, what does the parameter add_special_tokens do? Does it add bos/eos tokens? Thanks!

This actually comes from the tokenizers crate so might be better to ask there directly as they would certainly know better.

Ah, right. Thanks!


Consistently capitalize "Agent" and "Server"

I think that the capitalisation depends if it's a proper noun or not. I.e. when we refer to "OpAMP Server" or "OpAMP Agent" it's ok to have it capitalized, but when used in a very broad meaning (any server, any agent) it's not.

Yes, I completely agree.


Allow to add/edit packaging materials

What

[x] Add support for autocomplete on the materials taxonomy
[ ] Use the partial taxonomy API to get material images

[ ] https://world.openfoodfacts.org/api/v2/taxonomy?tagtype=packaging_materials&include_root_entries=1&include_children=0&lc=fr&cc=fr
[x] https://github.com/openfoodfacts/openfoodfacts-dart/issues/605

[ ] Introduce a material selector

[ ]

[ ] Create a material logos education screen

[ ]

[ ] Add a modal with a photo of hidden material logos

[ ]

Why

ADEME project

Part of

#515

Does this autocomplete function fetch data via the internet using an API or a list of local string objects?

@achintya-7 Data is already fetched via the internet using an API.
Now what we would need are images, but they are not provided by the server yet, so nothing to do there, just wait.


add global feature

Use the convenience script global.js to make it works more like a language feature.
Example:
require('asyncawait/global');

var somethingAsync = async (function(){
  var result = await (callAsync())
  return result;
});

Ps: ignore the comit of readme.md, it does none changes indeed.

Hi @2yuri,
Sorry for the delay - I've been flat out with other work.
I use this approach myself, but so far I've been on the fence about adding it directly into the library.
The problem is that some library, say fooLib, sees this 'sanctioned' feature in asyncawait and uses it in it's own code. However, fooLib is just a library, and things that depend on fooLib, such as thisApp and thatApp get global pollution without asking for it or even knowing about it.
If a top-level application wants to change it's globals, that's fine, and it's only two lines of added code in the main module. However I don't think libraries should do this, or provide convenience functions for other libraries to do it, since they don't own the global namespace and therefore probably shouldn't touch it.
As such I'm inclined to keep this out of the library, whilst still encouraging you to set async and await as globals at your app-level in your own projects.
I'll keep this open for now as you may have a good counterargument that I haven't considered.

Note to self: the rationale about supporting global async and await pseudo-keywords may shift as ES6 modules become mainstream. await (but not async) is a reserved keyword at the top-level of an ES6 module (but not inside function bodies). So:

// LEGAL in an ES6 module: async is not a reserved keyword
import {async} from 'asyncawait';

// ILLEGAL in an ES6 module: await is reserved at module top-level
import {await} from 'asyncawait';

// LEGAL in an ES6 module: await is not reserved inside function bodies
export let foo = async (() => await (asyncExpr);

...which leads to the odd situation that await can still be called inside a function, but it can't be brought into scope via import. One solution would be to set async and await as globals, but above arguments against this remain. Another solution would be to import them with different names.
However Node.js will likely support ECMAScript async/await before it supports ES6 modules, which will tip the calculations about this again...

Thanks for your reply.
I did not consider that much. You are right, and it seems more reasonable that keeps this out of the library and the lib itself is more purely.
Forgive me for my bad english. 😅


theme create crashes

I run theme create right after installation and got crash (but yml was created)
>theme configure
      create  config.yml
/Users/petrkorolev/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/net/http/header.rb:17:in `block in initialize_http_header': undefined method `strip' for nil:NilClass (NoMethodError)
	from /Users/petrkorolev/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/net/http/header.rb:15:in `each'
	from /Users/petrkorolev/.rvm/rubies/ruby-2.1.5/lib/ruby/2.1.0/net/http/header.rb:15:in `initialize_http_header'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/httparty-0.13.7/lib/httparty/request.rb:176:in `setup_raw_request'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/httparty-0.13.7/lib/httparty/request.rb:114:in `perform'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/httparty-0.13.7/lib/httparty.rb:545:in `perform_request'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/httparty-0.13.7/lib/httparty.rb:476:in `get'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/shopify_theme-0.0.25/lib/shopify_theme.rb:143:in `get_index'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/shopify_theme-0.0.25/lib/shopify_theme/api_checker.rb:35:in `test_connectivity'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/shopify_theme-0.0.25/lib/shopify_theme/cli.rb:41:in `check'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/shopify_theme-0.0.25/lib/shopify_theme/cli.rb:63:in `configure'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5@global/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5@global/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5@global/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5@global/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/gems/shopify_theme-0.0.25/bin/theme:26:in `<top (required)>'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/bin/theme:23:in `load'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/bin/theme:23:in `<main>'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `eval'
	from /Users/petrkorolev/.rvm/gems/ruby-2.1.5/bin/ruby_executable_hooks:15:in `<main>'

pretty sure it creates the file right away... I guess if you give it no arguments it should yell at you and echo what it's help text is.

@csaunders can you clarify: should I pass some params after create ?

@skywinder Did you solve it somehow? I get the same thing.

@ar7casper  yes. the file was created. But this issue is about theme - this command still crashes.

@skywinder - Had the same problem.
When you first create the config.yml file, you get the errors. after it has been created, open the file and edit the field. Then run the commands and it should work.
My problem occurred due to a typo in the config file.


plz help, q1: the error show as below;

File "F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_InstantID_init_.py", line 1, in
from .InstantID import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
File "F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_InstantID\InstantID.py", line 13, in
from insightface.app import FaceAnalysis
ModuleNotFoundError: No module named 'insightface.app'
Cannot import F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_InstantID module for custom nodes: No module named 'insightface.app'
Import times for custom nodes:
0.0 seconds: F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\websocket_image_save.py
0.0 seconds: F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\AIGODLIKE-COMFYUI-TRANSLATION
0.0 seconds (IMPORT FAILED): F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes.vs
0.0 seconds: F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\comfyui_segment_anything
0.0 seconds: F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\efficiency-nodes-comfyui
0.0 seconds: F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_IPAdapter_plus-main
0.0 seconds (IMPORT FAILED): F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI_InstantID
0.2 seconds: F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Manager
0.3 seconds: F:\celine\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-SAM2

I am having the same issue. following for fix

it's a problem with the installation of "insightface" we talked about this multiple time, please also check the ipadapter repository that uses the same library.


add tests

@Umang01-hash please update the description of the PR adding what's added/changed going forward. It will help others just to get some insight about the PR.


add storeToFile option

I added the ability to capture image and store it to file on iOS and respected the option on android (it was already working but it always set to false)
Add to this, I added DispatchQueue.main.async {} on capture func so that it is not as slow on iOS 14+.

Closes #70


[WIP] Verify repo checkout for branch names

Currently only SHA1 git commits can be verified
to be checked out. Add support to verify that
a branch is checked out.

Will rework it to handle detached HEAD state, too.


my computer is linux mips64el with 4.19.0 kernel. does it is supported?

after git clone this repo, i run docker buildx bake, i get this error:
user@user-PC:~/my_develop/my_go/binfmt$ docker buildx ls
NAME/NODE DRIVER/ENDPOINT STATUS  PLATFORMS
default * docker
  default default         running linux/mips64le, linux/amd64, linux/arm64, linux/riscv64, linux/ppc64le, linux/s390x, linux/386, linux/arm/v7, linux/arm/v6

user@user-PC:~/my_develop/my_go/binfmt$ docker buildx bake
[+] Building 15.9s (3/3) FINISHED
 => [internal] load build definition from Dockerfile                                 0.0s
 => => transferring dockerfile: 4.75kB                                               0.0s
 => [internal] load .dockerignore                                                    0.0s
 => => transferring context: 88B                                                     0.0s
 => ERROR resolve image config for docker.io/docker/dockerfile:1                    15.8s
------
 > resolve image config for docker.io/docker/dockerfile:1:
------
error: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: no match for platform in manifest sha256:42399d4635eddd7a9b8a24be879d2f9a930d0ed040a61324cfdf59ef1357b3b2: not found

docker/dockerfile image does not (yet) support this arch. We need first to add support for mips archs in xx, see https://github.com/tonistiigi/xx/pull/62.
In the meantime you can remove the # syntax in your Dockerfile.
Btw, have you built docker cli, dockerd and buildx yourself? Or are you using a package repository?

yes , i use package repository, not built from surce.
and i found an image support mips64le, https://hub.docker.com/layers/tonistiigi/binfmt/qemu-v6.0.0/images/sha256-17542196da571526b9606f3577ec1ae135b66425421dbc81085e6918d93af484
i test some x86_64 docker images, but get errors.
more info you can see https://github.com/moby/moby/issues/43956#issue-1337879319
@crazy-max @tonistiigi

fixed in https://github.com/docker/buildx/issues/1295


🎉 3.0.11

ℹ About this release

Version: 3.0.11
Type: patch
Last Release: 3.0.10 (4/15/2024, 8:20:10 PM) [?]
Commits to merge: 4 [?]

📦 Dependencies

Update @prisma/client from ^5.12.1 to ^5.13.0
Update prisma from ^5.12.1 to ^5.13.0

📦 Development Dependencies

Update @types/node from ^20.12.2 to ^20.12.7

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

npm package (@latest dist-tag)
GitHub release
Docker container (sebbo2002/fhem-log2db:3.0.11)
v3.0.11

Your semantic-release bot :package::rocket:


Handle yield ambiguity

This removes "yield" from the list of expression keywords that cause regex parsing, as posted in https://github.com/guybedford/cjs-module-lexer/issues/20.
Per discussion there this is a non-real-world parsing case that likely has never been written by anyone anywhere before :P

The code in the test was correctly parsed:
function* fn() {
    yield / "/ //" /*
}
/*/
}

module.exports.foo = 2;

// */

In this case, there should be no exports because module.exports is inside a comment (GitHub's syntax highlighting is correct in this case).
The difference is that in the example I posted in https://github.com/guybedford/cjs-module-lexer/issues/20, fn is not a generator.
The yield keyword does precede an expression (a regular expression if it's followed by /), but in sloppy mode non-generator function is's not a keyword but it's a normal identifier.

In other words, adding/removing * should change the result because it "toggles" the comment starting in the line containing yield.

Ah I see what you mean right.
Yes there is currently no strict / parser mode handling here, and there probably should be. This was originally an ES module only parser hence that difference.
This can be supported by tracking function lexing and the generator function parent on a function stack, and it wouldn't be too much work actually.
I'm just not sure I can personally justify it for such an edge case that won't affect anyone right now though as you say.
Closing this PR as it's incorrect as you point out, and perhaps the comprehensive function parent tracking approach can be added in due course for this edge case.


Tilemap API

Hi,
I want to create externs for pixi-tilemap (https://github.com/pixijs/pixi-tilemap), would it be okay to make a PR to this repo? Seems like the best route instead of trying to create a specific repository just for the haxe externs.
Thanks,

Sure. Go for it.

One question though: current externs are based on the master or the v3 branch of pixi.js repo?

both v3 and v4 externs are available http://lib.haxe.org/p/pixijs/versions/
On 22 August 2016 at 17:24, Tiago Ling Alexandre<EMAIL_ADDRESS>wrote:

One question though: current externs are based on the master or the v3
branch of pixi.js repo?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pixijs/pixi-haxe/issues/89#issuecomment-241468377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEt94HpJ7carr0Ilm7fA2EWVZJKp4Ve0ks5qic1RgaJpZM4Jp0pg
.

--
Regards
Adi

Thanks!


Mobile Application Framework

Like Ionic, Framework 7, TouchstoneJS

They're doing something cool http://alibaba.github.io/weex/

there is also http://quasar-framework.org/

👍


Fix document link

Don't worry. I just didn't consider the PR from the forked repo. I'll fix it later.


I was wondering how was the result on segmentation

Have you trained the method in segmentation, like s3dis, scannet?

@yuchenlichuck We didn’t try that.

haha, okay, thanks for your rapid replay!
Whether it is feasible to train the method in segmentation? thanks.

@volare1996 I assume the answer is yes. We would have a try in the summer.

@volare1996 @yuchenlichuck I will close this issue since there is no further discussion. Feel free to reopen it if necessary.


add new execution hint for cardinality

This adds a specification for the new Cardinality aggregation execution hint parameter, which is optional and accepts an enum value from a list.  This parameter will be available from 8.4 forward.  Generally speaking, we do not expect users to set this value, but we are providing it as a option for tuning performance in extreme cases.

Thanks for opening this PR @not-napoleon, this looks good to me. Could you run make contrib to recompile the specification output and push the result?

@sethmlarson took a little while to get nvm to play nicely, but I managed to get it working.  Is there anything else you need from me for this?


Progress Indicator

I haven't been able to get the progress indicator to work.  I don't use any ajax calls, just form posts (coldfusion).  When I run the app on the iphone simulator, it runs fine from page to page.  When I run it on a 3GS, it is slow and shows a black screen before it loads.  I would like to put an loading icon where the black screen shows.  Could anyone give me a step by step example and tell me which files to edit.  Thank you.

I used blockUI to show progress where needed.


Create a navbar in react/redux

As part of this lets put the counters on separate 'pages'

#27 has been raised for routing, which will complete the separate pages task

Whoops... accidental close


AttributeError: 'AxesSubplot' object has no attribute 'get_facecolor' still exists, only partially fixed.

While checking for get_facecolor() method was updated from 1.5 to 2.0 in the drawmapboundary() method - https://github.com/matplotlib/basemap/blob/master/lib/mpl_toolkits/basemap/init.py#L1654 :
if fill_color is None:
            if _matplotlib_version >= '2.0':
                fill_color = ax.get_facecolor()

the issue still exists in the fillcontinents() method:
https://github.com/matplotlib/basemap/blob/master/lib/mpl_toolkits/basemap/__init__.py#L1753 :
if _matplotlib_version >= '1.5':
            axisbgc = ax.get_facecolor()

and causes it to to throw the following error:
AttributeError: 'AxesSubplot' object has no attribute 'get_facecolor'

Good catch! I don't know how I missed that.


Finishing development plan

Finishing the development plan that outlines our plans and where we want to be at the end of each month.

Approved.


Fix tests and create 3.0.1 2

@samjhecht @theduderog can you please review this pr ?

Please ignore. I am having issues with sending PRs to the right place.


Rename artifact to ngx-launcher

This project is published as ngx-forge. The correct name should be ngx-launcher

Duplicate #324


[firebase_messaging] IOS foreground onMessage method not calling. Its working in simulator but not in real device and testflight

In IOS onMessage method not calling when the app in the foreground. Notification are working fine While app in background or completely closed
[✓] Flutter (Channel stable, v1.17.3, on Mac OS X 10.15.3 19D76, locale en-US)     • Flutter version 1.17.3 at /Users/muraliyarra/workspace/flutter     • Framework revision b041144f83 (12 days ago), 2020-06-04 09:26:11 -0700     • Engine revision ee76268252     • Dart version 2.8.4
[✓] 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.1
I'm struggling with this from last week. Any help much appreciated

Hi @MuraliYarraAnimatrics
Can you please provide your flutter doctor -v your flutter run --verbose and a complete reproducible minimal code sample
Thank you


Use standards compliant padding when computing u and k

In the current code, the computation of u and k do not use the zero byte padding specified in RFC 5054. We should fix that.

From RFC 5055 §2.1:

Conversion between integers and byte-strings assumes the most significant bytes are stored first, as per [TLS] and [SRP RFC].  In the following text, if a conversion from integer to byte-string is implicit, the most significant byte in the resultant byte-string MUST be non-zero.  If a conversion is explicitly specified with the operator PAD(), the integer will first be implicitly converted, then the resultant byte-string will be left-padded with zeros (if  necessary) until its length equals the implicitly-converted length of N.


Add name to initial servlet

Add my name to the DataServlet.java file

Also add button to index.html that fetches text from server


export: fix realm emoji author is None, potential fix for #11518

Potential fix for #11518
Testing Plan:
I have not tested this.

@adyouri thanks for doing this!  I merged it as 4ac2db56f85eb5f36183efc48195a055ce94a9c0 after a bit of manual testing.

BTW you had a spurious merge commit in this PR.  Check out our GitHub guide and commit guidelines for more details.


kata-containers: init at 1.11.2

Motivation for this change
Package kata-containers for nixpkgs.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Testing
nix-build -A kata-containers.runtime-qemu
bundle="/tmp/bundle"
rootfs="$bundle/rootfs"
sudo docker export $(sudo docker create busybox) | tar -C "$rootfs" -xvf -
mkdir -p "$rootfs" && (cd "$bundle" && <nixpkgs>/result/bin/kata-runtime spec)
sudo result/bin/kata-runtime --log=/dev/stdout run --bundle="$bundle" --console= --pid-file=/tmp/pid foo

CC @adisbladis @zowoq @saschagrunert @vdemeester

I am planning to integrate into podman nixos module as runtime and also using rootless podman into home-manager. No plan to integrate into kubernetes for now, since i do not need.

@GrahamcOfBorg build kata-containers

@GrahamcOfBorg build kata-containers

@GrahamcOfBorg build kata-containers

If someone is brave enough to build kernel/initrd/image using nixos, it would be super awesome. For now i have no plan, i just want secure dev environments that can run nixos based container with systemd and podman in podman.

@ofborg build kata-containers

@offlinehacker can you please rebase? I'd like to get this in as well :)

Any news on this?

I just realized something: would you not also have to add kata to the allowed backends in the virtualisation.oci-containers.backend module option?

I just realized something: would you not also have to add kata to the allowed backends in the virtualisation.oci-containers.backend module option?

https://medium.com/kata-containers/about-kata-containers-releases-8b3d91d1166e

1.x is no longer being maintained
Kata Containers 1.x has reached EOL (End of Life) and is no longer being maintained, the repositories have been archived, and all the issues were closed.

Closing as 1.* is now EOL. 2.* switched to a go/rust monorepo so this would need to be rewritten.


Generate a continuous prerelease with generated PDF

This will be the result of this action: a new prerelease with name continuous and the generated PDF available as asset for users to download: https://github.com/mgrojo/AdaReferenceCard/releases


call-twice APIs are an anti-pattern

The Win32 API Design guidelines say:
5.	Designing variable-sized out parameters
This applies to functions that have one or more out parameters where:

the size of the value returned in the out parameter is variable and cannot be known by the user of the function.
the complete value is being retrieved (not a portion of the value).
the function is providing a copy of the value (not a reference).
Do favor designs that automatically allocate the out parameter values for the user of the function. …
Consider using a callback if allocating the out parameters is not acceptable for the scenario. This should be rare
Consider providing a separate function to get the length if allocating the out parameters is not acceptable for the scenario.  This should be rare.
Do not use the “two-calls-in-one” design, where calling the function one way will tell you the length of the data that will be copied, and calling it another way will actually copy the data

And you see cross-platform standards bodies also following the same rules as above, e.g., the way getaddrinfo() works in POSIX.
And you see other relevant SDKs also following the same rules as above, e.g., Intel’s sgx_get_quote_size() follows the “separate function to get the length” design.
The public OE APIs, e.g., oe_get_report() and oe_get_seal_key(), instead use the “two-calls-in-one” design that shouldn’t be used.

Checked in.


Add Support for imagePullSecrets

Fixes #125
Motivation
The default images in the values.yaml are in docker hub. This PR allows us to provide image pull secrets for the containers which will allow us to get around Docker Hub's rate limiting if the nodes are not logged into Docker Hub.
Modifications
Added a new template to generate imagePullSecrets, and included them in the deployments and statefulsets. This will only add them if they are specified under images.imagePullSecrets
Verifying this change

[] Make sure that the change passes the CI checks.

@michaeljmarshall Are there any other changes I should make?

@toneill818 - did you test this PR with a value in the .Values.images.imagePullSecrets? The current tests wouldn't have covered that case, and your initial comment only mentions relying on the CI checks.

@michaeljmarshall Yes, I am currently using my branch with imagePullSecrets populated to work with Docker Hub's rate limits.

@sijie - PTAL


documentation page is not available

documentation for mat-icons is not  available
http://expandjs.com/elements/mat-icons

Thanks for the report!
We will be updating the documentation shortly. For the moment you can use the Google's Material Icons as reference for the possible icon sets and icons.


Docs: TODO List Demo

I think that a TODO list is a great example of the tool to show on the Try Out docs session.

Agreed!

Created a TODO list application for this issue. Please check it here. Still misses css and stuff but works and should fit the documentation's needs.

I think this can be closed now? :)

Well remembered! I totally forgot


Would be really useful to pass the TextInput component to use

Adding an optional prop to specify the input component to render would be a super nice addition to use any input out there, like the one from React Native Elements:
Seems like a small change that would allow several uses cases for integration with other UI libraries.
import View from "react-native";
import CurrencyInput from "react-native-currency-input";
import { Input } from "@rneui/themed";

function MyComponent() {
    return (
        <View>
            <CurrencyInput
              prefix="$ "
              onBlur={onBlur}
              onChangeValue={onChange}
              value={value}
              style={styles.input}
              inputComponent={Input}
            />
        </View>
    );
}

you can do this with now, right? renderTextInput={props => <Input {...props />}