Getting the device id

Hi,
How do I get the device id in index ?

You can use the cordova variable device to get it: device.uuid

Sorry to be a jerk but I'm now closing issues that don't follow the issue submission guidelines. This plugin takes a lot of work to maintain and I can't afford the time required to solicit the required info from everyone.
I'm closing this issue but please feel free to re-open the issue if you provide the requested details from the new issue submission guidelines.
https://github.com/phonegap/phonegap-plugin-push/blob/master/.github/ISSUE_TEMPLATE.md


how to generate multiple private keys and certifications in a shot time？

I want to generate multiple private keys and certifications in a shot time. It means it is not a good idea to generate one by one. I know it can share some processes or parameters to generate multiple private keys and certication. It can make the generation fastly.
But I donnot know how to progarm with openssl command. I can take some risks to reduce the secure because I use them to build socket connection to one streaming media server in same device.

marking as inactive, will be closed at the completion of 3.4 dev without further input


How to use redis sentinel with npm node_redis.

how to use redis sentinel with npm node_redis and socket.io-redis i.e. https://github.com/NodeRedis/node_redis i have to ensure high availability when master redis is down for any reason.

Here's the documentation on how to use Sentinel with ioredis: https://github.com/luin/ioredis#sentinel. For node_redis, there's a module for it though I haven't used it before: https://github.com/ortoo/node-redis-sentinel.

@luin thanks for the response but how can i pass it to redis connection configuration could not found any article on this how to use it with redis and socket.io-redis.
Waiting for your response.
Thanks


[design] Non-polling model?

In some situations a direct polling model may introduce challenges (such as rate limiting across a busy single organization). Is there an opinion on the design path for adding a different work-trigger method or even abstracting the current polling method?
For instance, if I wanted to develop a push model receiver or a queue driven workflow is that in line with the design intent here or would that go better into a separate operator (ex: jx-webhook-operator, jx-kafka-operator, etc..)?

the main reason we've not done a push model so far is to reduce the footprint of the git operator when using it in staging/pre-production/production clusters. e.g. to avoid needing to include Tekton or setup Ingress / Webhooks etc.
We should be able to add a jx admin boot or something like that - to effectively run the boot job whenever you like so if you know you want to run a boot job to just trigger it.
You can also configure the polling period to tone it right down if you are hitting rate limits.
BTW rate limits usually relate to git API calls rather than git pulls? e.g. we've never seen any git pull rate limits yet with github.com


Incorrect results with projected DTED

So i'm working with a projected DTED from issue #31. This was in Geographic WGS 1984, but is now in California State Plane Feet. The LLOS tool is running, and producing some results, but they are not correct. The lines are ALWAYS visible. The below graphic shows results from several runs on the surface, many of which have a LOT of intervening elevation changes that are much greater than the default 2 Meter observer offset could possibly account for. As you can see in the screenshot, all of the targets are visible from all of the observers.

If I use the LLOS GP Tool I get different results...

Looking at the profile graph of the top most line it looks like the results are legitimate:

I'm thinking this might be projection related. If I use the Geographic n36.dt1 surface with the GP tool the result are NULL points and lines, meaning there is no result produced.

@topowright from demo today, it apparently is.

Closing this issue based on the fact that i cannot replicate the issue.


from_template silently drops non-matching kwargs

As a user, it is surprising to me that I can add any argument to ModelCard.from_template only to have them silently being ignored if they don't match the template.
To reproduce, use the same code as in the README and add an arbitrary argument, e.g.
card = ModelCard.from_template(card_data=..., model_id=..., model_description=..., foo='123')
card.save(...)

The foo='123' part is silently dropped.
ping @adrinjalali @merveenoyan

What would be the expected behaviour for you?

I'd expect an exception with a message containing the keys which are not present in the template.

Yes, it's easy too easy to miss currently. And even if you know that only supported keys should be used, you could still make a typo and there would be no indication of anything being wrong. At the very least, there should be a warning.
That being said, I looked through the jinja2 docs and code and there seems to be no support from jinja2 in validating the keys.

I believe there are ways to locate the existing keys in a template then we can compare those against the provided template kwargs. Definitely something to look into

I believe there are ways to locate the existing keys in a template then we can compare those against the provided template kwargs. Definitely something to look into

That would be fantastic, let me know if you need help. Ideally, the validation could be provided in a separate method, so that 3rd party libraries can make use of it.


Eliminate hyperlinks to TF docs

It looks like we are emitting hyperlinks to TF docs. For instance, see this page:

The docker_image hyperlink goes to https://www.terraform.io/docs/providers/docker/r/image.html. Shouldn't it link to https://www.pulumi.com/docs/reference/pkg/docker/remoteimage/?
Interestingly, that resource page also links to TF docs!

@joeduffy I am working through this right now - I have managed this on a few resources so far - there is an issue in the home repo tracking this - ping me for more information if you need it

Ah got it, I'll close this as a dupe -- didn't know there was an existing issue.


Correction for raw affiliation Centre Hospitalier de Narbonne

Correction needed for raw affiliation Centre Hospitalier de Narbonne
raw_affiliation_name: Centre Hospitalier de Narbonne
new_rors:
previous_rors: 022m8c549
works_examples: W4200279750;W4223948974
contact: 1693c0fdc686ee510a42570297ea3f79:579b3b63c0d9dfdea89256d42d6288062923 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Allow for remote servers to connect to cluster

I was hoping you'd approve the ability to specify a specific broker cluster should a user need it.

Maybe a better way to do this is grab the broker cluster IP and host from the state-server but I have no idea how to do that.

@jon i can see how you wouldnt like this because it essentially hardcodes a server to one broker server instead of allowing the state server to dynamically assign a broker server but somewhere that is broken. Just go to aws spin up 3 servers and try it. I dont know scc well enough to track down where the state server is not sending the correct ip of a broker server. It is always <IP_ADDRESS> which doesnt work if the application server isnt on the same machine as the broker state server. I hope that makes sense. Thanks!

@jondubois Hey man, this is so the dev can specify a specific broker at start if they need it. One of the things I noticed is that the IP of the broker server is relative to the state server so if they are behind different availability zones on AWS then the IP that the app server sees is different than the IP broadcasted back to the state server. I think at some point, we need to pass from the broker server a different IP to the state server so that when it broadcasts the IP of the broker server to the app server it works behind say AWS' availability zones.

@happilymarrieddad I can't merge PR though because it doesn't account for the fact that there may be multiple back end broker servers. The logic logic in this repo is actually very complicated and desperately needs more comments to explain what is happening so it's a good attempt.
The uri passed here https://github.com/SocketCluster/sc-cluster-broker-client/pull/1/files#diff-93d530dd373561824113ae069f0bced6R30 comes from the state server (the state server sends this sc-cluster-broker-client a list of URIs for all brokers in our cluster) - The breakDownURI function will be called multiple times for each of those broker URIs (and again, there may be multiple of them).
The way SCC works is every backend scc-broker connects to the state server and reports their own instanceIp (IP address) - If an scc-roker doesn't report its instanceIp, then the state server will use the default remoteAddress for that scc-broker (which may or may not be suitable depending on the network infrastructure).
You can customize the ip address reported by the broker by setting an environment variable. See https://github.com/SocketCluster/sc-cluster-broker-server/blob/master/server.js#L8
If you look here: https://github.com/SocketCluster/sc-cluster-broker-server/blob/master/server.js#L88 - This is where the scc-broker reports its IP address to the state server (which the state server will then pass on to all sc instances in the cluster). If you look just a few lines above that, you can see where the instanceIp is being set here: https://github.com/SocketCluster/sc-cluster-broker-server/blob/master/server.js#L81

In the Kubernetes config file for the scc-broker, we pass a custom SCC_INSTANCE_IP environment variable which is the status.podIP provided by Kubernetes. https://github.com/SocketCluster/socketcluster/blob/master/kubernetes/scc-broker-deployment.yaml#L20-L23 so you'd have to do something similar when running it stand-alone (outside of K8s)

Thanks so much for taking the time to look at it!


re-organize examples and add a multi-function one

swith to 0.1.1
move examples in specific directories
add minimal readme
add multi-function example

my mistake, fixed and re-pushed.

👍  LGTM

can you merge, I can't

sure


Add .gitignore file

Description
Solves #35 by adding a .gitignore file to the project 😄

Thanks alot for you inputs!


[DOC-3561] Delegate release notes - move deprecation notices above latest

Delegate release notes - move deprecation notices above latest for FG and NG
For reviewers, previews are available.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


RFC: limit the number of stakeholders and managers to 20

Limiting them to 20 would allow us to use a multi() descriptor for both the deposit and CPFP descriptor, greatly simplifying the implementation of revaultd until bitcoind supports Miniscript.
This also gives more reasonable bounds to the configuration possibilities and allows for better testing of most setups.
I think we can reasonably assume that the first deployments won't have more than 20 stks or mans. But can we?

I think we don't yet have a use case in mind where it'd be necessary to have > 20. Also I don't think anyone is doing that in the industry? Largest I've seen is nunchuck's 6/7 of 11.
Even with a use case of always-online fully-automated managers, I can't see > 20 of them being used any time soon.
I think it's ok.

This was also the sentiment during the meeting, let's do it.


Persistent Storage

Right now,all data gathered via MQTT (and other sources) is stored in RAM, which means when the node gets restarted, it loses this. While data collected via the log parser can be regathered, MQTT data is lost.
This isn't a huge deal right now, but there are some other features I'd like to add where some persistence would be a good thing to have.
This could be achieved most easily by adding either a Redis cache (which can be configured to flush to disk) or another database engine.
Additionally, session cookie information is not persistent, meaning a restart forces users to log in again. Once again, this isn't so bad, but it would be easy to fix if some persistent store was available.

Redis cache in latest version


Export results does not work

When I try to download all results with Results -> Export Results -> All it starts the download and spins up a window calling "Working ... might take a while depending on your internet connection and the JATOS server ... please be patient. "  But it neither starts the download nor does it stops within any reasonable time frame.
The experiment has 1600 entries at the moment and all the results are roughly 20 MB together.
The following error shows up in the logs:
[ERROR] - a.s.i.ActorRefSource - Failing because buffer is full and overflowStrategy is: [Fail]

After restarting the server there is a short time window of roughly 5 minutes, where the data can be downlaoded. But afterwards the described behaviour from above reappears.
I set the upload size in the config file to 500 MB and set the heap size of the JVM to 4GB.
Any ideas?
(I do realised that I am running the server with OpenJDK 11, can this be the problem?)

Okay, I will add a property to change the cache size of the exports to the production.conf in the next release.
Going back to 3.5.10 won't change the export. The smaller cache size I introduced in version 3.5.9 - so back to 3.5.8 might bring something.

Another thought: Firefox doesn't implement the streaming API yet that JATOS is using to download the results. So it's using a polyfil but this doesn't provide all the features and uses a lot of memory and is slow. So in case you are using Firefox can you please try it with Chrome? A that can't cope with the amount of data in time can also cause the reported issue.

It shows different behaviour in Chrome and Firefox.
Firefox is presenting a file to download, but then no data is downloaded. The jatos backend website shows a spinning wheel with "Working".
In Chrome the download starts, but gets canceled at around 6 MB with a "Download failed (TypeError: network error)" error showing up in the jatos backend website. So maybe some values are set to low for the transfer used in Chrome. I am running jatos behind an nginx.

The error message "Failing because buffer is full ..." indicates that your server has a shortage in some resources, probably memory. Older JATOS version add to this problem in that all results are first loaded into memory and only then sent to the browser. I'd improved this in version 3.5.9. If you aren't yet on the newest version I'd recommend to update.

@kristian-lange  I'm commenting here because we're also having this problem with an older version of JATOS (3.3.3). In our case the studies with very large numbers of results will crash the JATOS GUI when the results pages load, which means we can't even export in batches via the GUI. We know that we need to upgrade JATOS ASAP. But we're not able to upgrade immediately and need to access the results, so as a short-term solution I'd like to try saving some study results to a file directly on the server.
So my question is: can you help me out with the MySQL query for selecting all of the results for a given study and saving that to a text file? Thanks!

Hi Becky,
The following command gives you the all result data from one component with ID, e.g. '123' (change 'jatosuser' and 'jatosdatabase'):
mysql -N -B -u jatosuser -p jatosdatabase -e "SELECT data FROM ComponentResult WHERE component_id = 123"

(For everyone who doesn't know where to find the component_id: You can find it in the GUI, in the study's page, in the table in column 'ID'.)
Of course if you have more than one component you have to do this command several times, once for each component ID.
The output is tab separated. If you want comma separated:
mysql -N -B -u jatosuser -p jatosdatabase -e "SELECT data FROM ComponentResult WHERE component_id = 123" | tr '\t' ','

Then additional to the data the experimenter usually needs some IDs to handle the data. With this command you get the component result ID, the study result ID and the component ID together with the data:
mysql -N -B -u jatosuser -p jatosdatabase -e "SELECT id, studyResult_id, component_id, data FROM ComponentResult WHERE component_id = 123" | tr '\t' ','

Thanks @kristian-lange, really appreciate the help!

Next release 3.6.1 will show error messages in case the export of results does not work. Hopefully this helps tracking down the reason for failed exports.


libssl.so.1.1: cannot open shared object file: Permission denied

After openssl installed on centos 6.10 on Oracle cloud,  enter the openssl in the ssh, it shows a message as "libssl.so.1.1: cannot open shared object file: Permission denied", but it works in root.

Can you figure out the permissions for that file?

I assume you installed openssl using the centos package manager (yum)? Or did you compile and install openssl yourself? Hopefully not the latter, because it is not a good idea to replace system libraries of your distribution with libraries built by yourself (unless you know what you are doing).
In either case, it is just a normal problem with linux file permissions. Probably the shared library file does not have the 'readable' bit set for 'others'. Try the following commands on your computer:
~$ which openssl
/usr/bin/openssl

~$ ldd $(which openssl)
        linux-vdso.so.1 =>  (0x00007ffff5f83000)
        libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f6f160c0000)
        libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f6f15c70000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6f158a0000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6f15680000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f6f16400000)

Now look for the full path of libssl.so.1.1.0 in the ldd output and do an ls -l to check ownership and file permissions. You should see something like -rw-r--r-- 1 root root at the beginning.
~$ ls -l /lib/x86_64-linux-gnu/libssl.so.1.1.0
-rw-r--r-- 1 root root 428384 Apr 18  2018 /lib/x86_64-linux-gnu/libssl.so.1.1.0

This is not an OpenSSL specific problem. Please ask a local linux expert if you need more help.

Can you figure out the permissions for that file?

You beat me be seconds again @levitte. But my reply was definitely much longer ;-).

I'm wondering if installing on Oracle cloud might have something to do with it...

Well, maybe I shouldn’t have closes the ticket immediately. Let’s wait for a reply from @mattjma first.

libssl.so.1.1 -> /usr/local/lib64/libssl.so.1.1, the last part blinks even has the 777 mod


Fixing the key prop warnings in the ui/applications and SMI Result

Description
This PR fixes #6252
Notes for Reviewers
I have tried to use uniqueID property wherever there are chances of dynamic rendering of content(Addition, Removal etc).
Signed commits

[x] Yes, I signed my commits.

Thanks @legendarykamal

Welcome @Abhishek-kumar09 🪐  😃


Check whether given port is in use before launching server (fixes #338)

@pdreiter Do you mind seeing if this produces a more reasonable error report for you?

From an informational perspective, looks good to me.


chore: disable trigger for all lts and hotfix branch

disable trigger for all lts and hotfix branch

/hold


ASP.NET Core web api antiforgery configuration is to working for separate spa project like angular cause cookies can't be shared accoss domain

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 47b14f57-82ac-a2e2-cbc7-22a81a60f4ac
Version Independent ID: bffca13c-223f-c61f-9cb2-9da8811eecfa
Content: Prevent Cross-Site Request Forgery (XSRF/CSRF) attacks in ASP.NET Core
Content Source: aspnetcore/security/anti-request-forgery.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @steve-smith
Microsoft Alias: riande

I suppose it is mentioned in the doc but not explicitly

Attacks that exploit trusted cookies between apps hosted on the same domain can be prevented by not sharing domains. When each app is hosted on its own domain, there is no implicit cookie trust relationship to exploit.

@Rick-Anderson any thoughts? Do we need to add any closure for this?

I think that's good. We can monitor this issue to see if we should reevaluate.


⚠ Bofrost.at has degraded performance

In dc132ee, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1978 ms

Resolved: Bofrost.at performance has improved in e379974 after 6 minutes.


fix: false positive yamllinter error

Yaml linter looks for any occurence of 'params.' substring in tekton scripts
However this help message matches, updating message to avoid false positive error as quick fix.

Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

also fixing in #1189

closing in favor of the linter fix


Subscribe / psubscribe hangs after calling sub.receive()

Hey, thanks very much for this project!
I've noticed that after a RedisSubscription.receive() loop has started, calls to subscribe or psubscribe never finish.
Here's the minimal repro:
const sub = await redis.subscribe(key)
sub.receive().next()
const sub2 = await redis.subscribe(key2)
// Never resolves

Sorry for the late reply. I believe this problem has been resolved in v0.32.1.


Add Custom Formatter System

Right now there is just one way to format everything and it does not make everybody happy. Also it makes it hard for us to change it without potentially breaking things. So I propose the following:

add a context setting to override a formatter class
that formatter has attributes and methods to customize how things are emitted
we have two classes for this: a default formatter that we keep improving and a legacy formatter that is as it looked like in click 5 which is super stable if you need a stable target

Things this would be used for:

usage rendering
wrapping of text
colorization flags
maximum width / minimum width of help output
indentation style of help
default value rendering etc.
error messages

Formatter class is an anti-pattern. Better export all settings as a tree and pass it to template engine.

@kx-chen and I were looking into this, and we've compiled our findings for what currently uses formatting as well as the requests that users have made over time: https://hackmd.io/9W3mAZv-TL-0DRVxghsoEw

After looking at the very helpful list of APIs from @amy-lei and browsing the source code, I might have some ideas on how a more central formatter could be structured. Though I am sure that there will be a lot of details to figure out...
One could have a central formatter class which would take the command itself and the context and arguments. This formatter could then have methods to generate usage and help messages when supplied with the command and context as arguments, practically replacing the Command.format_{} methods which have many hard-coded strings.
Similar formatters could exist for Option, handling Option.get_help_record and ParamType.get_missing_message, and exceptions, handling the ClickException.format_message method. In the latter case, the ClickException could only contain error information while formatting, with a default or user-defined formatter, is handled where the exception is caught in BaseCommand.main.
This approach would provide a clean separation between commands and output formatting and could even allow for localised strings in the CLI (this is quite common on macOS). However, it does require supporting new errors, parameter types, etc, explicitly in the formatter instead of just providing formatting methods on the classes themselves. This does potentially increase the burden of maintenance.
To conclude, I can understand why you'd want to keep things as is, with hard-coded section titles, indents, messages, etc.


[ALLUXIO-3362] Refactor inode metadata into InodeStore

https://alluxio.atlassian.net/browse/ALLUXIO-3362

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1232/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1238/
Test PASSed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1256/
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1282/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1283/
Test PASSed.


The PackageInstall CRD documentation is not up to date

The documentation in the Package Install Custom Resource has a TODO already done.
This particular instance is https://github.com/carvel-dev/kapp-controller/blob/6eb91df8648dda30cb919ec1d9e2add7781ceb3d/pkg/apis/packaging/v1alpha1/package_install.go#L102-L104.
But we should make sure that we go through the CRDs to see if there is another instance where we have TODOs that are no longer valid.

The PackageInstall CRD documentation also says status.packageRef exists, but no such type exists in the API.
# Populated by the controller
status:
  packageRef:
    # Kubernetes resource name of the package chosen against the constraints
    name: fluent-bit.tkg.vmware.com.v1.5.3

In this story, we want to make sure that we address both the code comments in the Package Install CRD and update the CRD spec that we manually created to be displayed on the website.


No stdint.h on OpenVMS.

No stdint.h on OpenVMS, it is inttypes.h instead, some projects use HAVE_STDINT_H.

Thanks, it's a simple enough change.
Just for my understanding : I'm surprised of this issue, because stdint.h is supposed to be part of the C99 standard library, and the test is supposed to check for C99 compliance.
Does that mean OpenVMS claims C99 compliance but does not provide stdint.h ?
Related : my understanding is that inttypes.h is a superset of stdint.h, which it is supposed to include. See https://en.wikibooks.org/wiki/C_Programming/C_Reference/inttypes.h :

The inttypes.h file is a C header file that is part of the C standard library and API. It was added with the 1999 version of the ISO C standard (known as C99). It includes the stdint.h header

Yes, the OpenVMS HP C compiler claims C99 compliance but stdint.h is not provided.
A mention in HP OpenVMS Systems, UNIX, Linux to OpenVMS Porting Guidelines:
http://h71000.www7.hp.com/portability/portingguidelines.html
4.1. Data Structures and Data types
  4.1.1.   int64_t and uint64_t
    In UNIX or Linux, int64_t and uint64_t data types are defined in the stdint.h, sys.h or types.h
    header files. However, in OpenVMS, these data types are defined in the inttypes.h header file.
    Hence, the header file inttypes.h must be included when porting to OpenVMS systems.

Some detailed discussion:
https://groups.google.com/d/msg/comp.os.vms/Bnh3tIOc7bo/flrc8d626WgJ

Craig A. Berry 12/24/14 Re: compiler language support
On 12/22/14 3:11 PM, John Reagan wrote:

On Monday, December 22, 2014 9:58:04 AM UTC-5, Stephen Hoffman wrote:

Interesting.   Haven't heard that one.   AFAIK, C99 was just something
that never made the list of stuff that got (completely) implemented and
shipped.

I haven't heard that either and I was there.  The compiler and RTL were under
the same management for years.

I no longer remember exactly how I came to this conclusion. Maybe it's
an impression I formed so long ago that it feels like a memory. I've
long tried to reconcile the repeated assertions by members of the
compiler team that the compiler is C99-compliant but the CRTL is not.
That's a complete non sequitur as far as the standard goes since the
standard governs the language, not the compiler nor the library by
itself, and I've never seen another implementation where the standards
compliance for the compiler was thought to be separate from the state of
the library.
And this isn't just being pedantic. When the compiler defines:
STDC_VERSION=199901L
but the library and headers don't implement everything mandatory from
C99, then various packages fail to compile because they test for C99 and
assume the required features are available. In some cases they have
perfectly adequate fall-back code that they don't make use of since
they've been told by the compiler that they don't need it.

The C99 headers would have been solely part of the C kit, after all.
Those headers are not shipped with VMS.

The library ships with the operating system. The headers are really part
of the library whether they ship with it or not.

And there are those C99
headers that are missing.   Ugh.  Now which C99 header is the one I'm
that always running into?   stdint.h?  Yeah.  stdint.h is missing.

Yeah, that one always surprises me.  stdint.h and fenv.h are both missing.
[fenv.h is an edge condition that we wouldn't support anyway.]

stdint.h is puzzling since most of it would be so easy to implement:
just a bunch of typedef statements based on built-in types.
inttypes.h is also missing a number of things required by the standard,
mostly format specifiers. It's not clear to me in this case what the
compiler knows, what the headers know, and what the relevant library
functions (scanf, printf, etc.) know.

Just FYI, gcc on OpenVMS will provide stdint.h from:
https://github.com/gcc-mirror/gcc/commit/e55b581dfa231b70aa01ea2b85758369f98386be#diff-b6372309633c7131af243fa2773f7f1b
https://gcc.gnu.org/ml/gcc-patches/2012-03/msg01133.html
(I am using the HP C compiler).
Thanks.

This issue can be solved by providing users with exotic compilers with an independent stdint.h header implementation. From my codebase:
//
// stdint.h:
//
// I'm no longer willing to define my own types for everything just because
// certain compilers refuse to supply even the most fundamental stuff.
// If someone wants to use my sourcecode, then that someone will have to keep
// up with me, not the other way around.
//
// Download an implementation for your compiler here:
//
//   C (portable, including MSC):
//     https://github.com/James-Jones/HLSLCrossCompiler/blob/master/include/pstdint.h
//
//   C (MSC only):
//     https://code.google.com/p/msinttypes/downloads/list
//
//   C++ (for old compilers):
//     http://www.boost.org/doc/libs/release/boost/cstdint.hpp
//
#include <stdint.h> // ***** see this header file for download locations *****


fix: merge control markdown with json (#1528)

Types of changes

[ ] Hot fix (emergency fix and release)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation (change which affects the documentation site)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Release (develop -> main)

Quality assurance (all should be covered).

[x] My code follows the code style of this project.
[x] Documentation for my change is up to date?
[x] My PR meets testing requirements.
[x] All new and existing tests passed.
[x] All commits are signed-off.

Summary
Key links:

Sonar coverage

Before you merge

Ensure it is a 'squash commit' if not a release.
Ensure CI is currently passing
Check sonar. If you are working for a fork a maintainer will reach out, if required.

In Python, __file__ is a special built-in variable that represents the path to the current script file. I still struggle with why we want to change?

We discussed the unit test updates in Slack, and I am making a separate PR with them.


fix, Log command outputs into the repository logs as well

@zimmski LGTM... cannot review so please feel free to review yourself and merge xD


Add addon OPA Gatekeepr

OPA Gatekeepr is often required in Enterprise K8s deployment to:

apply preventative controls
auditing
Gatekeeper

PR is in progress. https://github.com/aws-quickstart/ssp-amazon-eks/pull/147
Closing this ticket.


STORM-350: Upgrade to newer version of disruptor

This upgrades to version 3.3.2 of the Disruptor Queue.  There have been questions about stability in the past, and also out of order delivery.
I really wanted to be sure that everything would be about the same.  I ran the DisruptorQueue related unit tests over the weekend and got no failures at all, with well over 10,000 runs.
I did some performance tests too using the FastWordCountTopology I added as a part of this.  I ran 5 times with the original 0.11.0-SNAPSHOT this is based off of (e85921035fa9bb59d25f0347dc6d26002aac9fab) and with this branch.  By setting the topology.max.spout.pending to 200 I got essentially identical results.  The new Queue was slightly faster but it was small enough it could just be noise.
Similarly when I did not set topology.max.spout.pending and relied on the automatic throttling I got very similar numbers, although the variance between the runs was much higher so having a real comparison there is much more difficult.
@HeartSaVioR in the past you did some testing to see if out of order delivery was happening, I would love it if you could take a look at this patch and test it similarly.
Anecdotally I have seen this version behave better than the current one we are using.  I have seen no NPEs from tuples disappearing and I have seen that show up in some of my stress testing using the old queue.  Again I don't know how often this happens so I cannot guarantee that it was a disruptor bug.

The travis failure looks unrelated.  I think we need to fix how we do ports with the DRPC test.  It seems that every so often we cannot bind to the port we want.

@revans2
Patch looks good overall.
I'll run performance test and see there's no failed tuple. If it doesn't show failed tuples I think we're safe to merge.

+1 LGTM

@revans2
I ran performance test from small cluster (three machines, each one has zookeeper and supervisor, and only one has zookeeper, nimbus, supervisor) with configuration below,

com.yahoo.storm.perftest.Main --ack --bolt 4 --name test -l 1 -n 1 --workers 4 --spout 3 --testTimeSec 900 -c topology.max.spout.pending=1092 --messageSize 10

Unfortunately I'm seeing failed tuples again.

I packaged perf test with 0.10.0-rc of storm-core, but I think it doesn't matter cause its scope is provided.
I still don't know why this happens. According to log files, there's no Netty connection issue.
Could you test it too?

@HeartSaVioR I figured out the failed tuples and will be pushing a new patch shortly.  This is the same null issue we were seeing previously.  Just with the newer disruptor it exacerbates the two issues.
First MutableObject is not synchronized so it is possible for the data to not be flushed to memory and if the receiver thread is on a different core you can get a null out.
Additionally I noticed that the non-bocking receive seems to not be putting the correct barriers in place, and the polling can try to read a MutableObject that has not been updated yet, and is still set to null.  The only way I could find to fix it was to implement it in terms of the blocking call.  From my performance tests I did not see any impact from these changes.

I pushed the fix, please try again.

@revans2
Seems like it doesn't resolve the failed tuples. First time I can't see failed tuple, but at second trial it appears.

@HeartSaVioR can you share the topology that you are running so I can try and reproduce/debug it locally.

@HeartSaVioR
I added an in-order test case that I ran for over 50 mins on both Linux and my Mac and they both passed with no errors and each processed over 35 million tuples.  Any help you could give me in reproducing the failures would be greatly appreciated.

@revans2
I mailed you to attach jar file. If you can't receive it, I'll find another way to share. (via dropbox?)

@HeartSaVioR Oh you are using my perftest https://github.com/yahoo/storm-perf-test.  I will try it out and see if there are any failures.

@HeartSaVioR I ran a number of tests, and I am fairly sure that what you are seeing is a failure in the messaging layer and not disruptor.  I limited the number of workers to just 1 so that I would be sure to isolate things.
storm jar storm_perf_test.jar com.yahoo.storm.perftest.Main --ack --ackers 8 --bolt 8 --maxPending 200 --workers 1 --spout 8 --testTime 8000 --pollFreq 30
I didn't run for the full 8000 seconds, but part way through I got this screen shot.

I hope 185 million tuples from this test plus the 35 million tuples from my in-order test all with no failures is enough to convince you that the new disruptor queue is solid.  If you want me to try and debug the messaging layer and try to reproduce the failures you saw I am fine with that, but I would like to do it as a part of another JIRA.

@revans2
It just dropped throughput when tuples are being failed.
It occurred nearly end of performance test, so I'd like to test it again with longer test duration.
If it occurs nearly end of performance test again, I also treat it to other issue, maybe transfer issue while worker shutdown.

@HeartSaVioR we started doing some stress/load testing on 0.10 + this patch and ran into the NPE issue.  I am going to close this pull request until the NPE can be resolved, but it looks like it is something with disruptor itself.  The exact same code but with the version of disruptor reverted back saw no issues.
I will also update my batching pull request #765 to be based off of the original version of the disruptor queue.


Setup OK; Deploy OK; But can't access app

Hi, I'm trying to deploy my app to DigitalOcean in a droplet using Ubuntu 16.04.
mup setup and mup deploy ran ok.
In my droplet docker seems good(to me):
CONTAINER ID        IMAGE                  COMMAND                  CREATED             STATUS              PORTS                        NAMES
c97df00753d6        abernix/meteord:base   "/bin/sh -c 'bash $ME"   14 hours ago        Up 14 hours         <IP_ADDRESS>:80->80/tcp           Geekble
8f4cb27bf786        mongo                  "/entrypoint.sh mongo"   18 hours ago        Up 18 hours         <IP_ADDRESS>:27017->27017/tcp   mongodb

But when I try to access my app through the browser (w/ URL or IP), I get nothing but the 'can't access' warning. And when I try with curl the return is Failed to connect (...): Connection refused.
with mup logs -f the end of log is:
=> Starting meteor app on port:80
Note: you are using a pure-JavaScript implementation of bcrypt.
While this implementation will work correctly, it is known to be
approximately three times slower than the native implementation.
In order to use the native implementation instead, run
meteor npm install --save bcrypt
in the root directory of your application.

This is my mup.js
module.exports = {
  servers: {
    one: {
      host: 'xxx.xxx.xx.xx',
      username: 'root',
      // pem:
      password: 'xxxxxxx',
      // or leave blank for authenticate from ssh-agent
    }
  },

  meteor: {
    name: 'Geekble',
    path: '../',
    servers: {
      one: {}
    },
    buildOptions: {
      serverOnly: true,
    },
    env: {
      ROOT_URL: 'http://xxxxxx.com/',
      MONGO_URL: 'mongodb://localhost/meteor'
    },

    //dockerImage: 'kadirahq/meteord',
    dockerImage: 'abernix/meteord:base',
    deployCheckWaitTime: 60
  },

  mongo: {
    oplog: true,
    port: 27017,
    servers: {
      one: {},
    },
  },
};

I would appreciate some help! Thank you guys!

'Fix it'.
I don't know why but I deploy my app again, and stop and start my container manually and it runs.
Is crazy as it sounds.

I have the exact same issue. any additional feedbacks you could add to troubleshoot this ?
my config is almost the same: ubuntu 16 and:
module.exports = {
  servers: {
    one: {
      host: 'xxx.xxx.xxx.xxx',
      username: 'xxxx',
      pem:'/Users/xxxx/.ssh/xxx,
    }
  },

  meteor: {
    name: 'todos',
    path: '/Users/xxx/projectname',
    servers: {
      one: {}
    },
    buildOptions: {
      serverOnly: true,
    },
    env: {
      ROOT_URL: 'http://websitename.com',
      MONGO_URL: 'mongodb://localhost/meteor',
    },

    dockerImage: 'abernix/meteord:base',
    deployCheckWaitTime: 120
  },

  mongo: {
    oplog: true,
    port: 27017,
    servers: {
      one: {},
    },
  },
};

Hi @guillim!
It wasn't me who created the droplet and it was gave to me with LAMP and a little trouble which was that the DNS pointing to wrong IP.
LAMP was not a big challenge, I just turned Apache off.
About the DNS it's confusing because I always tested the connection with the URL and IP without success.
After my last test I noticed that accessing IP returned ok, but the URL did not, so I found that the pointing was wrong.
But just before I was about to put docker to another port (3000) and use Nginx to link :80 to that, I was just trying to turn the app on anyway.
So while doing that I changed the container port from 80->80 to 3000->80 and then put 3000->80 to 80->80 back. I don't know why but when I returned to 80->80, it worked ok.
I hope this can help you anyway.

Tks for your response.
I had actually an issue on a forced redirection from https to http that an underlaying package was doing. It is commented on the issue i opened and closed afterwards. (attached to this issue BTW)


Russian Support

Russian completed but still not in app. Why?

It'll be in the app in the next release 2.3.0, if it is completed.

Russian language is included in version 2.3.0-Beta1. Let me know if there's anything I can do!

Thank you very much for adding Russian language support in 2.3.0-b1. is there anything we can do with
"planned" button? In Russian, maybe, we need to replace "Запланировано" with "В планах" to keep more short but synonym werb.

Thank you for your work bringing Russian support to Noto :)
You don't have to imitate the exact word. You can change the word however you want, as long as it has a similar meaning.

Also, did I mention you correctly in the app?

Absolutely correct mentioned. I updated some strings on crowdin, maybe there's needed to include them to new build.

No worries. I'll include them in the next beta!


Translation files are not copied to build folder

Package version
2.0.0
Describe the bug
Installed and configured i18n.
npm i @adonisjs/i18n
node ace configure @adonisjs/i18n

Created language file resources/lang/en/crud.json and used it. Everything works fine while running in dev mode.
When I build the app using npm run build, it does not copy the resources/lang folder to build. Note that I am not using edge views, so resources only has lang folder.
I am copying it separately after build for now.
Reproduction repo
No response

Hey @jaysson! 👋🏻
Thanks for the feedback! It should have been automatically added to the metaFiles key in the adonisrc.ts file.
In the meanwhile, you can add them by hand:
{
  metaFiles: [
  // ...
    {
      pattern: 'resources/lang/**/*.json',
      reloadServer: false
    }
  ]
}

📚 https://docs.adonisjs.com/guides/adonisrc-file#metafile

That was quick! Awesome job @RomainLanz!


Dynamic style change on Callouts not working properly

Is this a bug report?
Yes
Have you read the Installation Instructions?
Yes
Environment
  "dependencies": {
    "react": "16.2.0",
    "react-native": "https://github.com/expo/react-native/archive/sdk-25.0.0.tar.gz",
    "react-native-maps": "^0.20.1"
  }

Steps to Reproduce
I'm trying to change width of my marker callout when state changes, using react native animation. However when the state changes, callout style still remains the same.
Workaround I found was to set tooltip={true} however this will break the callout image (Instead of the default text bubble shape, it'll just be transparent).
Expected Behavior
Style on callout will change as state changes.
Actual Behavior

The width will remain the same like above screenshot even though the code is set to dynamically change width.

This is the callout when tooltip={true} is applied, it is showing the width I want however the background text bubble image is gone.
Reproducible Demo
    render() {
        return (
            <MapView.Marker image={markerImage} onPress={e => {e.stopPropagation(); this.onMarkerPress(this.props.bayID)}} coordinate={ this.props.coordinate } tracksViewChanges={this.state.tracksViewChanges}>
                <MapView.Callout style={[{ flex: -1, position: 'absolute' }, this.state.isLoaded && { flex: -1, position: 'absolute', width: 220 }]}> //<- CHANGING WIDTH DOESN'T WORK
                    {this.state.isLoaded ?
                    <View>
                        <Text>{this.state.descriptions.description1}</Text>
                        <Text>{this.state.descriptions.description2}</Text>
                        {this.state.descriptions.description3 ? <Text>{this.state.descriptions.description3}</Text> : null}
                    </View>
                    :
                    <ActivityIndicator size="large" />
                    }

                </MapView.Callout>
            </MapView.Marker>
        )
    }

Closing as tracksViewChanges works fine now. Please open a new issue if you still find this

Hi minotaurrr! I hope you were able to fix your issue. I was wondering how you were able to remove the padded borders from the call out from your image in the "actual behavior." What styling did you use?
Thanks!


[feature request] support yurtadm init command based on sealer

What would you like to be added:
OpenYurt is an open-source project in the field of cloud-native computing that enables the extension of Kubernetes clusters to edge devices. However, currently, the OpenYurt cluster can only be installed manually, and we lack a unified installation method for quick and convenient deployment of a high-availability OpenYurt cluster. The Sealer project provides a new approach to delivering distributed applications by packaging the Kubernetes cluster and all application dependencies into a single Sealer Image, reducing deployment difficulty and complexity.
There have been some progress in the 2022 ASOC, which can be viewed here. However, the implementation is not yet quite refined. For example, the generation of Sealer Image has not been integrated into Openyurt's CI process, and the maintenance of the implemented yurtadm init command has been abandoned. Therefore, we need to take up this task anew.
Why is this needed:
This feature has the potential to greatly enhance the user-friendliness of Openyurt.
others
/kind feature

@YTGhost As we discussed in the community meeting, yurtadm init command will not be supported in the OpenYurt. and yurtadm init command has been removed in the #1537 . so i will close this issue.


(#398) Add blank credits screen

You have to press i to open credits.

@kolumb thanks for the PR! I'm gonna review it on the next Nothing Stream.

@kolumb looks good to me! :+1: Thank you very much for the PR!


No useful developer information.

Is it 0 (read zero) or 1 based array. What index is the first element???
That is the information that is needed on this page.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 48f5c8ec-fa98-7869-bcb7-7b55feb4aef4
Version Independent ID: 069473b9-c74f-60f7-a090-ba747f0daf39
Content: JsonArray.Get(Integer, var JsonToken) Method - Business Central
Content Source: dev-itpro/developer/methods-auto/jsonarray/jsonarray-get-method.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for the feedback. The array is 0-based, which is by design because these methods are wrappers. Other arrays in AL are 1-based. We will update the docs specifically for the JsonArray data type. Thanks.

Closing this issue. Update for the next doc refresh.


Add resource quotas

Take into account quotas on resources
Increase the polling interval of drones to 60s

Codecov Report

Merging #19 into master will increase coverage by 0.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master      #19      +/-   ##
==========================================
+ Coverage   83.45%   83.46%   +0.01%
==========================================
  Files          37       37
  Lines        1227     1228       +1
==========================================
+ Hits         1024     1025       +1
  Misses        203      203

Impacted Files
Coverage Δ

tardis/resources/drone.py
47.61% <0%> (ø)
:arrow_up:

tardis/resources/poolfactory.py
56.25% <100%> (+0.93%)
:arrow_up:

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 64358ed...278d1dc. Read the comment docs.


replication guarantee / auto replication

Masters should automatically maintain replication level.
For example, with replication 001 and two volume servers, I'm adding a third volume server then stopping a second one yet no automatic replication is happening to ensure safety of data.

The automatic rebalancing will be problematic in large clusters. It can cause unexpected busy network activities, for example, the heartbeat may come and go, causing unnecessary busy system. Current recommended strategy is to keep existing data readonly, and automatically add new writable volumes.
There are volume.balance and volume.fix.replication commands in weed shell. You can configure them to run during off hours.
Will add them to the wiki.

Auto healing is absolutely necessary in large cluster. Please reopen.
It is easy to implement automatic periodic execution of such maintenance commands for example after configurable delay since volume disappearance.
Storage admin should not have to script essential maintenance operations that should be completely transparent and automatic.
Have a look how it is implemented in MooseFS and LizardFS please.

Also volume.fix.replication does not even work:
$ ./weed shell
> volume.fix.replication
replicating volume 3 001 from <IP_ADDRESS>:9334 to dataNode <IP_ADDRESS>:9334 ...
error: rpc error: code = Unknown desc = failed to copy /mnt/NVMe/weed/data/3.dat file: receiving /mnt/NVMe/weed/data/3.dat: rpc error: code = Internal desc = unexpected EOF

See #1268 for details about volumes replication.


Implementation of hiccup.page

See hiccup.page

[ ] html4
[ ] xhtml
[ ] html5
[ ] include-js
[ ] include-css

4d22742


NotFoundHandler is not invokable

Method process should be used instead.

Thanks, @webimpress; nice catch!


Failed to patch the osx installer

Describe the bug
The error occurred at this step (Patching OSX Installer). After i pressed Install button, it finally shows an Installation Failed warning.
Expected behavior
The installer completes without error.
Environment:

Running OSX version: 10.14.6
Target drive OSX version: 10.14.6 (Installer)
HaC Mini installer version: v2.1

Additional context
The USB media I've used to create the installer is a bridged mSATA SSD. I do not have a USB stick drive currently, and I will try it later.
Update: Patching the installer on a USB stick drive also has failed.
Logs
24-Sep-2019.txt

I've found that even if the UI shows me a failure, the installer has been patched.


More than 3 roles being created with postgresql flex server

Hello
When I created postgesql flex serer I see below list of roles being created. Documentation says only 3 roles.
"azuresu"
"pg_database_owner"
"pg_read_all_data"
"pg_write_all_data"
"pg_monitor"
"pg_read_all_settings"
"pg_read_all_stats"
"pg_stat_scan_tables"
"pg_read_server_files"
"pg_write_server_files"
"pg_execute_server_program"
"pg_signal_backend"
"pg_checkpoint"
"azure_pg_admin"
"replication"
"pgadmin"
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: aa11a8d3-7c20-0351-c289-6b47dbcebd86
Version Independent ID: 373f7ccb-fd4a-84bb-22f7-693984cb072e
Content: Security in Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/concepts-security.md
Service: postgresql
Sub-service: flexible-server
GitHub Login: @GennadNY
Microsoft Alias: gennadyk

@ravick4u
Thanks for your feedback! We will investigate and update as appropriate.

@ravick4u - rest of the roles are Postgres built-in roles, not unique for Azure Postgres Flex

#please-close


ES6 support

When duktape can support ES6

That's a gradual process and features are implemented piece by piece; there are a lot of individual issues tracking ES6 features (see label es2015).


Dotnet exporters update 2

This PR brings .NET exporters page in line with Java, Js, Python, C++
It also adds some base setup for metrics & logs, and renames the "config" page under automatic to "configuration" since this is an assumption made by one of the shortcodes

@cijothomas PTAL!


Use current branch instead of fixed branch

Is it somehow possible to use the current branch instead of a fixed one? ->
"openInGitHub.remote.branch": "master", // Name of the remote branch
Maybe only use the specified branch if the current doesn't exist on Github.

Just saw it in the README... Sorry

Reading this issues I was thinking "yeah, that's how it should work, why didn't I code it this way?", glad to hear that I actually did 😄


Move example sketches to appropriately named folders

The Arduino IDE requires the sketch folder name to match the filename of the primary sketch file. This change causes the example sketch to be accessible via the Arduino IDE's File > Examples > LIBRARYNAME menu after the library is installed.
Reference:
https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5:-Library-specification#library-examples

thanks @per1234 . merged!


Bug: Incorretly raised ImproperlyConfiguredException for sub-paths with a path-type parameter

Describe the bug
As described by @rgajason in https://github.com/starlite-api/starlite/discussions/825#discussioncomment-4221738, when using the path type for a path parameter, an ImproperlyConfiguredException will be raised, where a str type parameter would be accepted.
To Reproduce
from pathlib import Path

from starlite import Starlite, post, put

@post(path="/{string:str}")
def post_endpoint(string: str) -> None:
    pass

@put(path="/{string:str}/{path:str}")
def put_endpoint(string: str, path: Path) -> None:
    pass

app = Starlite(route_handlers=[post_endpoint, put_endpoint])

This works
from starlite import Starlite, post, put

@post(path="/{string:str}")
def post_endpoint(string: str) -> None:
    pass

@put(path="/{string:str}/{path:str}")
def put_endpoint(string: str, path: str) -> None:
    pass

app = Starlite(route_handlers=[post_endpoint, put_endpoint])

@Goldziher @peterschutt Probably one of you should take a look at this


Commit Version, Subversion, ProtoVersion, RelayFee RPC

Commit Version, SubVersion, Protocol Version and RelayFee commands in electrum using bitcoind.
Also split out bitcoind into its own class

sorry for the conflicts.
two issues:

do not call bitcoind on each request; better cache the result, as I did for relayfee
do not mix tabs and spaces, it creates syntax errors

Thanks Tom will get it fixed as soon as I get my copy of electrum back up
Sent from my iPhone

On 1 Feb 2016, at 05:19, ThomasV<EMAIL_ADDRESS>wrote:
sorry for the conflicts.
two issues:
do not call bitcoind on each request; better cache the result, as I did for relayfee
do not mix tabs and spaces, it creates syntax errors
—
Reply to this email directly or view it on GitHub.


Backport/rocko 19 08 14

The OSTREE_BRANCHNAME backport went wrong, will instead take something like that: https://github.com/advancedtelematic/meta-updater/pull/585

Weird, minnowboard keeps failing. Also on sumo and thud.

Weird, minnowboard keeps failing. Also on sumo and thud.

Can you reproduce locally? That test seems surprisingly flaky. I haven't determined why.

Seems like it's actually broken:
error: file
`/ostree/poky-ee5dda54cd602959a6b11de59df52e0f7d1de44b70436617c864101e1fdad072/
vmlinuz' not found.
error: you need to load the kernel first.

Press any key to continue...

Ok I think the last commit should fix it. Wasn't so easy to track down when everything depends on some variables being globally exported...

But then, I don't know how it works on master... Will investigate.

Will investigate

In src/boot/grub2/ostree-grub-generator of ostree, I see the comment "Default to /boot if OSTREE_BOOT_PARTITION is not set and /boot is on the same device than ostree/repo". Perhaps the directory layout is different in master?
In any case, it won't hurt to have the same export in master, right?
And is this ready to go by your estimation? Looks fine to me and ready for QA.

Yes, you're right it also belongs to master probably. Ready to test indeed!


Model refactor

Pull Request Test Coverage Report for Build 64

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at ?%

Totals

Change from base Build 41:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


Support W3 Validation

Great plugin! I found an issues using w3 validation when using the element syntax:
<js-tag></js-tag>

This also doesn't work if there was a JavaScript error on the page the input wouldn't show. A better method would be to do the following:
<label for="tags">Tags</label>
<input id="tags" type="text" placeholder="Enter tags (separated by commas)" class="js-tag" />

The update your directive to have restrict = 'c' and replace = true to replace the input with class="js-tag":
jsTag.directive('jsTag', ['$templateCache', function($templateCache) {
    return {
        restrict: 'C',
        scope: true,
        controller: 'JSTagMainCtrl',
        replace: true,
        templateUrl: function($element, $attrs) {
            var mode = $attrs.jsTagMode || "default";
            return 'jsTag/source/templates/' + mode + '/js-tag.html';
        }
    };
}]);

This validates as html5 compliant and provides a working input field if the library where to fail for some reason!
Additional features could be:

Grab the placeholder text from the input field, for your tags text
Apply an option to only load the directive on desktop computers vs mobiles

Thank you for your contribution.
Removing jsTag as a custom tag is not an option, but adding support for jsTag via attributes is welcome. I would like you to open a PR about it.


no tables populated in DB

I have a DB bound to my page deployment for the manager but when I select it in the interface, I'm greeted with the DB title up top, the query field and no tables.
When I download the DB from the "download" button and open it up I get "{"success":false,"error":"Route not found"}"

+1 Facing the same issue

I just added some server logs. Can you try to re-deploy and tail the logs with wrangler pages deployment tail? (See an example here.)
Additionally, if you have any special characters in the table name, please let me know.

遇到相同的问题，没有可选的数据库

遇到相同的问题，没有可选的数据库
遇到同样的问题 ，老铁解决了吗？

+1 the same isssue
use  wrangler pages deployment tail ,get log here
(debug) d1-manager:dbms Database Bindings: +0ms

set D1 database bindings
before you deploy the workers
you will find the table
if want to change or add DB , you can git pull ,change some code ,and commit and push .
the workers will rebuild and deploy again . and then ,you will find out the DB table you added


Remove nrfxxx nwtsim

CONFIG_BOARD_NRFXX_NWTSIM doesn't exist and thus any code ifdef
protected cant be compiled or tested.  Remove this dead code.
Additionally, this code scatters a ton of CONFIG_BOARD_* defines in drivers and core code and we shouldn't be doing that.

This requires some discussion. In particular whether it would be possible to have this encapsulated in a more centralized way where it wouldn't be scattered all over the code, so that compatibility with the non-existent board can be kept upstream but at the same time it doesn't tarnish the code in the way it's today.
@aescolar-ot Do you have any proposals in this direction?

Agreed, as a general rule we shouldn't accept changes that have CONFIG_BOARD_* in subsytems and drivers w/o some really good reason, and especially not over 50 #ifdef/ifndef cases.

Agreed, as a general rule we shouldn't accept changes that have CONFIG_BOARD_* in subsytems and drivers w/o some really good reason, and especially not over 50 #ifdef/ifndef cases.

Maybe we could introduce a new Kconfig option that targets special simulated environments so that instead of relying on a particular board, we add this knowledge directly into the kernel.

Maybe we could introduce a new Kconfig option that targets special simulated environments so that instead of relying on a particular board, we add this knowledge directly into the kernel.

Even for simulators we should try and avoid this kinda thing.  I know we've done it a little in a few places for qemu or other simulators, but I think it needs to be very isolated.
I'm not sure if anyone can share what's going on with the NRF__regw_sideeffects calls.  What are they trying to accomplish?

Codecov Report

Merging #7064 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #7064      +/-   ##
==========================================
- Coverage   58.62%   58.61%   -0.01%
==========================================
  Files         464      464
  Lines       47440    47440
  Branches     8790     8790
==========================================
- Hits        27811    27809       -2
- Misses      15796    15798       +2
  Partials     3833     3833

Impacted Files
Coverage Δ

samples/philosophers/src/main.c
96.87% <0%> (-1.57%)
:arrow_down:

lib/posix/pthread.c
69.34% <0%> (-0.51%)
:arrow_down:

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 f2177bf...e94140d. Read the comment docs.

@galak please allow us a couple of days to discuss this and present an appropriate way forward.

No worries, I will.  Was opening this PR so people can see the code impact and generate the discussion on the topic.

Some snippets from the last time this was discussed:

Running the same SW on HW and in a simulator is a very old problem.
There exist some more sofisticated solutions than what we have done here that we could be inspired by.
They pretty much all require that we interface with some function-based interface (HAL layer) instead of this unmanage-able struct-based interface (CMSIS).

If you want to avoid macros you could always have a single header-file with
the function prototypes and then 2 different source implementations, one for sim,
one for HW. This is a zero-cost abstraction if you build it correctly.

What's the latest on the cleanup here?  Its been a few weeks now.

@galak A more thorough cleanup is ready in a provisional repo using the NRFx HAL.
But that required a few fixes in the NRFx HAL, some of which are in the process of being merged in right now.
As soon as those are in, another PR will follow here.
You can safely close this PR.

Want to leave this open til the other PRs mentioned get merged.

What are the PR # that fix this?

@galak no PRs yet, we are waiting for the required drivers to get merged to nrfx first.

@carlescufi what timeframe are we talking about?  If this is going to take some time, I'd rather we remove this dead code for now, and let a proper fix come in when you guys are ready.

@galak target is next week.

@galak this code is not dead, we are using it. It is just of no direct use for you.
Anyhow, the commits for fixing this are ready and based on the original code.
If this PR were to be merged, it would create unnecessary extra work for the rest of us. Given that this code is not creating any real inconvenience for you, I would hope you could wait.

@galak this code is not dead, we are using it. It is just of no direct use for you.
Anyhow, the commits for fixing this are ready and based on the original code.
If this PR were to be merged, it would create unnecessary extra work for the rest of us. Given that this code is not creating any real inconvenience for you, I would hope you could wait.

The code is dead since it can't be built or tested by any random person.
I'm fine waiting as long as this get resolved before the merge window for 1.12 closes.

https://github.com/zephyrproject-rtos/zephyr/pull/8418 fixes this instead


Easily allow family option for requests

Hi,
We're using node-fetch extensively throughout our projects. We've identified an issue where we have intermittent request failures.
After debugging the issue we're pretty sure that node is sometimes trying to use IPv6 to do DNS lookups and failing as described in this issue https://github.com/nodejs/node/issues/7931.
I would like to allow the family option to be passed to the request directly rather than needing to use the http/https agent. Passing the option directly will allow our code to be a lot simpler. We wouldn't need to differentiate between http/https requests etc.
How do you feel about the following approach?
https://github.com/bitinn/node-fetch/pull/506

I agree we would like to offer a solution to this for quite a while, I think Timothy could help.
There were PRs and I think they were stuck for some reasons.
(From my phone)

On Aug 20, 2018, at 9:54, joshuacullen<EMAIL_ADDRESS>wrote:
Hi,
We're using node-fetch extensively throughout our projects. We've identified an issue where we have intermittent request failures.
After debugging the issue we're pretty sure that node is sometimes trying to IPv6 to do DNS lookups and failing as described in this issue nodejs/node#7931.
I would like to allow the family option to be passed to the request directly rather than needing to use through an http/https agent. Passing the option directly will allow our code to be alot simpler. We wouldn't need to differentiate between http/https requests etc.
How do you feel about the following approach?
#506
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Awesome.
@bitinn Want to give Timothy a bump?

Hi @joshuacullen, I have decided against adding more non-spec compliant options.
But for future readers: check this test case, passing lookup through Agent should allow you to configure DNS lookup somehow. It's not in the nodejs doc, I am asking nodejs team to add them.

https://github.com/bitinn/node-fetch/blob/master/test/test.js#L1597-L1608
https://github.com/nodejs/node/issues/24098


Blank screen before starting the webapp

When the user starts the app the screen is blank which can be mistaken as an error.
Options:

show the first story
show a message

Which option will be more useful for developers?

Duplicate issue #56


First element of the list of elements, takes up entire window height, when using RTL or LTR layout methods

Issue
I faced one layout issue while rendering the list of elements.
Issue Description with Code Snippet
I have created a dummy app here, in which the hyperlink needs to be rendered with right_to_left layout.
If I don't use the with_cross_align() method, then as checked in below screenshot, the first element in the list takes up entire window size.
Code Snippet:
ui.with_layout(
    Layout::right_to_left(),
    |ui| {
        ui.add(egui::Hyperlink::from_label_and_url(
            "See User's Profile",
            format!("http://example.com/u/{}", user.id),
        ));
    },
);

Issue Screenshot

Workaround to be performed by every developers
We can fix the above using the with_cross_align method and passing the Align::LEFT in the params. But this is just a workaround, and not the actual fix.
The code snippet for that dummy app, along with the fix is also mentioned here.
Code Snippet:
ui.with_layout(
    Layout::right_to_left().with_cross_align(Align::LEFT),
    |ui| {
        ui.add(egui::Hyperlink::from_label_and_url(
            "See User's Profile",
            format!("http://example.com/u/{}", user.id),
        ));
    },
);

Screenshot

Note: I have submitted PR #1837 for the actual fix. I would like the creator of this awesome library, to look into that and help merge the fix asap.

The reason for this behavior is twofold:

with_layout uses up all available space
horizontal layouts centers vertically (as you noted)

Both these are the intended behavior. If you don't want to use up all the available space, use allocate_ui_with_layout.
If you don't want vertical centering, use .cross_align(Align::MIN).
The documentation for Layout is really bad though; I might take some time to improve that.

Thank you @emilk for the update. I really faced issues with reading the documentation but a great work by the way.
Would follow your advice.. Amd would mostly refer the source code to get updated features, instead of relying on docs.
Even I am unable to update my projects' docs, due to time constraint..


[Question]: ragflow-server looks start successfully, but can't access by 'http://localhost'

Describe your problem
这是后端服务

这是前端

请问是我哪里做的不对
下载的版本是0.14.1的dev

The IP address might be wrong.
Is it deployed on the host where the web explorer is?


double-beep: Watch rugler.com

double-beep requests the watch of the watch_keyword rugler\.com. See the MS search here and the Stack Exchange search here.

rugler\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Olivia in Charcoal HQ

Approved by Shree in Charcoal HQ


[BUG] Could not resolve suparnatural-kotlin-multiplatform:fs:1.1.0.

Describe the bug
After Bintray was closed on 1st May I can't reach the library.
Could not resolve suparnatural-kotlin-multiplatform:fs:1.1.0.

To Reproduce
Add library dependency to the project
"suparnatural-kotlin-multiplatform:fs:1.1.0"

or

"suparnatural-kotlin-multiplatform:fs-android:1.0.10"

Expected behavior
Stacktrace
* What went wrong:

Could not determine the dependencies of task ':[project]:[package]:compileDevDebugKotlin'.

> Could not resolve all files for configuration ':[project]:[package]:devDebugRuntimeClasspath'.

   > Could not resolve suparnatural-kotlin-multiplatform:fs:1.1.0.

     Required by:

         project :[project]:[package] > project :[project]:[package2]

      > Could not resolve suparnatural-kotlin-multiplatform:fs:1.1.0.

         > Could not get resource 'https://dl.bintray.com/kodein-framework/Kodein-DI/suparnatural-kotlin-multiplatform/fs/1.1.0/fs-1.1.0.pom'.

            > Could not GET 'https://dl.bintray.com/kodein-framework/Kodein-DI/suparnatural-kotlin-multiplatform/fs/1.1.0/fs-1.1.0.pom'. Received status code 403 from server: Forbidden

      > Could not resolve suparnatural-kotlin-multiplatform:fs:1.1.0.

         > Could not get resource 'https://dl.bintray.com/suparnatural/kotlin-multiplatform/suparnatural-kotlin-multiplatform/fs/1.1.0/fs-1.1.0.pom'.

            > Could not GET 'https://dl.bintray.com/suparnatural/kotlin-multiplatform/suparnatural-kotlin-multiplatform/fs/1.1.0/fs-1.1.0.pom'. Received status code 403 from server: Forbidden

version 1.0.10
* What went wrong:

Could not determine the dependencies of task ':[project]:[package]:compileDevDebugKotlin'.

> Could not resolve all files for configuration ':[project]:[package]:devDebugRuntimeClasspath'.

   > Could not resolve suparnatural-kotlin-multiplatform:fs-android:1.0.10.

     Required by:

         project :[project]:[package] > project :[project]:[package2]

      > Could not resolve suparnatural-kotlin-multiplatform:fs-android:1.0.10.

         > Could not get resource 'https://dl.bintray.com/kodein-framework/Kodein-DI/suparnatural-kotlin-multiplatform/fs-android/1.0.10/fs-android-1.0.10.pom'.

            > Could not GET 'https://dl.bintray.com/kodein-framework/Kodein-DI/suparnatural-kotlin-multiplatform/fs-android/1.0.10/fs-android-1.0.10.pom'. Received status code 403 from server: Forbidden

      > Could not resolve suparnatural-kotlin-multiplatform:fs-android:1.0.10.

         > Could not get resource 'https://dl.bintray.com/suparnatural/kotlin-multiplatform/suparnatural-kotlin-multiplatform/fs-android/1.0.10/fs-android-1.0.10.pom'.

            > Could not GET 'https://dl.bintray.com/suparnatural/kotlin-multiplatform/suparnatural-kotlin-multiplatform/fs-android/1.0.10/fs-android-1.0.10.pom'. Received status code 403 from server: Forbidden

   > Could not resolve suparnatural-kotlin-multiplatform:fs-metadata:1.0.10.

     Required by:

         project :onemeter-mobile-multiplatform:advertisingmonitor > project :onemeter-mobile-multiplatform:data

      > Could not resolve suparnatural-kotlin-multiplatform:fs-metadata:1.0.10.

         > Could not get resource 'https://dl.bintray.com/kodein-framework/Kodein-DI/suparnatural-kotlin-multiplatform/fs-metadata/1.0.10/fs-metadata-1.0.10.pom'.

            > Could not GET 'https://dl.bintray.com/kodein-framework/Kodein-DI/suparnatural-kotlin-multiplatform/fs-metadata/1.0.10/fs-metadata-1.0.10.pom'. Received status code 403 from server: Forbidden

      > Could not resolve suparnatural-kotlin-multiplatform:fs-metadata:1.0.10.

         > Could not get resource 'https://dl.bintray.com/suparnatural/kotlin-multiplatform/suparnatural-kotlin-multiplatform/fs-metadata/1.0.10/fs-metadata-1.0.10.pom'.

            > Could not GET 'https://dl.bintray.com/suparnatural/kotlin-multiplatform/suparnatural-kotlin-multiplatform/fs-metadata/1.0.10/fs-metadata-1.0.10.pom'. Received status code 403 from server: Forbidden

Version
1.0.10 and 1.1.0
Platforms affected:

iOS [x]
Android [x]
JVM [ ]
JS [ ]

All the libs have been migrated to maven central. Try this setup. https://kmpdocs.suparnatural.com/fs/#setup

When placing
implementation("com.suparnatural.kotlin:fs:1.1.0")

and using maven central I get the following error:
:shared:iosSimulatorArm64Main: Could not resolve com.suparnatural.kotlin:fs:1.1.0.
Required by:
    project :shared

Possible solution:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

:shared:iosSimulatorArm64Test: Could not resolve com.suparnatural.kotlin:fs:1.1.0.
Required by:
    project :shared

Possible solution:
 - Declare repository providing the artifact, see the documentation at https://docs.gradle.org/current/userguide/declaring_repositories.html

It only happens for iOS simulator main and text, no other iOS or for Android. However, it seems to work still anyways (Android does work, haven't had a chance to test iOS yet).

@coderforlife  I got the same issue. seems like iOS Simulator Arm 64 metadata is missing.
`FAILURE: Build completed with 2 failures.
1: Task failed with an exception.

What went wrong:
Execution failed for task ':shared:transformIosMainCInteropDependenciesMetadataForIde'.

Could not resolve all files for configuration ':shared:iosSimulatorArm64CompilationDependenciesMetadata'.
Could not resolve com.suparnatural.kotlin:fs:1.1.0.
Required by:
project :shared
No matching variant of com.suparnatural.kotlin:fs:1.1.0 was found. The consumer was configured to find a library for use during 'kotlin-metadata', preferably optimized for non-jvm, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native', attribute 'org.jetbrains.kotlin.native.target' with value 'ios_simulator_arm64' but:
- Variant 'commonMainMetadataElements-published' capability com.suparnatural.kotlin:fs:1.1.0 declares a component for use during 'kotlin-api':
- Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'native'
- Other compatible attributes:
- Doesn't say anything about its component category (required a library)
- Doesn't say anything about its target Java environment (preferred optimized for non-jvm)
- Doesn't say anything about org.jetbrains.kotlin.native.target (required 'ios_simulator_arm64')

BUILD FAILED in 711ms`


Propagate child output ordering in GpuCoalesceBatches

Fixes #3002.
GpuCoalesceBatches was failing to propagate the child output ordering.  This can force the plan to re-sort the data on a subset of the keys that the plan had already sorted on, and without forcing a stable sort can cause inadvertent reordering of data.

build


update(curriculum): Change advanced bash tutorial title to new title

Will this create any problems with crowdin? This curriculum file exists in the other languages. I renamed the file - my understanding is that crowdin will get all the english files, create duplicates in the other languages, and translate the known strings. That process would not keep the old files in the other languages. So it should be fine.
Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

I do not think so, that said I think we would have to re-arrange the folder naming a bit.
On a side note, I hate this:

I propose we move the certificates up the order with a 00-certificates, which should allow us to add folders for these new certifications.

I propose we move the certificates up the order with a 00-certificates, which should allow us to add folders for these new certifications.

At that point can I suggest to rename Coding Interview Prep as 99-coding-interview-prep so it will always be the last one as it is not a certificate by itself?

Yeah - probably. Just to add, the reorganisation bit can be a part of its own PR, not this.

@nhcarrigan I think it's worth it, with the suggestion of translating the things in crowdin in order, everything after Interview COding Prep may end be translated after it, and Interview Coding Prep is almost 50% of the curriculum by itself. Maybe not fun for the couple of languages that are already there, but it would streamline everything for the others without too much explanations of what order to do things


Updated getting-started.md

Overview
Added the usage documentation from Armo Platform docs

Hi @Anu-Ra-g,
Thanks for jumping in!  We're actually in the middle of a migration of the content from ARMO's readme.com instance to kubescape.io, in this repo here.
That will also involve creating and uploading new screenshots - we can't just link to the hosted versions, and they're out of date anyway.
I would encourage you to watch that repo to see how you can get involved!


dispatcher: add simple unit tests

Description:
The dispatcher has no real unit testing of documented functionality.  As components that are linked into Envoy start to take advantage of the dispatcher, this functionality should have unit tests that clearly show that the methods work as desired.
Risk Level: Low
Testing: Added new tests.

I chose not to use atomics because of the issue mentioned here and the fact that the condition variable requires a mutex to exist anyway.  Let me know if I'm missing something and using an atomic bool would be a better solution.

I chose not to use atomics because of the issue mentioned here and the fact that the condition variable requires a mutex to exist anyway. Let me know if I'm missing something and using an atomic bool would be a better solution.

That's fine.


what's the parameter 'borders' means?

Hello!
in build_model, borders control the generation of encoded image. what's the 'borders' mean? what's the different between 'no_edge' 'black' 'random' 'white' and 'image'

The border parameter describes how to pad the image during the affine transform augmentation:
black - pad with black pixels
white - pad with white pixels
random - pad each example with a random color
'image- pad with a random image (ie composite the masked transformed image on top of a random image)no_edge` - Do not perform affine transformation

@tancik Thanks for your reply, I have a confuse about the perspective transform.
in your code:
input_image --(perspective)--> input_warped --(CNN)--> residual_warped --(inverse perpective)--> residual
In my sight, residual should come from input_image, and encode_image = residual+input_image, and then get some perspective transform
Are the two method the same operation?

The CNN to encode is applied prior to the transform.
input_image --> CNN_encoder --> residual --> (perspective) --> residual_warped
We also run the following:
input_image --> (perspective) --> input_warped
This allows us to calculate the encoded image with and without the warping:
encoded_warped = input_warped + residual_warped
encoded = input + residual

@tancik I don't know if I understand correctly,
In your code, residual comes from residual_warped(by inverse perspective) and residual_warped = encoder((secret_input, input_warped))
In your reply, residual should comes from input_image directly?

Ahh, yes, it is a bit confusing. We do a prewarp to the image which in practice allows the borders to be independent of the warping. I think what ultimately matters is that some form of warping is performed, our implementation is not necessarily ideal. I think it is useful to visualize the networks inputs and outputs with tensorboard. The attached screenshot includes some annotations that are hopefully useful.


react-native-picker-select destroys tests

Describe the bug
Any module which imports the react-native-picker-select package immediately causes a test suite to fail.
To Reproduce
Steps to reproduce the behavior:

Head to the directory for your local repo for this project and commit any code changes you have made.
git checkout -b clients
git branch --set-upstream-to=origin/clients clients
git pull
npm test

Expected behavior
I should be able to run tests on a component defined in a module that imports the react-native-picker-select package.
Screenshots

Additional context
The solutions described here, here here and here have not fixed the problem.

Having this issue with our Batches screen as well.

Fixed the problem. It is an issue with Jest and React Native (it has nothing to do with Enzyme). Any third-party React Native library written in TypeScript but not compiled when uploaded to the npm registry breaks any test suite that imports that library (or any test suite which imports a module that imports the library).
The problem has something to do with Babel expecting to see JavaScript code while browsing node_modules files written in TypeScript. The Jest docs suggest a simple workaround that is easy to implement: see description of transformIgnorePatterns and the section for the React Native.
For our case, we need a little extra finagling to implement this workaround because we configure Jest using the withEnzyme method from jest-expo-enzyme. Here is an example of what needs to be done:
const {withEnzyme} = require('jest-expo-enzyme');

const addSetup = (config) => {
  config.setupFilesAfterEnv.push('<rootDir>/__tests__/setup.js');
  config.testMatch = [
    '<rootDir>/src/component/Clients/ClientScreen.test.js',
  ];
  config.transformIgnorePatterns = [
    'node_modules/(?!(jest-)?(react-native|@react-native-community|expo(nent)?|@expo(nent)?/.*|react-navigation|@react-navigation/.*|@unimodules/.*|unimodules|sentry-expo|native-base|react-native-svg|@react-native-picker|react-native-picker-select)/)',
  ];
  return config;
}

module.exports = {
  projects: [
    addSetup(withEnzyme(require('jest-expo/android/jest-preset'))),
  ],
  collectCoverage: true,
  collectCoverageFrom: [
    '<rootDir>/src/**.{ts,tsx,js,jsx}',
    '<rootDir>/src/component/Header/Header.tsx',
    '<rootDir>/src/screens/Batches/Batches.tsx',
  ],
  coverageDirectory: 'coverage',
  coverageThreshold: {
    global: {
      statements: 70
    }
  },
}

Any third-party module which breaks tests needs to be added to the enormous string assigned to config.transformIgnorePatterns.


add config for prisma language server

adding a config setup for the prisma language server

Squash the commits, then I'll merge.

Squash the commits, then I'll merge.

done

We can't do this re: prisma-fmt, the binary needs to be on path, or it will crash prisma.


Js/2596 bug hidden notes stack view

Description
Resolves #2596: Users were able to see each others notes in stack view, even if the option was disabled in board settings.
Changelog

Fixed users being to see each others notes in stack view if the option is disabled by filtering them out

Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] The light- and dark-theme are both supported and tested
[x] The design was implemented and is responsive for all devices and screen sizes
[x] The application was tested in the most commonly used browsers (e.g. Chrome, Firefox, Safari)

Might be a minor thing, but when the setting is changed to not show notes of other users while in Stack View and the parent note is from another user, it should navigate out of the stack view.
(e.g., user A creates a note, user B opens the note in Stack View. User A changes the setting, but User B still sees the note from user A in Stack View)

Not sure if moderators should see other cards despite the option but i think its good that way :)

@CronJorian yeah you're right about that, tbh I forgot to consider it, but if it turns out moderators should always see all notes, we can easily change it afterwards 👌

Not sure if moderators should see other cards despite the option but i think its good that way :)

@CronJorian yeah you're right about that, tbh I forgot to consider it, but if it turns out moderators should always see all notes, we can easily change it afterwards 👌

That's what I thought too, so it's fine that way:)


logic: Support matching closed issue with link

Note: I only tested this by hand in a python interpreter.

Thanks so much, we really need unit tests, but I guess adding this without is fine.
Also the idea is that this tool is not specific to pydantic (though it might never be used elsewhere), so I guess the org/user and repo should be [^/+] or similar?

And you can move the ID out of the regex group.

Also the idea is that this tool is not specific to pydantic (though it might never be used elsewhere), so I guess the org/user and repo should be [^/+] or similar?

Good idea. In that case, should we add org/user name and repo name to Settings? Alternatively I could match it to [-a-zA-Z0-9]+ or something like github username regex. That opens up a possibility for false positives though.
I'm matching [-a-zA-Z0-9]+ for now.
Neat tool by the way!

Best to use [^/]+ (sorry fixed above).
Can't add to settings since one deploy would serve all repos.

Best to use [^/]+ (sorry fixed above).
Can't add to settings since one deploy would serve all repos.

Ah, that makes sense.

Thanks so much, will be auto deployed in a few minutes.


Fix announcers issue on broken connections

When the connection is broken, the server keeps the old Calypso announcers, so we are resetting them when a new connection is made to avoid wrong references.

These "applyChangesFromClient.st" commits are old, they shouldn't be here in this PR...

Right, there are separate subscriptions for SystemAnnouncer from browser
tabs (check references to ClyMethodChange, ClyClassChange and
ClyPackageChange).
Try to release them with:
SystemAnnouncer uniqueInstance subscriptions subscriptions
   select: [ :each | each subscriber isSeamlessProxy ]
   thenDo: [ :each | SystemAnnouncer uniqueInstance unsubscribe: each
subscriber]

чт, 5 мар. 2020 г., 19:46 oliveiraallex<EMAIL_ADDRESS>
@oliveiraallex commented on this pull request.
In TelePharo-Core.package/TlpRemoteIDE.class/instance/connectTo..st
https://github.com/pharo-ide/TelePharo/pull/30#discussion_r388457505:

@@ -8,6 +8,7 @@ connectTo: aTCPAddress
remotePeer := connectingNetwork remotePeerAt: aTCPAddress.
remotePharo := TlpRemotePharo peer: remotePeer.
remotePharo registerTools: tools.

remotePharo evaluate: [TlpRemotePharo resetCalypsoAnnouncers].
"When a new connection is made, the annoucers of Calypso on the server side need to be reseted, because if the network is broken, the server keeps the wrong old announcers"

Humm.. this cleanup it's not working. It removes the queryCache, but this
some times doesn't make the browser work again on the client-side
[image: image]
https://user-images.githubusercontent.com/39618015/76009478-8e9da400-5f11-11ea-8d70-4a0866259a36.png
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/pharo-ide/TelePharo/pull/30?email_source=notifications&email_token=AB6FVICND7F7UQQGSGNAVPDRF7QQFA5CNFSM4LBK7472YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCYFGZWQ#discussion_r388457505,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6FVIFFCBY2HXHBN5UBQQDRF7QQFANCNFSM4LBK747Q
.

@dionisiydk
What you mean is this?
https://github.com/pharo-ide/TelePharo/pull/30/commits/9bb51325924d4ace571f001d7131a3950ffdb00d

@dionisiydk but the problem, in this way, this implementation is not fixing this scenario. Sometimes the error starts when you disconnect and connect after many times.
I put a halt in #cleanupEnvironmentFromRemoteTool and it's not called. So, the cleanup method is not called and the error still happened.

I see what is happening. If we do not close remote browser and disconnect
then tools are successfully unregistered but browser still keeps all
subscriptions.
So you right, it should be unconditional cleanup (without ifTrue).
вт, 10 мар. 2020 г., 23:50 oliveiraallex<EMAIL_ADDRESS>
@dionisiydk https://github.com/dionisiydk but the problem, in this way,
this implementation is not fixing this scenario. Sometimes the error starts
when you disconnect and connect after many times.
I put a halt in #cleanupEnvironmentFromRemoteTool and it's not called. So,
the cleanup method is not called and the error still happened.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pharo-ide/TelePharo/pull/30?email_source=notifications&email_token=AB6FVIHL653NFCF7MP5PX6LRG2RZ7A5CNFSM4LBK7472YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEONDDFQ#issuecomment-597307798,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6FVIDVATRSKPLCGP533ZTRG2RZ7ANCNFSM4LBK747Q
.

And I think that we also need to do cleanup during disconnection because
normal disconnection must leave the remote image in good original shape.
So add also the cleanup into TlpRemoteUIManager>>#restoreLocalTools.
(The current logic (during connection) is still needed to recover from
really broken scenario (when client dies)).
ср, 11 мар. 2020 г., 10:06 Denis Kudriashov<EMAIL_ADDRESS>
I see what is happening. If we do not close remote browser and disconnect
then tools are successfully unregistered but browser still keeps all
subscriptions.
So you right, it should be unconditional cleanup (without ifTrue).
вт, 10 мар. 2020 г., 23:50 oliveiraallex<EMAIL_ADDRESS>
@dionisiydk https://github.com/dionisiydk but the problem, in this
way, this implementation is not fixing this scenario. Sometimes the error
starts when you disconnect and connect after many times.
I put a halt in #cleanupEnvironmentFromRemoteTool and it's not called.
So, the cleanup method is not called and the error still happened.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pharo-ide/TelePharo/pull/30?email_source=notifications&email_token=AB6FVIHL653NFCF7MP5PX6LRG2RZ7A5CNFSM4LBK7472YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEONDDFQ#issuecomment-597307798,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6FVIDVATRSKPLCGP533ZTRG2RZ7ANCNFSM4LBK747Q
.

In this last commit, I did a test with 2 clients connecting at the same time, editing and disconnecting 1 and connecting again
It's working.


Difference between ensure and finally

The difference between ensure and finally is not clear in the docs. As far as my understanding, ensure can be called before catch and finally can be called after catch. But both functions are executed after the whole promise chain.
Is this correct?

PromiseKit version: 6

Finally is executed after the whole chain. Ensure is executed where it is in the chain.

Like both are executed WHERE THEY ARE in the chain. Not sure how you came to think otherwise.

Hey @mxcl
In the commit that references this issue you write:

finally is the same as ensure, but it is not chainable

However, there's another subtle difference between the two--ensure can be called on a DispatchQueue of a user's choice whereas finally can't. Am I correct in assuming that a user should resort to using ensure as a substitute for finally if they're interested in calling the closure on a specific queue? Also, I'm curious to know why finally has the limit of not being able to be called on any queue?
Thanks!

This is an omission, finally should take a queue.

@mxcl Done: https://github.com/mxcl/PromiseKit/pull/876

Reading the V6 news item, I find the difference a bit confusing too.
Looking at the example in the PromiseKit readme:
firstly {
    when(fulfilled: fetchImage, fetchLocation)
}.done { image, location in
    self.imageView.image = image
    self.label.text = "\(location)"
}.ensure {
    UIApplication.shared.isNetworkActivityIndicatorVisible = false
}.catch { error in
    self.show(UIAlertController(for: error), sender: self)
}

vs the use of finally:
firstly {
    when(fulfilled: fetchImage, fetchLocation)
}.done { image, location in
    self.imageView.image = image
    self.label.text = "\(location)"
}.catch { error in
    self.show(UIAlertController(for: error), sender: self)
}.finally {
    UIApplication.shared.isNetworkActivityIndicatorVisible = false
}

Would the difference be that with the first example, the isNetworkActivityIndicatorVisible = false code is executed before the self.show block, and with the second example it is executed after the self.show line?
Is that the only difference, or does it have any other side effects?

Would the difference be that with the first example, the isNetworkActivityIndicatorVisible = false code is executed before the self.show block, and with the second example it is executed after the self.show line?

That's correct.

Is that the only difference, or does it have any other side effects?

This is the only difference with the example code.


Upgrade app-operator to v5.10.0

Towards https://github.com/giantswarm/giantswarm/issues/21891
Checklist

[x] Update changelog in CHANGELOG.md.

❤  🎉

Build is green but the status does not seem to get reported back by CircleCi.