About different indices and schemas

My use-case is an indexing agent that indexes certain websites that a user specifies. The websites are grouped into similar technology stacks.
For example, all ***.stackoverflow.com websites are the same, all websites using Wikimedia behave the same etc.. And each of these families might have different features and properties I would like to index. Depending on the family it might be possible to extract more knowledge or more structured knowledge than from a simple website.
Other families could be audio files containing a lot of metadata I'd like to be able to query for: lyrics, year, artist. Maybe images too with their: size, timestamps, primary colors, aspect ratio etc..
This question is a follow-up of #2221. Performance wise, is it better to have one single, big index with sparse entries. Or would it be better to have a single index for each family mentioned above. And have multiple readers accessing the index files simultaneously?
It is hard to test this without building the index beforehand. But it takes a lot of time to prototype it. So I was hoping for people with more insights to give me a little bit help and advice.
I personally feel like the second approach might explode quickly if one has too many families.

Indexing or search performance? What type of query?

@mainrs did you figure out an optimal solution for your problem? I am dealing with something quite similar and would appreciate any insight you may have to offer!


Added a working port of gawk and a port of xz-utils.

The gawk port works fine in my limited testing, but the xz-utils port needs some work in mlibc, the current issue for xz-utils is an unknown printf() terminator, see the issue here for more information on that.

Looks good, thanks a lot for your efforts.


fix d.ts based on pull request comments (it was missing)

Just realized,
In the previous PR we merged the wrong version of the d.ts definitions:
https://github.com/arnaudbenard/redux-mock-store/issues/39
The right version was the one commented by @asgarddesigns  but by mistake we merged the one in the PR.
import {Store} from 'redux';

interface MockStore extends Store {
    getState():any;
    getActions():Array<any>;
    dispatch(action:any):any;
    clearActions():void;
    subscribe():any;
}

declare function configureStore(...args:any[]):(...args:any[]) => MockStore;
export = configureStore;

In this fork you can find the fix (gong to add it to a new issue I have created).

👍

Give me a buzz when it is published on npm to give a try.
Thanks
Braulio


Does it have a proxy config option?

Hi, i would like to know if there is a proxy setting once i'm running behind a proxy.
Thanks.

Hi!
I believe you could use NANO_BOTS_API_ADDRESS to set a proxy. Or, use a local API instance to make it go through a proxy. Also, I believe tools like Charles Proxy may help you with that as well.


[Feature] Create landing page for LinksHub

Description
As of now, we don't have any landing page for LinksHub. But we are done with the design, you may figma files here
Additional Info
Multiple contributors can work on this issue
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (optional)
[ ] I am a GSSoC'23 contributor

i would like to work on this issue please assign to me

i would like to work on this issue please assign to me

Sure :)

i would like to work on this issue please assign to me

Are you a GSSoC’23 contributor?

yes

yes

Thanks, could you please create a draft PR until you're working on the issue? that would be much helpful for us to track your activity :)

hey @rupali-codes, is this issue still open?

hey @rupali-codes, is this issue still open?

Yes, do you want to work on this?

yes

yes

Thanks, would you mind creating a darft PR?

yes

Thanks, would you mind creating a draft PR?

yes

yes

Thanks, would you mind creating a draft PR?

I am creating a new landing page using Figma design mentioned above. it is a new app as of now, then we will integrate it directly into the main website..?? or shall I start directly integrating into the main website??

didn't get you sorry

yes

Thanks, would you mind creating a draft PR?

I am creating a new landing page using Figma design mentioned above. it is a new app as of now, then we will integrate it directly into the main website..?? or shall I start directly integrating into the main website??

didn't get you sorry

ok check this draft pr [#804]

@Noothan-am are you still working on the issue? any updates?

yes, i am still working on this here is the landing page link for preview
👉https://my-links-hub.vercel.app/

CSS needs to be fixed
buttons and links are not active till now

will fix it soon working on it...

yes, i am still working on this here is the landing page link for preview 👉https://my-links-hub.vercel.app/

CSS needs to be fixed
buttons and links are not active till now

will fix it soon working on it...

It’s look great @Noothan-am! :)

@Noothan-am it looks really awesome, thanks :)

@rupali-codes
I'm a GSSOC'23 contributor
Is this issue open ?
I'm interested to work on this.
Can you assign it to me?

yes, i am still working on this here is the landing page link for preview 👉https://my-links-hub.vercel.app/

CSS needs to be fixed
buttons and links are not active till now

will fix it soon working on it...

It’s look great @Noothan-am! :)

yes, i am still working on this here is the landing page link for preview 👉https://my-links-hub.vercel.app/

CSS needs to be fixed
buttons and links are not active till now

will fix it soon working on it...

hey @Noothan-am  I"m interested to work on this . Can we work together.
Please let me know your decision.

ok

hey @Noothan-am
Just drop a Hii to my discord
Discord username : itsmohit097#8439
Discord id:-<PHONE_NUMBER>32839179

hey @itsmohit097, sent a friend request from @dev13#5749

hey @itsmohit097, sent a friend request from @dev13#5749

should we create a sperate channel for it?

@Noothan-am & @itsmohit097 we would need to finish this issue as soon as we can, bcz we want to add a few more things on the dashboard, let me know if you need any kinda help

hey @rupali-codes were are working on it still. and i have couple of questions

@rupali-codes we will update you by tomorrow morning

hey @itsmohit097, sent a friend request from @dev13#5749

should we create a sperate channel for it?

it will be better @rupali-codes

hey @itsmohit097, sent a friend request from @dev13#5749

should we create a sperate channel for it?

it will be better @rupali-codes

Please share me your discord usernames so i can add you up there. Or have you joined LinksHub's discord?

hey @rupali-codes were are working on it still. and i have couple of questions

is this landing page to be a home page
if so which pages should we link to resources, about us , contact us page ?

let's discuss out there

share me your discord usernames so i can add y

yes i am in LinksHub discord

what is ur username

dev13#5749

i can not find you

just now i messaged you

itsmohit097 #8439

can u try joining this

hyyy...could you please assign me this problem??

hyyy...could you please assign me this problem??

this issue is assigned to @Noothan-am & @itsmohit097, and i guess they are done with it. So, can you please look for some other issues :)

@Noothan-am @itsmohit097 please update your progress.....and try to complete the issue as soon as possible, and let me know if you are facing any issues....or any help needed from my side :)

hey @k-deepak04 @rupali-codes , I have exams currently so I will give the code you can assign it to someone else.

my exams are over now i can start working on it by tomorrow @rupali-codes

okay @itsmohit097 please complete this soon

@k-deepak04 this issue has been opened from a while, i'm going to work on this at me own, as i wanna make some improvements in the design it self.
@Noothan-am & @itsmohit097 thank you for your support and collaboration!

@rupali-codes made any progress or need any assistance?

@rupali-codes made any progress or need any assistance?

Not actually, lets close this issue for now. I'll raise a new when i'm ready for it :)


Include DataUriSvgWriter?

Is there a specific reason why the Twig function qrcode_data_uri() cannot generate SVG? Implemenation looks straightforward to me: Just create DataUriSvgWriter (extending SvgWriter, as DataUriWriter does). Can I commit that?

Hi @ThomasLandauer no problem. Feature requests are always welcome. I added a SvgDataUriWriter in 2.0.6 and extended the qrcode_data_uri method so it works like the qrcode_path method.

Wow, cool! :-)
However, there's an issue which I don't know how to fix: The Twig extension is effectively calling SvgWriter, not SvgDataUriWriter! Result: The data:image/svg+xml;base64, part is missing from the output.

I already noticed. This should be fixed in the latest version.

Well, I'm having trouble keeping up with composer update today.... ;-)
Thanks, works now!


csound-manual: 6.17.0 -> 6.18.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/csound/manual/releases.
meta.description for csound-manual is: "The Csound Canonical Reference Manual"
meta.homepage for csound-manual is: "https://github.com/csound/manual"
meta.changelog for csound-manual is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 6.18.0 with grep in /nix/store/fs4j4m66f8xwnccjbh805ndfx3ib04lv-csound-manual-6.18.0
found 6.18.0 in filename of file in /nix/store/fs4j4m66f8xwnccjbh805ndfx3ib04lv-csound-manual-6.18.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
csound-manual

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/fs4j4m66f8xwnccjbh805ndfx3ib04lv-csound-manual-6.18.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A csound-manual https://github.com/r-ryantm/nixpkgs/archive/c9e344912b5d0dae7184e3e228d95693d65f673d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/fs4j4m66f8xwnccjbh805ndfx3ib04lv-csound-manual-6.18.0
ls -la /nix/store/fs4j4m66f8xwnccjbh805ndfx3ib04lv-csound-manual-6.18.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

csound-manual

Maintainer pings
cc @hlolli for testing.

@ofborg build csound-manual csound-manual.passthru.tests


feat: Define intNorm and intTrace.

The connection to RingOfIntegers.norm will be provided in a later PR.

The connection needs some other stuff (for example #9444) and will come in a later PR.

I somehow missed this PR, sorry. Anyway the new intNorm could completely replace RingOfIntegers.norm, right?

Maybe yes. This might not work when k and K aren't number fields but we might not care.
I'd still keep RingOfIntegers.norm but redefine it in terms of intNorm though.


[[FIX]] Correct location reported for W043

In addition, do not emit the E029 error. Maintain the error code itself
to replace with W043 in a future release.
This is intended to resolve gh-3152.

Coverage remained the same at 97.763% when pulling 7dbae3d4b185fab059ea2f8fc5b9a5a4fef0f55a on jugglinmike:3152-w043-location into d3d84ae1695359aef077ddb143f4be98001343b4 on jshint:master.


Fix usage of UNKNOWN! in regression test 37 01

https://github.com/goblint/analyzer/pull/260/files#r662129466

Fixed. There were also some UNKNOWN! in the branching test which should have been UNKNOWN instead following Michael's description. I changed them as well.


Code deduplication in operations over array containers when conversion from array containers to bitmap

SUMMARY
Code deduplication in operations over array containers, where it is a lot of code, which can be replaced by call to existing methods. The performance should not be affected as both code sections are early the same, if not the same completely.
Automated Checks

[x] I have run ./gradlew test and made sure that my PR does not break any unit test.
[x] I have run ./gradlew checkstyleMain or the equivalent and corrected the formatting warnings reported.

I have approved.
Maybe @richardstartin wants to have a look?


Make it easier to pipe to files

I am having trouble figuring out how to pipe command's stderr to a file :)
Here's the code I arraivied at:
const child = $`my-command`.stderr('piped').spawn();
child.stderr().pipeTo((await Deno.open("log.vopr")).writable)
await child

This typechecks, but throws at runtime  Error: Bad file descriptor (os error 9), and it requires reaching for raw Deno.open APIs. As far as I understand, it isn't actually possible to do that with $.path API (or I am utterly failing at finding this in the API surface).
Ideally, I'd love to write just
await $`my-command`.stderr($.path("log.vopr"));

Not sure whether there's a gap in the API surface or in my doc reading abilities :)
(note: I really want to pipe there, as the output is gigs in size)

Yeah, it's not very good atm (my knowledge of pipes in JS when I wrote this was not good). This works for me in the latest version:
import $ from<EMAIL_ADDRESS>
const txtFile = $.path("test.txt");
using file = txtFile.createSync();
await $`deno eval 'console.error(1); setTimeout(() => console.error(2), 2000);'`
  .env("NO_COLOR", "1")
  .stderr(file);

(I should update the docs with an example showing this... it's not in the docs)

await $my-command.stderr($.path("log.vopr"));

Yeah, that would be good because it could also handle automatically closing the file when the command is done.

Ah, right, indeed its the case of me being lost in the API maze! I guess I can name a couple stumbling blocks:

the .stderr( parameter, if I recall, has to be a WriterSync, and that made me falsely assume that I wouldn't be able to just pass a file here, as I expected the relevant API to be asynchronous. That's why I started reaching out for spawn.
besides assuming that file can't be WriterSync, I tried to search for relevant "impls", but failed:

in VS Code, because it is a dependency, I can't use "whole project text search" to just look for relevant functions acrosss files in the library
the API docs are not particularly useful either https://deno.land/x/dax@0.36.0/mod.ts?s=WriterSync

Not sure if theer's anything actionable here. Maybe defining ShellPipeWriterKind as
| "inherit"
| "null"
| "piped"
| "inheritPiped"
| WriterSync
| FsFileWrapper

which is of course redundant, but also clearly signals to the user "hey, you could pass in a file here".

In 0.38.0 it's now possible to do:
await $`my-command 2> log.vopr`;
// or specified via a PathRef (ex. `$.path("somePath")`)
await $`my-command 2> ${pathRef}`;


Development edit email

Description
Check the balance before updating the email
Changes
Screencast from 19-05-24 16:17:14.webm
Related Issues

https://github.com/threefoldtech/tfgrid-sdk-ts/issues/2661

Checklist

[ ] Tests included
[ ] Build pass
[ ] Documentation
[x] Code format and docstrings
[x] Screenshots/Video attached (needed for UI changes)

What if i wanna cancel the edit ??

Screencast from 05-20-2024 04:30:42 PM.webm


FIX #259 - implementation of noEcho was never merged into master.

Coverage decreased (-0.2%) to 89.195% when pulling<PHONE_NUMBER>e1c16cf04c8640fd8ea31653977694 on fix-259 into b91d9f252ed918328dce32dbab4bf83ca01a59f3 on master.


tests: Reduce amount of kept builds

This PR reduces the amount of builds again. In addition it keeps all PR
builds for at least one month, so long running community PRs don't loose
their test logs.
@brancz Let me know if these numbers are still ok for you?

yay, green build :green_apple:


USE_TBB macro override in src/thread.h

To build successfully on Windows, the internal overriding of the USE_TBB macro should be removed as this is counter intuitive.
On Windows, this re-enabling/overriding causes the tbb.h header to be loaded and implicitly linking tbb.lib

I'm confused about the TBB part -- this seems to disable TBB, if not explicitly enabled, even on the Unix platforms.  Wouldn't it be better to leave the defaulting, but enclose it in a #ifndef WIN32?
The rest certainly looks fine to me.

Yes the original is confusing.
I have no problem with #ifndef WIN32, just that for the last pull request, #ifndef WIN32 was not recommend and a full fix was proposed.
In this case, my proposal for a fix is to not have the code in the first place.
I am happy with the #ifndef WIN32 proposal as long as it builds out of the box for those of us not using TBB

It's not clear to me which exact compile problem this is trying to fix, but I don't think adding #if WIN32 really solves the TBB issue? Seems it's due to inconsistent setting of USE_TBB in CMake. libOpenImageIO and maketx cmake files use the USE_TBB cmake option, but others like oiiotool don't.

The problem is that thread.h defines USE_TBB to 1 if it is not set. For Windows users that do not build with TBB, it forces linkage with tbb.lib.
Pull request #218 sets USE_TBB in only one cmake file (the "root" one right under src) and remove USE_TBB usage from other cmake files. Therefore, consistent usage is now guaranteed.
Because Cmake now takes proper care of all the settings for the developer, the thread.h code (#ifndef USE_TBB ... #endif) is now useless (but also harmless) and I think it should be removed.

The remaining #ifdef USE_TBB isn't quite useless -- it's for the benefit of other apps who may wish to use our thread.h (for which they wouldn't be able to count on USE_TBB being set by CMake).  Though if you want to argue that the default should be NOT to use TBB, then I wouldn't argue.
We keep flirting with the idea of removing TBB entirely, but IIRC the problem is that the Windows API fallbacks are actually horribly slow compared to TBB's implementation, so we've been afraid to mess with it.  I think that it's not an issue for Linux and OSX, though I'd want a round of benchmarks to be extra sure before we disable TBB for those platforms.
In the mean time, it kind of sounds like the real problem is/was inconsistent definitions of USE_TBB in the CMake files, no?
So, Henri (darkhorse64), are you saying that this change is no longer needed now that 218 has been merged, and that at most, the thread.h change should be to change the default to 0 for the benefit of apps that want to use thread.h but not worry about building or linking TBB?

Yes for the first question.
Yes for the second. This would get rid of the side effect of trying to link with tbb without ever asking for it.

Hi there, are we good with this pull request regarding TBB in thread.h ?


fix(dockerfile): copy libssl, libcrypto from build

Closes: #XXX
Description
Copy libssl and libcrupto from build image since current image is broken

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Can you please get in more details as to what's going wrong when building the image?
Please note that for building Hermes 1.1.0 you need to use the v1.1.0 Dockerfile which does include those COPY steps for OpenSSL shares libraries.
On the other hand, the Dockerfile on master can only be used to build Hermes master since we only removed the dependency on OpenSSL only after the v1.1.0 release.
If building from master please make sure to set the TAG variable to master.
I can provide detailed instructions for building both versions later today if needed.


workspaceStorage storage leak

// file: $HOME/.config/Code/User/workspaceStorage/xxxxxxxxxxxxxxhash/workspace.json
{
  "folder": "file:///path/to/projects/2021/foo/project-name-fork"
}

The above is the only way that VS Code currently associates workspace cache with a specific project residing in the folder: .....
Once the project's folder path gets renamed VS Code loses its reference to the project cache. Upon launching the cache gets rebuilt from scratch once again (ignoring the previous one). If repeated for several times the cache will grow enormously, wasting the startup-time and HDD storage space. C/C++ projects will turn into a storage killer (see related issues below).
Discovery
I got a  C++ project  that got indexed (including dependencies) multiple times.  Later I've moved it into another place so it got indexed once again. The same thing happened to a whole range of other C++ projects and forks I have. I ended up with having a significant amount of gigabytes wasted. :expressionless:
Steps to Reproduce:
Assuming you are using Linux-based OS and zsh/bash.

Install  C/C++ tools extension
Get any C/C++ project: e.g.$ git clone --depth 1 --no-tags https://github.com/madler/zlib /tmp/zlib-0
Remember the number of dirs in .../workspaceStorage, like so:
$ dir -d $HOME/.config/Code/User/workspaceStorage/* | wc -l
Open in VS Code, wait until cache gets indexed, close VS Code, rename the folder, open it up once again
$ code /tmp/zlib-0
$ mv /zlib-0 /zlib-1
$ code /tmp/zlib-1
Repeat the last 2 steps and see the number of folders in  .../workspaceStorage growing

Solutions proposal

Make it configurable so one can keep cache in the .vscode folder
Somehow mark the workspace (e.g. by a cookie) and keep its value both inside workspace.json and .vscode, making the cache a workspace-path-independent
Regularly clean stale caches - should be very cheap to implement and maintain

Workaround
As a temporarily solution I've made a simple bash script to audit cache files, checkout: code.workspaces.cache.filter

Versions

VS Code Version: 1.60.2 and earlier
OS Version:  Kubuntu 20.04 - Kubuntu 21.04 / x64

Extensions

C/C++ tools [v1.6.0] - Not a culprit in this case for sure

Related issues

#32461
#53552
#53552
#22557
#3884
#329

@bpasero Thanks for letting me know. I've updated the top.

@bpasero Thanks for letting me know. I've updated the OP.


Work on LOGO!

The logo of the website is very simple. I can make some changes in it. Can you please give me one chance and assign this work to me:)

Here you go 🚀  and make changes.


=== time: 15, textures/shared_vega/trim03a#7, drawCounts: 234
=== time: 7, textures/shared_vega/trim03a#8, drawCounts: 66
=== time: 1149, textures/shared_vega/trim03a#9, drawCounts: 126
=== time: 1188, textures/shared_vega/trim03a#10, drawCounts: 36
=== time: 12, textures/shared_vega/trim03a#11, drawCounts: 18
=== time: 1213, textures/shared_vega/trim03a#12, drawCounts: 345
=== time: 11, textures/shared_vega/trim03a#13, drawCounts: 12
=== time: 6, textures/shared_vega/trim03a#14, drawCounts: 36
=== time: 6, textures/shared_vega/trim03a#15, drawCounts: 18
=== time: 9, textures/shared_vega/trim03a#16, drawCounts: 99
=== time: 11, textures/shared_vega/trim03a#17, drawCounts: 165
=== time: 1154, textures/shared_vega/trim03a#18, drawCounts: 270
=== time: 20, textures/shared_vega/trim03a#19, drawCounts: 174
=== time: 1160, textures/shared_vega/trim03a#20, drawCounts: 264
=== time: 1345, textures/shared_vega/base03#0, drawCounts: 642
=== time: 2532, textures/shared_vega/base03#1, drawCounts: 816
=== time: 1352, textures/shared_vega/base03#2, drawCounts: 12
=== time: 1306, textures/shared_vega/base03#3, drawCounts: 396
=== time: 1373, textures/shared_vega/trim02#0, drawCounts: 30
=== time: 1416, textures/shared_vega/panel01a#0, drawCounts: 12
=== time: 1395, textures/shared_vega/trim04#0, drawCounts: 6
=== time: 14, textures/shared_vega/trim04#1, drawCounts: 78
=== time: 1418, textures/shared_vega/trim04#2, drawCounts: 66
=== time: 17, textures/shared_vega/trim04#3, drawCounts: 108
=== time: 4, textures/shared_vega/trim04#4, drawCounts: 6
=== time: 7, textures/shared_vega/trim04#5, drawCounts: 54
=== time: 5, textures/shared_vega/trim04#6, drawCounts: 6
=== time: 3163, textures/shared_vega/trim04#7, drawCounts: 66
=== time: 3517, textures/shared_vega/trim04#8, drawCounts: 72
=== time: 15, textures/shared_vega/trim04#9, drawCounts: 21
=== time: 5, textures/shared_vega/trim04#10, drawCounts: 12
=== time: 7, textures/shared_vega/trim04#11, drawCounts: 78
=== time: 46, textures/shared_vega/base02#0, drawCounts: 72
=== time: 18, textures/shared_vega/base02#1, drawCounts: 138
=== time: 5, textures/shared_vega/base02#2, drawCounts: 12
=== time: 13, textures/shared_vega/base02#3, drawCounts: 54
=== time: 14, textures/shared_vega/base02#4, drawCounts: 84
=== time: 14, textures/shared_vega/base02#5, drawCounts: 54
=== time: 4, textures/shared_vega/base02#6, drawCounts: 12
=== time: 18, textures/shared_vega/trim02a#0, drawCounts: 18
=== time: 19, textures/shared_vega/panel06_300#0, drawCounts: 30
=== time: 7, textures/shared_vega/panel06_300#1, drawCounts: 36
=== time: 6, textures/shared_vega/panel06_300#2, drawCounts: 36
=== time: 30, textures/shared_vega/trim03#0, drawCounts: 240
=== time: 11, textures/shared_vega/trim03#1, drawCounts: 120
=== time: 28, textures/shared_vega/trim03#2, drawCounts: 108
=== time: 21, textures/shared_vega/trim03#3, drawCounts: 72
=== time: 33, textures/shared_vega/trim03b#0, drawCounts: 78
=== time: 48, textures/shared_vega/concrete01#0, drawCounts: 633
=== time: 10, textures/shared_vega/concrete01#1, drawCounts: 84
=== time: 15, textures/shared_vega/concrete01#2, drawCounts: 75
=== time: 14, textures/shared_vega/concrete01#3, drawCounts: 84
=== time: 23, textures/shared_vega/concrete01#4, drawCounts: 303
=== time: 8, textures/shared_vega/concrete01#5, drawCounts: 48
=== time: 15, textures/shared_vega/concrete01#6, drawCounts: 24
=== time: 12, textures/shared_vega/concrete01#7, drawCounts: 33
=== time: 8, textures/shared_vega/concrete01#8, drawCounts: 126
=== time: 18, textures/shared_vega/concrete01#9, drawCounts: 48
=== time: 24, textures/shared_vega/concrete01#10, drawCounts: 195
=== time: 19, textures/shared_vega/concrete01#11, drawCounts: 207
=== time: 9, textures/shared_vega/concrete01#12, drawCounts: 18
=== time: 19, textures/shared_vega/concrete01#13, drawCounts: 174
=== time: 34, textures/shared_vega/trim01a#0, drawCounts: 84
=== time: 19, textures/shared_vega/trim01a#1, drawCounts: 12
=== time: 11, textures/shared_vega/trim01a#2, drawCounts: 72
=== time: 117, models/mapobjects/vega/globe/globe#0, drawCounts: 1260
=== time: 2826, models/mapobjects/vega/container/container2#0, drawCounts: 276
=== time: 40, models/mapobjects/vega/container/container2#1, drawCounts: 276
=== time: 29, textures/shared_vega/floor02#0, drawCounts: 36
=== time: 55, textures/shared_vega/floor02#1, drawCounts: 36
=== time: 10, textures/shared_vega/floor02#2, drawCounts: 18
=== time: 15, textures/shared_vega/floor02#3, drawCounts: 36
=== time: 1812, textures/shared_vega/floor01#0, drawCounts: 51
=== time: 33, textures/shared_vega/floor01#1, drawCounts: 195
=== time: 9, textures/shared_vega/floor01#2, drawCounts: 27
=== time: 11, textures/shared_vega/floor01#3, drawCounts: 12
=== time: 11, textures/shared_vega/floor01#4, drawCounts: 27
=== time: 14, textures/shared_vega/floor01#5, drawCounts: 24
=== time: 11, textures/shared_vega/floor01#6, drawCounts: 12
=== time: 1575, textures/shared_vega/dirt01#0, drawCounts: 6
=== time: 23, textures/shared_vega/dirt01#1, drawCounts: 6
=== time: 1656, textures/shared_vega/light03_1500#0, drawCounts: 36
=== time: 1570, textures/shared_vega/light03_1500#1, drawCounts: 30
=== time: 1893, textures/shared_vega/panel05_300#0, drawCounts: 72
=== time: 26, textures/shared_vega/panel05_300#1, drawCounts: 18
=== time: 26, textures/shared_vega/panel02#0, drawCounts: 18
=== time: 17, textures/shared_vega/asphalt01#0, drawCounts: 36
=== time: 42, models/mapobjects/vega/monitor/display_door_red#0, drawCounts: 6
=== time: 10, models/mapobjects/vega/monitor/display_door_blue#0, drawCounts: 6
=== time: 1817, models/mapobjects/vega/monitor/monitor#0, drawCounts: 204
=== time: 41, models/mapobjects/vega/emitter/emitter#0, drawCounts: 240
=== time: 1946, textures/vega_custom/starchart02#0, drawCounts: 6
=== time: 62, textures/vega_custom/roadstrip#0, drawCounts: 12
=== time: 29, textures/vega_custom/wheeltracks#0, drawCounts: 72
=== time: 31, textures/vega_custom/vega_banner#0, drawCounts: 48
=== time: 30, textures/shared_vega/grate01#0, drawCounts: 90
=== time: 1548, textures/shared_vega/grate01#1, drawCounts: 60
=== time: 27, textures/shared_vega/grate01#2, drawCounts: 60
=== time: 64, textures/vega_custom/holo_projector#0, drawCounts: 48
=== time: 25, textures/shared_vega/glass01#0, drawCounts: 12
=== time: 2, textures/shared_vega/glass01#1, drawCounts: 6
=== time: 9, textures/shared_vega/glass01#2, drawCounts: 36
=== time: 8, textures/shared_vega/glass01#3, drawCounts: 18
=== time: 4, textures/shared_vega/glass01#4, drawCounts: 12
=== time: 5, textures/shared_vega/glass01#5, drawCounts: 6
=== time: 1, textures/shared_vega/glass01#6, drawCounts: 126
=== time: 24, textures/shared_vega/glass01#0, drawCounts: 12
=== time: 9, textures/shared_vega/glass01#1, drawCounts: 6
=== time: 15, textures/shared_vega/glass01#2, drawCounts: 36
=== time: 8, textures/shared_vega/glass01#3, drawCounts: 18
=== time: 62, textures/shared_vega/glass01#4, drawCounts: 12
=== time: 9, textures/shared_vega/glass01#5, drawCounts: 6
=== time: 1524, textures/shared_vega/glass01#6, drawCounts: 126
=== time: 73, textures/shared_vega/glass01#0, drawCounts: 12
=== time: 5, textures/shared_vega/glass01#1, drawCounts: 6
=== time: 15, textures/shared_vega/glass01#2, drawCounts: 36
=== time: 7, textures/shared_vega/glass01#3, drawCounts: 18
=== time: 10, textures/shared_vega/glass01#4, drawCounts: 12
=== time: 5, textures/shared_vega/glass01#5, drawCounts: 6
=== time: 20, textures/shared_vega/glass01#6, drawCounts: 126
=== layout numComponents: 3, componentType: 0x1406, normalize: 0, stride: 32
=== layout numComponents: 4, componentType: 0x140b, normalize: 0, stride: 32
=== layout numComponents: 4, componentType: 0x1401, normalize: 1, stride: 32
=== time: 51, textures/shared_vega/glass01#0, drawCounts: 6

And 0x1402 is GL_SHORT and 0x1401 is GL_UNSIGNED_BYTE and the R300 limitations are said to be:

Vertex formats GL_*INT and GL_DOUBLE are not supported. GL_*SHORT is supported only for 2- and 4-component vertex attributes, and GL_*BYTE only for 4-component attributes. All individual vertex attribute fetches must be DWORD-aligned. Quads and quadstrips cannot have the first vertex be the provoking vertex.

It looks like everything looks good.
Well I don't know why there are some 0x140B (GL_HALF_APPLE ???) and 0x1406 (GL_FLOAT) but I'm not sure this is used, there is no Tess_DrawElements call immediately following them. And other things done in tr_vbo.cpp are setting GL_HALF with 4 components, which is said to be OK.

Well, maybe the thing is the usage of GL_HALF_FLOAT, in ioq3 renderergl2 tr_vbo.c, there is no GL_HALF_FLOAT set for TEXCOORD, but GL_FLOAT, if I do the same in our tr_vbo.cpp I obviously get wrong textures (I assume there is a mismatch with some half float functions used there and there), but, I get almost 48fps (even 50fps with r_smp 1), which is the performance I achieve with ioq3 renderergl2. Maybe the r300 driver lies about the support of ARB_half_float_vertex and emulates it in our back?
With GL_FLOAT and r_smp 0: 48fps:

With GL_FLOAT and r_smp 1: 50fps:

With GL_FLOAT and r_smp 1 on Thunder, 48fps:

The single change that recovers the performance (while breaking the texture rendering) is to do:
--- a/src/engine/renderer/tr_vbo.cpp
+++ b/src/engine/renderer/tr_vbo.cpp
@@ -220,7 +220,7 @@ static void R_SetAttributeLayoutsStatic( VBO_t *vbo )
        vbo->attribs[ ATTR_INDEX_QTANGENT ].frameOffset   = 0;

        vbo->attribs[ ATTR_INDEX_TEXCOORD ].numComponents = 4;
-       vbo->attribs[ ATTR_INDEX_TEXCOORD ].componentType = GL_HALF_FLOAT;
+       vbo->attribs[ ATTR_INDEX_TEXCOORD ].componentType = GL_FLOAT;
        vbo->attribs[ ATTR_INDEX_TEXCOORD ].normalize     = GL_FALSE;
        vbo->attribs[ ATTR_INDEX_TEXCOORD ].ofs           = offsetof( shaderVertex_t, texCoords );
        vbo->attribs[ ATTR_INDEX_TEXCOORD ].realStride    = sizeShaderVertex;

Two years ago I started a work-in-progress branch to support graphics cards not having support for ARB_half_float_vertex, like some Intel GL 2.1 cards. I haven't found time to touch it before, especially because my only sample for that Intel card is at some hundreds of km of here I live, so testing was a bit limited.
But preparatory work for it was already merged:

Commits improving our type system, helping the compiler to report more type errors and then making the conversion easier with the less risk of introcing silent errors:
https://github.com/DaemonEngine/Daemon/pull/728
Some enablement of GL 2.1 on the said Intel graphics chip so we can know GL 2.1 is supported but catch the lack of the half float vertex extension, meaning that if we implement a workaround one day (that is the day today), we would already have everything else already in place for it:
https://github.com/DaemonEngine/Daemon/pull/478

I revived this branch and worked on it a bit more to make it work (it is still in a very rough state), given I wanted to check if using that on an ATI r300 would improve the performances…
Et voilà!  🎉 I now get 55fps on the default Vega spectator scene:

And 53fos on default Thunder spectator scene:

And I guess I fixed the support for those old GL 2 Intel cards in the process (I may be able to verify it with real hardware in the coming months). 😎
I assume the r300 driver just emulates half-float vertexes, as it is said it is hardware limitation to not support GL_HALF_FLOAT as component type for a vertex, while the driver accepts it. This is consistent with the u_vbuf_translate_buffers  function name we can see in the call trace. 🙂

Is there some necessary reason why the driver has to implement this in the dumbest possible way? I.e. re-translating the attributes on every frame instead of when the VBO is created or used for the first time?
Maybe we could implement attribute reformatting at the last minute like the driver does, instead of modifying all our structs. It appears we have all the struct layouts stored in a tabular format (vbo->attribs). This provides all the information we would need to create a new array on the fly with some component stored as a different type.

If we know that some data stays the same but the driver doesn't, then we would only have to translate it once, which should fix the performance.

Ah, yea, that would work, I misunderstood "on the fly" as "per frame".

Is there some necessary reason why the driver has to implement this in the dumbest possible way? I.e. re-translating the attributes on every frame instead of when the VBO is created or used for the first time?

I will probably report the issue on Mesa side at some point. Something looks weird indeed. Maybe they can do better and providing them our game as a testbed may help.

Maybe we could implement attribute reformatting at the last minute like the driver does, instead of modifying all our structs. It appears we have all the struct layouts stored in a tabular format (vbo->attribs). This provides all the information we would need to create a new array on the fly with some component stored as a different type.

This is currently a very naïve implementation and some conversions may be useless. Also it may indentifies that some data model are badly shaped. Before I touched anything there was already multiple places where some half-float were converted to float for processing then later re-converted to half-float, and we may decide to keep everything of this as float before the latest storage step, which would not only avoid duplication of some code to support both float and half-float, but also would make faster the original half-float code.

Is there some necessary reason why the driver has to implement this in the dumbest possible way?

I investigated my question a bit and found one possibility... In case your R300 does not have the GL_ARB_buffer_storage extension, try the slipher/glbufferdata-init branch. (If it does have the extension, I guess you could still try it by disabling the cvar r_arb_buffer_storage.) With glBufferData we use the GL_STATIC_DRAW hint which is supposed to inform the driver that the contents will not be changed. But maybe due to the way the buffer is initialized, the driver sets some user-is-an-idiot flag and ignores the hint. The patch ensures to populate the buffer at the moment of initialization instead of shortly after.

@slipher Running slipher/glbufferdata-init doesn't speed-up anything, even when disabling r_arb_buffer_storage.

Those hints are very unreliable, the driver is free to just completely ignore them.


Multiple Browser opened at the same time

Hello Guys,
I am experiencing this consistent error where in one of my application is open in chrome and all the menus are showing as it should be. The user in chrome is a front end user of the application. When I open another instance of my application in Safari and logged in as a back end user, then go back to chrome and hit refresh, the menus disappear.
Any Idea what's causing it?
Regards,
Mark

Not sure. There were issues like this in v3 because of shared caching between users.
Could you create a demo application with the behavior so I can take a look?

Were you able to work out this issue?

Closing for lack of response for more than 2 months.


Add dot markers for day

Please, add ability to add events to date
Small dots like this

Hi,
you can already do this for separate day by using WeekDayPicker.setDateIndicator(LocalDate date, boolean enabled) method.
You can si an example in libraries example project.


[Snyk] Security upgrade next-auth from 3.29.0 to 3.29.9

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
yarn.lock

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

451/1000  Why? Recently disclosed, Has a fix available, CVSS 3.3
Information Exposure SNYK-JS-NEXTAUTH-2965597
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

Closing this PR as there is already another to migrate to 3.29.10 which is the latest patch


Peg compile fails with pegjs 0.90

Hi John!
First of all congrats for the hard work to do the the port!
StringTemplate is one of my favourite pieces of software and I am delighted to see it ported to JS. I will happy to help with testing and occasional PRs.
I am testing it and fails for me at build time. Compiles with pegjs 0.80 but fails with pegjs v. 0.90. I have the following errors on the grammar:
cd compiler

pegjs --allowed-start-rules groupFile,templateFile,templateFileRaw,templateAndEOF stGrammar.pegjs
213:15: Expected "!", "$", "&", "(", ".", character class, comment, end of line, identifier, literal or whitespace but "{" found.

The problem appears not only here but in all other empty expressions for error handling.
grunt-peg 2.0.0 relies also on pegjs ~0.9.0
It looks like a grammar refactor is needed to support pegjs 0.9.0.

Thanks for the report. I guess the workaround for now is to use 0.8 version. I'll mark as a bug but it will be a while before I can get to work on this again.


ImportError: DLL load failed: %1 is not a valid Win32 application on 64 bit Python

Hello,
I am running Python 3.7, 64 bit. When I try to run_mission.py, I get "ImportError: DLL load failed: %1 is not a valid Win32 application."
Additionally, I have "C:\Program Files (x86)\CodeSynthesis XSD 4.0\bin64" in my PATH. What is going on?
Thanks!

hi，I got this problem, have you work out this?


Why did you remove the Daum map?

I'd like to use Daum map.
I wonder why you removed it.

Daum emailed me that I can use Daum map tiles only by using Daim map api, so I removed it for now. But, I am going to find another way to use it on Leaflet sooner or later.


Block TRE access to Terraform/Hashicorp domains

Resolves #2445
What is being addressed
With all bundles implementing Terraform provider mirroring it's time to start blocking TRE communication to Terraform/Hasihcorp domains.
Migration
It's advised to upgrade your firewall to the new 0.5.0 version if all your deployed tre resources are at (or above) the versions below.
If you have created and deployed custom templates that use Terraform, you need to make sure you mirror providers. Look at the dockerfile.tmpl of one our templates for an example.
The method to do this upgrade is manual - upgrade the templateVersion of tre-shared-service-firewall resource in Cosmos to 0.5.0

template name
version

tre-workspace-base
0.3.28

tre-workspace-unrestricted
0.1.9

tre-service-mlflow
0.3.7

tre-service-innereye
0.3.5

tre-workspace-service-gitea
0.3.8

tre-workspace-service-mysql
0.1.2

tre-service-guacamole-linuxvm
0.4.13

tre-service-guacamole-windowsvm
0.4.8

tre-service-guacamole
0.4.5

tre-user-resource-aml-compute-instance
0.3.2

tre-service-azureml
0.4.8

tre-shared-service-cyclecloud
0.2.6

tre-shared-service-gitea
0.3.14

tre-shared-service-airlock-notifier
0.1.2

tre-shared-service-certs
0.1.3

tre-shared-service-sonatype-nexus
2.1.6

tre-shared-service-firewall
0.4.3

/test-extended

/test-extended

/test-extended


Possible route collision bug

Summary
It seems that we have ran into a really bizarre route (collision?) bug.
Given two routes - /e and /example - if one does not have any methods defined on the first one, while the second has a ["GET" ...], when hitting /example, kong will forward the request to the upstream of /e with the request URI set to /xample (yes, without an e).
Steps To Reproduce

Run two http servers -- one on :8080, one on :8181
Configure two API's in kong as follows:

  --url http://localhost:8001/apis/ \
  --data 'name=example-api' \
  --data uris=/example-api \
  --data preserve_host=true \
  --data 'upstream_url=http://localhost:8080'

curl -i -X POST \
  --url http://localhost:8001/apis/ \
  --data 'name=e' \
  --data uris=/e \
  --data preserve_host=true \
  --data 'upstream_url=http://localhost:8181'\
  --data 'methods=GET'

Hit /e via kong; everything should work as expected. Inbound request on first server will look something like this:

----- Request Start ----->

/
Host: localhost
Connection: keep-alive
X-Forwarded-For: <IP_ADDRESS>
X-Forwarded-Proto: http
X-Forwarded-Host: localhost
X-Forwarded-Port: 80
X-Real-IP: <IP_ADDRESS>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Upgrade-Insecure-Requests: 1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.8,ca;q=0.6
Cookie: foo=bar

<----- Request End -----

Now hit /example-api; you would expect it to go to /example-api on :8080, but you get delivered to the server on :8181 (w/ /xample-api ???).

The output of the request on the upstream of /e looks something like this:
----- Request Start ----->

/xample-api
Host: localhost
Connection: keep-alive
X-Forwarded-For: <IP_ADDRESS>
X-Forwarded-Proto: http
X-Forwarded-Host: localhost
X-Forwarded-Port: 80
X-Real-IP: <IP_ADDRESS>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Upgrade-Insecure-Requests: 1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.8,ca;q=0.6
Cookie: foo=bar

<----- Request End -----

Additional Details & Logs

Kong version ($ kong version)

LUAROCKS_VERSION=2.4.1
KONG_VERSION=0.11.0
SERF_VERSION=0.8.1

Kong debug-level startup logs ($ kong start --vv)

2017/10/10 18:01:22 [debug] ngx_lua: 10008
2017/10/10 18:01:22 [debug] nginx: 1011002
2017/10/10 18:01:22 [debug] Lua: LuaJIT 2.1.0-beta2
2017/10/10 18:01:22 [verbose] reading config file at /etc/kong/kong.conf
2017/10/10 18:01:22 [debug] KONG_SSL_CERT_KEY ENV found with "/usr/local/kong/ssl/server.key"
2017/10/10 18:01:22 [debug] KONG_PG_USER ENV found with "kong"
2017/10/10 18:01:22 [debug] KONG_PG_HOST ENV found with "postgres-94"
2017/10/10 18:01:22 [debug] KONG_PROXY_LISTEN ENV found with "<IP_ADDRESS>:80"
2017/10/10 18:01:22 [debug] KONG_DATABASE ENV found with "postgres"
2017/10/10 18:01:22 [debug] KONG_PROXY_LISTEN_SSL ENV found with "<IP_ADDRESS>:443"
2017/10/10 18:01:22 [debug] KONG_SSL_CERT ENV found with "/usr/local/kong/ssl/server.crt"
2017/10/10 18:01:22 [debug] KONG_NGINX_DAEMON ENV found with "off"
2017/10/10 18:01:22 [debug] KONG_PG_PASSWORD ENV found with "******"
2017/10/10 18:01:22 [debug] admin_access_log = "logs/admin_access.log"
2017/10/10 18:01:22 [debug] admin_error_log = "logs/error.log"
2017/10/10 18:01:22 [debug] admin_http2 = false
2017/10/10 18:01:22 [debug] admin_listen = "<IP_ADDRESS>:8001"
2017/10/10 18:01:22 [debug] admin_listen_ssl = "<IP_ADDRESS>:8444"
2017/10/10 18:01:22 [debug] admin_ssl = true
2017/10/10 18:01:22 [debug] anonymous_reports = true
2017/10/10 18:01:22 [debug] cassandra_consistency = "ONE"
2017/10/10 18:01:22 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
2017/10/10 18:01:22 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2017/10/10 18:01:22 [debug] cassandra_keyspace = "kong"
2017/10/10 18:01:22 [debug] cassandra_lb_policy = "RoundRobin"
2017/10/10 18:01:22 [debug] cassandra_port = 9042
2017/10/10 18:01:22 [debug] cassandra_repl_factor = 1
2017/10/10 18:01:22 [debug] cassandra_repl_strategy = "SimpleStrategy"
2017/10/10 18:01:22 [debug] cassandra_schema_consensus_timeout = 10000
2017/10/10 18:01:22 [debug] cassandra_ssl = false
2017/10/10 18:01:22 [debug] cassandra_ssl_verify = false
2017/10/10 18:01:22 [debug] cassandra_timeout = 5000
2017/10/10 18:01:22 [debug] cassandra_username = "kong"
2017/10/10 18:01:22 [debug] client_body_buffer_size = "8k"
2017/10/10 18:01:22 [debug] client_max_body_size = "0"
2017/10/10 18:01:22 [debug] client_ssl = false
2017/10/10 18:01:22 [debug] custom_plugins = {"nginx-log","helloworld-hdr","redirect","requestid","external","requirejwt","xsrf","418","authredir","cache-until-events"}
2017/10/10 18:01:22 [debug] database = "postgres"
2017/10/10 18:01:22 [debug] db_cache_ttl = 3600
2017/10/10 18:01:22 [debug] db_update_frequency = 5
2017/10/10 18:01:22 [debug] db_update_propagation = 0
2017/10/10 18:01:22 [debug] dns_error_ttl = 1
2017/10/10 18:01:22 [debug] dns_hostsfile = "/etc/hosts"
2017/10/10 18:01:22 [debug] dns_no_sync = false
2017/10/10 18:01:22 [debug] dns_not_found_ttl = 30
2017/10/10 18:01:22 [debug] dns_order = {"LAST","SRV","A","CNAME"}
2017/10/10 18:01:22 [debug] dns_resolver = {}
2017/10/10 18:01:22 [debug] dns_stale_ttl = 4
2017/10/10 18:01:22 [debug] error_default_type = "text/plain"
2017/10/10 18:01:22 [debug] http2 = false
2017/10/10 18:01:22 [debug] latency_tokens = true
2017/10/10 18:01:22 [debug] log_level = "notice"
2017/10/10 18:01:22 [debug] lua_code_cache = "on"
2017/10/10 18:01:22 [debug] lua_package_cpath = ""
2017/10/10 18:01:22 [debug] lua_package_path = "?/init.lua;./kong/?.lua"
2017/10/10 18:01:22 [debug] lua_socket_pool_size = 30
2017/10/10 18:01:22 [debug] lua_ssl_trusted_certificate = "/usr/local/kong/ssl/server.crt"
2017/10/10 18:01:22 [debug] lua_ssl_verify_depth = 1
2017/10/10 18:01:22 [debug] mem_cache_size = "128m"
2017/10/10 18:01:22 [debug] nginx_daemon = "off"
2017/10/10 18:01:22 [debug] nginx_optimizations = true
2017/10/10 18:01:22 [debug] nginx_user = "nobody nobody"
2017/10/10 18:01:22 [debug] nginx_worker_processes = "auto"
2017/10/10 18:01:22 [debug] pg_database = "kong"
2017/10/10 18:01:22 [debug] pg_host = "postgres-94"
2017/10/10 18:01:22 [debug] pg_password = "******"
2017/10/10 18:01:22 [debug] pg_port = 5432
2017/10/10 18:01:22 [debug] pg_ssl = false
2017/10/10 18:01:22 [debug] pg_ssl_verify = false
2017/10/10 18:01:22 [debug] pg_user = "kong"
2017/10/10 18:01:22 [debug] prefix = "/usr/local/kong/"
2017/10/10 18:01:22 [debug] proxy_access_log = "logs/access.log"
2017/10/10 18:01:22 [debug] proxy_error_log = "logs/error.log"
2017/10/10 18:01:22 [debug] proxy_listen = "<IP_ADDRESS>:80"
2017/10/10 18:01:22 [debug] proxy_listen_ssl = "<IP_ADDRESS>:443"
2017/10/10 18:01:22 [debug] real_ip_header = "X-Real-IP"
2017/10/10 18:01:22 [debug] real_ip_recursive = "off"
2017/10/10 18:01:22 [debug] server_tokens = true
2017/10/10 18:01:22 [debug] ssl = true
2017/10/10 18:01:22 [debug] ssl_cert = "/usr/local/kong/ssl/server.crt"
2017/10/10 18:01:22 [debug] ssl_cert_key = "/usr/local/kong/ssl/server.key"
2017/10/10 18:01:22 [debug] ssl_cipher_suite = "modern"
2017/10/10 18:01:22 [debug] ssl_ciphers = "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256"
2017/10/10 18:01:22 [debug] trusted_ips = {}
{"level":"fatal","method":"main","msg":"lookup dd-statsd on <IP_ADDRESS>:53: no such host","time":"2017-10-10T18:01:23Z"}
2017/10/10 18:01:23 [notice] 41#41: using the "epoll" event method
2017/10/10 18:01:23 [notice] 41#41: openresty/<IP_ADDRESS>
2017/10/10 18:01:23 [notice] 41#41: built by gcc 6.3.0 (Alpine 6.3.0)
2017/10/10 18:01:23 [notice] 41#41: OS: Linux 4.9.36-moby
2017/10/10 18:01:23 [notice] 41#41: getrlimit(RLIMIT_NOFILE): 4096:4096
2017/10/10 18:01:23 [notice] 41#41: start worker processes
2017/10/10 18:01:23 [notice] 41#41: start worker process 49
2017/10/10 18:01:23 [notice] 41#41: start worker process 50
2017/10/10 18:01:23 [notice] 41#41: start worker process 51
2017/10/10 18:01:23 [notice] 41#41: start worker process 52

Kong error logs (<KONG_PREFIX>/logs/error.log)

None

Kong configuration (registered APIs/Plugins & configuration file)

{
    "created_at":<PHONE_NUMBER>000,
    "strip_uri": true,
    "id": "ef197831-08f7-4772-aa3d-95f961190678",
    "name": "example-api",
    "http_if_terminated": false,
    "https_only": false,
    "upstream_url": "http://localhost:8080",
    "uris": [
        "/example-api"
    ],
    "preserve_host": true,
    "upstream_connect_timeout": 60000,
    "upstream_read_timeout": 60000,
    "upstream_send_timeout": 60000,
    "retries": 5
},
{
    "created_at":<PHONE_NUMBER>000,
    "strip_uri": true,
    "id": "04be0978-f98e-45f0-ae00-eda1050f283f",
    "name": "e",
    "methods": [
        "GET",
        "POST"
    ],
    "http_if_terminated": false,
    "https_only": false,
    "upstream_url": "http://localhost:8181",
    "uris": [
        "/e"
    ],
    "preserve_host": true,
    "upstream_connect_timeout": 60000,
    "upstream_read_timeout": 60000,
    "upstream_send_timeout": 60000,
    "retries": 5
}

Operating System

Linux 36669050a8bb 4.9.36-moby #1 SMP Wed Jul 12 15:29:07 UTC 2017 x86_64 Linux
alpine-release: 3.6.2

Note: We've been able to get around this issue by setting both routes to have explicit allowed methods. It appears this issue only occurs if one route has implicit methods and another route explicit methods.
Secondly - this issue occurs ONLY if the second route's URI is a subset of the first route. Let me write up the scenarios we've tested.
Buggy behavior:
Route 1: /example-api, Methods defined: None
Route 2: /e, Methods defined: ["GET"]
Not buggy behavior:
Route 1: /example-api, Methods defined: ["GET"]
Route 2: /e, Methods defined: ["GET"]
Not buggy behavior:
Route 1: /example-api, Methods defined: None
Route 2: /e, Methods defined: None
Not buggy behavior:
Route 1: /example-api, Methods defined: None
Route 2: /eb, Methods defined: ["GET"]
^^^ Note that this last example illustrates that the 2nd route's URI being a subset of the 1st route's URI has an effect on the buggy behavior.
A workaround (we have not fully tested yet), is to always define allowed methods for all API's (and not rely on implicit allowed methods).
Please let me know if I can provide any other info.
TIA

Hi @dselans,
Thanks for the report. I was indeed able to reproduce on our latest release 0.11.1.

Added to our internal tracking tools, we intend to fix this for our 0.12 release, or, potentially a 0.11.2 release, if 0.12 gets delayed too much. And as always: we also accept contributions... 😉
Thanks!

After spending some time and spawning a few reproducible test cases, I am afraid that I'll be backtracking on my previous statement that this was a buggy behavior, and actually affirm that what you are seeing is the intended behavior of the router. Sorry for not seeing it sooner. Explanation:

Let's re-affirm the postulate that when not specifying regexes in the uris field, matching is evaluated by prefix.
That is, if we have uris=/e and uris=/example, both would match  a given request if its URL is /example.
APIs are evaluated in a specific orders: when an API has more matching attributes than another, it is evaluated for matching before. An API with uris+methods will be evaluated before an API with only uris.
Hence, when you make the following request: GET /example, the router finds that the API with uris=/e + methods=GET is a perfectly valid match, and rightfully so.

It seems you have setup conflicting routes, at least for GET methods.
If you are in doubt regarding how the router works, or if you want to experiment with URI regexes to circumvent this mis-configuration, feel free to have a look at our Proxying Guide, which covers the workings of the Kong's router.
I'll be closing this now, hoping to have shed some light on what is going on here. Thank you for the report, and sorry again for the confusion!


[Discussion] Rename CharacterStylesPopupPlugin to FloatingToolbar?

It always takes me 30 ages to find this plugin, I wonder if we should rename it

may be FloatingFormatter?

We have other floating toolbars some maybe something more specific like TextFormatFloatingToolbar?

TextFormatFloatingToolbar -> FloatingTextFormatToolbar may be? It would be easy to grasp if floating was at the start?

Closed by #2456


Question: Do I have to use Flash-Attention all the way from pretrain and finetune and inference ? And if so can I quantize with AutoGPTQ after all ?

Check before submitting issues

[X] Make sure to pull the latest code, as some issues and bugs have been fixed.
[X] I have read the Wiki and FAQ section AND searched for similar issues and did not find a similar problem or solution
[X] Third-party plugin issues - e.g., llama.cpp, LangChain, text-generation-webui, we recommend checking the corresponding project for solutions

Type of Issue
Model training and fine-tuning
Base Model
Chinese-Alpaca-2-16K (7B/13B)
Operating System
Linux
Describe your issue in detail
There is no issue, it is a question as stated on the title:

If I use Flash-Attention-2, do I have to use Flash-Attention-2 all the way from pretrain and finetune and then inference ?
If I do use Flash-Attention as (1) above, can I quantize with AutoGPTQ after training for faster inference ?

Thanks for great repo.
Steve
Dependencies (must be provided for code-related issues)
Flash-Attention-2
AutoGTPQ
Execution logs or screenshots
None.

@tri the author of FlashAttention already answer here
Cheers,
Steve


Networks: Adds restricted.networks.access setting

[x] Docs.
[x] Restrict API access to networks specified in restricted.networks.access project config if restricted=true.
[x] Restrict usage of networks in instance NIC devices.
[x] Tests.

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.10866/

jenkins: test this please

jenkins: test this please

jenkins: test this please


Adding AutoRefresh for token refresh

Coverage increased (+0.006%) to 88.068% when pulling f5ca941892f4658545ed7763e854f50e48a90cb0 on sthang:develop into 88ab83968a2f901513410fbf5af5e8d37585a323 on intuit:develop.

@sthang : Thanks for the PR 👏 . Have a couple of questions with your implementation :

I noticed that as part of the createToken method, you are doing a check to see if the autoRefresh is enabled and if YES, the client sets up the autoRefresh. This point forward depending on the autoRefreshIntervalInSeconds field the auto-refresh of tokens goes on until its killed explicitly. But what if there is a call made to OAuthClient.prototype.refresh explicitly ? Will it process the current refresh request into a Queue ?

You have updated the sample to stopAutoRefresh on demand as shown here. But the actual stopRefresh() method is missing on the client. were you planning on updating it later?

@abisalehalliprasan : Thanks for the review.

No. If refresh is called explicitly it will be independent of the autoRefresh and has no impact on the timer. I thought about it and made it independent to keep the implementation simple. The alternative is to reset the timer on setInterval when refresh is called outside of autoRefresh. What do you think?

Here's the stopRefresh on the OAuthClient. The sample app is calling it on the oauthClient.

@sthang :
1.) We do not want the explicit token refresh call to coincide with the autoRefresh. The workaround seems fine but there is a one-off edge case where the two API calls might coincide(the probability is very low 😃). I will see if I could implement Queue logic here.
Could you close this PR and create a PR for the branch autoRefresh . Apologize for the re-do, I need to test this feature before actually releasing it. Thanks @sthang

No problem. I'll reopen the PR with the branch autoRefresh.


Failed to set syscore CPU time limit: D8E05BF4

launching fbi from hbl give me this whithin a black screen
My Error is as follows:
"Fbi has encountered a fatal error!"
"Failed to set syscore CPU time limit: D8E05BF4"
"Press any button to exit."
i'm using the latest version on 9.2 i have CFW

Are there any unusual characteristics to the environment you're running FBI in? It seems that, for whatever reason, the syscore CPU time limit maximum is lower than usual.

Are there any unusual characteristics to the environment you're running FBI in?

I have a lot of problem actually and whatever i look for a solution i end i a new one

I'm actually in a wiered situation:
-I don't have healt and safety app on my home
-injectig fbi give me succes but no fbi appear on reboot
-using hbl give me the error i posted
looks like there's no way for me to lauch fbi

I solved following this http://emulators128.rssing.com/chan-51395358/all_p220.html
Open FBI from hbl and install fbi.cia


Check $log output when running tests

Might be helpful when compiling templates, they often print warning messages when something is missing (e.g. ARIA labels)

Current coverage is 97.99% (diff: 100%)

Merging #168 into master will increase coverage by 0.18%

@@             master       #168   diff @@
==========================================
  Files           100        100
  Lines          1324       1449   +125
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1295       1420   +125
  Misses           29         29
  Partials          0          0

Powered by Codecov. Last update 9e0ffde...bdbbef8


support for multiple cursors

support for multiple cursors
moving each cursor back into quotes "|"

Good stuff! I just tested, works well. Thank you. We'll release very soon.

0.6.0 released! @alexfabianoricioli check out the contributors table at the bottom of readme! 🥇


Issue/136 Support array argument for createSelector.

Sadly, I can't find a way to support either format without duplicating the same approach taken for the multiple-argument signature. The definition file is now 10X bigger than the library itself. :(
Fix some eslint complaints.
Use trailing commas consistently.
It's possible there's a way to do this with ...args: Selector<>[], but I can't figure out how to preserve the selector / combiner return/argument pairing with that approach. Changes to Typescript 2.1 (supporting object spread) might open up some possibilities here.

Coverage remained the same at 100.0% when pulling 9bda1cc066fe94364431895e88c2bfe09d1f3cfd on threehams:master into 2f1a9673857a4bed90ab46d4d0fe275fabecbf3d on reactjs:master.

[Current coverage][cc-pull] is 100%

Merging [#143][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #143   diff @@
====================================
  Files           1      1
  Lines          13     13
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits           13     13
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last updated by [2f1a967...9bda1cc][cc-compare]
[cc-base-branch]: https://codecov.io/gh/reactjs/reselect/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/reactjs/reselect/compare/2f1a9673857a4bed90ab46d4d0fe275fabecbf3d...9bda1cc066fe94364431895e88c2bfe09d1f3cfd
[cc-pull]: https://codecov.io/gh/reactjs/reselect/pull/143?src=pr

I guess the size of the definition file doesn't really matter, kind of funny though! What needs to be done to get this merged? Are you looking for someone else to review it first?

@threehams By the way, just gave you publish rights on NPM if you need to make a release.

Thanks. It'd be good to have another pair of eyes on this - it's working well in a smaller project I'm using, but there may be a better way to handle this.
@geon - think you could take a look?

This would help remove some duplication, but it's only a proposal for now:
https://github.com/Microsoft/TypeScript/issues/5296

@threehams: Yeah, it looks good to me. Haven't tried it. I noticed a redundant definition, though.

Hey @aikoven and @ulfryk, I hope you don't mind me pinging you. I see you are the keepers of the Redux Typescript type definitions, and as Reselect is part of the Redux organisation I wondered if you could spare a little time to look at this PR too, it would be much appreciated. No problem if you don't have time, I realise everyone is really busy, but I figured it was worth a try!

Closing to reopen against 3.0.0: https://github.com/reactjs/reselect/pull/148

@ellbee Looks good to me.

Thanks @aikoven!

I used the latest definition file, it still complains.

@beckend Make sure to replace the right definitions file. There is one in src and lib.
Is this fix going to be backported to version 2.5.x or will it only be available in 3.0.0?


Mouse scrolling is broken in the tilemap editor

After the new UI collision refactor, the tilemap scrolling was broken.

This is fixed


fix: broken dapps support url

Description
I forgot to update the branding hash after I added the new dapps support link, the CI was passing with silent errors in my branch, which i didn't notice. the CI correctly fails on main.
Test plan
n/a
Related issues

Fixes RET-550

Backwards compatibility
Y

@kathaypacific looking at the differences form the branch CI run and the main CI run.
Main: Test suite failed to run from DappList.spec.js is failing on the final test run, so CI is marked as failing.
Branch CI: the Test suite failed to run from DappList.spec.js is failing in the first run, along with a fail from QRScanner.spec.js. Detox then retries the failing specs, but the DappList.spec.js is not rerun in the second retry. So in the second retry, only the QRScanner.spec.js specs is run and passes.
It seems like an issue with Detox's --retries not picking up all failing specs https://github.com/wix/Detox/issues/3848
Silently Failing with Retries - Branch CI.

Test Run
Test Name
Test Result
Fail Type

1
QRScanner.spec.js
Fail
Timeout expired without matching of given matcher

1
DappList.spec.js
Fail
Test suite failed to run - Syntax Error

2
QRScanner.spec.js
Ok

2
DappList.spec.js
Not Run


Can't create a collection with namespace if folder with namespace already exists

Bug Report
What did you do?
I created a collection called namewith a namespace callednamespace. Then I tried to create a second collection with the same namespace (namespace`).
What did you expect to see?
It should create the second collection in the same folder.
What did you see instead? Under which circumstances?
The attempt to create the second collection failed. The core command `ansible-galaxy collection init COLLECTION_NAME.COLLECTION_NAMESPACE' seems to be the blame...

[!NOTE]
See Additional comments on issue.

Possible Solutions

It might be possible to handle this in the operator-sdk repo
Bar the user from creating collections in this circumstance or warn them
Create a bandaid solution that detects if the namespace folder exists, determines its current state as a collection or not , etc., creates an alternate uuid for the namespace behind the scenes so the command doesn't fail, then replaces all appropriate values with the proper namespace. This is a large workaround...

Additional context
The namespace is tied to multiple values in the collection like the domain and namsespace fields in the galaxy and operator-config files.

[!NOTE]
This was my user error. The command takes COLLECTION_NAMESPACE.COLLECTION_NAME as input and I had it reversed. My mistake.


Cloud Publishing error 422 "Compilation destination"

We have NAV2018 installed, created Extensions and published to OnPremise installations.
Works Fine.
Now we are signed up for Business Central and has created a Cloud Sandbox.
In VSC created a new project with al-objects.
Symbols downloaded fine.
Compilation is fine.
Creation of package is fine:
Output-message: "Success: The package is created."
But publishing fails with the error:
"The request for path /v1.0/sandbox/dev/apps?SchemaUpdateMode=recreate failed with code 422. Reason: Udvidelsen angiver en højere kompileringsdestination end tilladt."
(Reason can be translated to something like "The Extension states a higher compilation destination than allowed)
In FAQ I read that for NAV2018, AL Language Extension shall be from the NAV-installation, and for Cloud, AL Extension Language shall be from VS Code Marketplace.
Is this causing the error above ?
If so, how can we develop for OnPremise as well as Cloud ?
Shall we change uninstall / install the AL Language Extension each time we want to publish for one or the other platform ?

AL Extension Version:
AL Compiler version 0.12.17091

Server Version:
Cloud, Business Central

An extension is compatible with a given server. A NAv 2018 server will not work with the newest released August version of the AL extension for example.
This is the error message you have received. As a not too nice solution you can install the green (experimental VSCode, which is as stable as the blue one to my experience) and install the NAv 2018 AL extension there and use the blue one for the BC development, or vice-versa.

Hi,
Thanks a lot for the reply.
The green experimental VSCode, you are referring to, is that what is "officially" called
VS Code Insiders
which is found here: https://code.visualstudio.com/insiders/
?

Yes

Thanks.
Works fine :-)


Help

constexpr void NormalWalk(UserCmd* cmd) noexcept
{
cmd->buttons |= UserCmd::IN_MOVERIGHT;
cmd->buttons |= UserCmd::IN_MOVELEFT;
cmd->buttons |= UserCmd::IN_FORWARD;
cmd->buttons |= UserCmd::IN_BACK;

if (cmd->forwardmove > 0.0f);
cmd->buttons |= UserCmd::IN_FORWARD;
else if (cmd->forwardmove < 0.0f)
cmd->buttons |= UserCmd::IN_BACK;
if (cmd->sidemove > 0.0f);

{
	cmd->buttons |= UserCmd::IN_MOVERIGHT;
}
else if (cmd->sidemove < 0.0f)
{
	cmd->buttons |= UserCmd::IN_MOVELEFT;
}

}
hi i want to add this code but i don't understand else if
help?

It's just basic English
Else if means :
else plus there's a condition

This code makes no sense + it has syntax errors.

What is this function


Microservice:  Subscribe to Emergency Air Quality or Heat Index Alerts

Allow users to subscribe to emergency air quality or heat index alerts for devices that they have access to.
This gives users a way to take action based on bad air quality.

Oops, this was meant for SimpleAQ-Frontend


createFontPreview should not choose the font.

Font should be given as an argument.

Resolved with 0789c65432df1a7d4489d37629fd4e5689203eeb.


Add TypeScript typings

Hi! It would be nice to have TypeScript typings in this very useful package. If you've find an issues in the PR, feel free to point me :point_left:

Hi, folks! This PR fixes #6, so if anyone can merge, I will be very thankful :star2:

I get an error:

ERROR in /Users/[REDACTED]/src/static/ts/typings-custom/preact-redux/index.d.ts
(161,14): error TS2415: Class 'Provider' incorrectly extends base class 'Component<ProviderProps, {}>'.
  Types of property 'render' are incompatible.
    Type '(props: ProviderProps) => VNode' is not assignable to type '(props?: (ProviderProps & ComponentProps<this>) | undefined, state?: {} | undefined, context?: an...'.
      Types of parameters 'props' and 'props' are incompatible.
        Type '(ProviderProps & ComponentProps<this>) | undefined' is not assignable to type 'ProviderProps'.
          Type 'undefined' is not assignable to type 'ProviderProps'.

I commented it out, since I figured I could live without it, but then the typing is not recognized at all:
error TS7016: Could not find a declaration file for module 'preact-redux'.

Which version of Preact you use?
I have types working with 8.2.1. Here is my example:

interface IOwnProps {
    index: number;
}

interface IStateProps {
    type: string;
    place: string;
    visible: boolean;
}

export const MyComponent = (props: IOwnProps & IStateProps) =>
{ props.type }
;

const mapProps = (o: IOwnProps) => o;
const mapState = (s: IState, p: IOwnProps) => ({ ...s.list[p.index] });

export default connect(mapState, null, mapProps)(MyComponent);

I might be missing something here, but this does not decay the props like react-redux does.
Take the example here
interface LabelProps {
	content: string;
}

const Label = (props: LabelProps) => (

{props.content}

);

const mapStateToProps = (state: State) => ({
	content: state.theTextForTheLabel
});

const ConnectedLabel = PreactRedux.connect(mapStateToProps)(Label);

const App = () => (
	<PreactRedux.Provider store={store}>
		<ConnectedLabel /> // error here
	</PreactRedux.Provider>
)

Error:
'Type '{}' is not assignable to type 'LabelProps & ComponentProps<Component<LabelProps, any>>'.
  Type '{}' is not assignable to type 'LabelProps'.
    Property 'content' is missing in type '{}'.'

This is because the type of ConnectedLabel is Preact.ComponentConstructor<LabelProps, any> instead of Preact.ComponentConstructor<{}, any> or something similar.
I am not well enough versed to fully understand how the react-redux libray does it, but it seems like the InferableComponentEnhancerWithProps interface there is the key. It is removing the keys returned from the mapStateToProps function from the required props of the connected type.
I am of course coming from react-redux so preact-redux might work in a different way here and this is actually the expected behaviour, but I don't believe that to be so.

Hey, @Yen, could you check updated typings, I will be very thankfull if You do :grey_exclamation:

Let's merge this and see how it does in the wild :)

In case anyone else runs into the same issue I'm having using preact-redux with TypeScript, AFAICT the current AnyComponent typing in preact seems to be causing connect to not recognize component classes correctly and gives error TS2345: Argument of type 'typeof MyComponent' is not assignable to parameter of type 'AnyComponent...
There is a PR open for typings overhaul which would probably fix this issue https://github.com/developit/preact/pull/621
But in the mean time, I found that a workaround to disable the error is to just tell TS that it's AnyComponent with e.g. connect(...)(MyComponent as AnyComponent<MyProps, {}>)


Explore the possibility to generate the menu from routes directly

I am not sure about this but a little experiment would be useful because when someone needs the navigation based on routes only (no elements), routes config structure must be projected to items structure and they are very similar. The optional auto mode could solve the issue with two (almost) same arrays and save maintenance time spent on projects using the tree nav.

Implemented. Will be released as v4.0.0.


Deprecate in favor of a regular yaml parser/generator.  Thoughts?

(@rmg mostly for your input here)
I'm turning a bit of attention at getting node-tap to do nested/indented tests like perl's Test::More library.
In the meantime, it seems like there are a lot of edge cases in this yamlish thing, which could be avoided by just deprecating this and having tap use a performant and well-tested yaml library instead. (http://npm.im/js-yaml looks like the obvious choice).  When I wrote this module, there were no decent yaml parsers in JS, but times have changed.
Unless anyone strongly objects, I'll plan on dropping this dependency in<EMAIL_ADDRESS>and deprecating it then.

I think it makes sense.
Someone had the brilliant idea of not only listing dependants on npm, but listing repo urls on module pages, so we can get a pretty good idea of who else to ask :-)
These dependants have all seen at least one release in the last 9 months and their authors may have opinions or otherwise appreciate a heads up:

demobox - https://github.com/jaredly/demobox
eslint-tap - https://github.com/sindresorhus/eslint-tap
tap-eater - https://github.com/macbre/tap-eater
tap-unfunk - https://github.com/Bartvds/tap-unfunk
tapr - https://github.com/jeffbski/tapper

I skipped the @ mentions for the above list to leave the decision up to you on pinging them yet or not.
These dependants are probably not worth pinging the authors about since their module is either "done", abandoned, or otherwise and would probably appreciate one less thing in their inbox:

fo3 - unknown
ios7crypt - https://github.com/mcandre/node-ios7crypt - last published 3 years ago
node-markdownblog - https://github.com/semu/node-markdownblog - last published 3 years ago
pop - https://github.com/alexyoung/pop - last published 2 years ago
tap - https://github.com/isaacs/node-tap - looks fresh, but I hear they're moving away from yamlish anyway..
tap_ - https://github.com/isaacs/node-tap - republish of tap by aredridel 2 years ago, accidental?
tap-harmony - https://github.com/ttaubert/node-tap-harmony - last published 2 years ago
taper - https://github.com/nylen/taper - last published 3 years ago

FYI, I made a benchmark project to compare your lib to js-yaml, and JSON (for fun)
https://github.com/fed135/yaml-benchmark

This package isn't used by node-tap any more.  It uses js-yaml isntead.


mediaStreamTrack doesn't stop after executing setMediaStreamTrack multiple times

Describe the bug
The restartTrack function creates a new mediaStreamTrack and stops the previous one. Then, it assigns the new mediaStreamTrack to the _mediaStreamTrack attribute of the LocalTrack class (in the setMediaStreamTrack function).
However, if the restartTrack function is called multiple times in a short time interval, it can cause a bug. For example, imagine that restartTrack is executed twice within a short time interval. Then the code this._mediaStreamTrack.stop() in the (2) second execution may run before the code this._mediaStreamTrack = newTrack in the (1) first execution. As a result, the mediaStreamTrack from the (1) first execution will never be stopped and there will be no way to access it again.

This problem causes the browser to say This tab is using the camera or microphone even after the end of the meet, which causes the user to feel insecure.

Suggested solutions

1- Stop older mediaStreamTrack just before placing it in this._mediaStreamTrack(easier solution):

This change ensures that the older mediaStreamTrack is being stopped each time before the new mediaStreamTrack is being saved.(#980)

2- Add a Mutex lock for LocalTrack.restart() function(safer solution):

This change ensures that restart method calls are not executed in parallel:

Reproduction
A simple way for reproducing this problem is clicking multiple times on Flip(back) Camera button  in a short time interval in the example project.
Logs
No response
System Info
-

Severity
serious, but I can work around it
Additional Information
Besides the case mentioned above, there are some other scenarios that may happen very rarely, but they are caused by the uncertainty in the sequential execution of some async functions.
For instance, the localParticipant.setCameraEnabled(false) function may be executed while the restartTrack function is still running, which results in the new mediaStreamTrack being unmuted despite localParticipant.isCameraEnabled being false.

thanks for the in depth report!


scryer-prolog: 0.9.1 -> 0.9.2

Description of changes
closes https://github.com/NixOS/nixpkgs/issues/254861
change log: https://github.com/mthom/scryer-prolog/releases/tag/v0.9.2
diff: https://github.com/mthom/scryer-prolog/compare/v0.9.1...v0.9.2

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 254881 run on x86_64-linux 1

1 package built:

scryer-prolog


Firmware still ob 2<IP_ADDRESS> HS earning nearly 0

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
App Version [e.g. 3.3.0]

Additional context
Add any other context about the problem here.

Who is your manufacturer? You need to contact them to push an update.

closing as this is not an app issue.

            Nebra is the manufacture Gesendet mit der mobilen Mail AppAm 02.11.21 um 18:45 schrieb Coco Tang

                Von: "Coco Tang"<EMAIL_ADDRESS>2. November 2021An: "helium/hotspot-app"<EMAIL_ADDRESS>"Author" ***@***.***>,"mineHNT1"<EMAIL_ADDRESS>Re: [helium/hotspot-app] Firmware still ob 2<IP_ADDRESS> HS earning nearly 0 (Issue #1025)

Who is your manufacturer? You need to contact them to push an update.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.

check in with the nebra team. they're the ones pushing out firmware updates to your Hotspot.

        It’s impossible to reach out to them.I sent an email and just get the „ticked closed“ as answer back without any word.Gesendet mit der mobilen Mail AppAm 02.11.21 um 23:59 schrieb Coco Tang

                Von: "Coco Tang"<EMAIL_ADDRESS>2. November 2021An: "helium/hotspot-app"<EMAIL_ADDRESS>"mineHNT1" ***@***.***>,"Author"<EMAIL_ADDRESS>Re: [helium/hotspot-app] Firmware still ob 2<IP_ADDRESS> HS earning nearly 0 (Issue #1025)

check in with the nebra team. they're the ones pushing out firmware updates to your Hotspot.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.


getMappedType does not work when disableDynamicFileAccess = true

Describe the bug
Setting disableDynamicFileAccess: true causes getMappedType not to work. Here's the relevant config:
const mikroOrmConfig: Options = {
  discovery: {
    disableDynamicFileAccess: true,

    getMappedType(type: string, platform: Platform) {
      console.log("getMappedType called!");

      // Change default column type from `VARCHAR(n)` to `TEXT`
      if (type === "string") {
        return Type.getType(TextType);
      }

      return platform.getDefaultMappedType(type);
    },
  },

  /* ... */
}

And here's my entity:
@Entity()
export class User {
  @PrimaryKey()
  id!: number;

  // Setting `type` doesn't make a difference: @Property({ type: "string" })
  @Property()
  fullName!: string;
}

With this config and entity, running mikro-orm schema:create --dump or mikro-orm migration:create generates SQL that creates the user table with full_name as a varchar(255) instead of text.
I can tell that getMappedType is not even being called, since the console.log message doesn't appear in the output.
Is this an expected behavior when using disableDynamicFileAccess: true? Relevant docs
To Reproduce
Minimal repro with instructions for running
Expected behavior
getMappedType should work, so the full_name column will have type text in the database.
Additional context
We're bundling our Node application using Vite which is why we have disableDynamicFileAccess set to true.
Versions

Dependency
Version

node
18.14.0

typescript
4.9.5

mikro-orm
5.6.15

@mikro-orm-postgresql
5.6.15

FYI you don't really need the disableDynamicFileAccess flag, its only effects:

enforces usage of entities option with entity references (only a validation)
enforce usage of ReflectMetadataProvider (default)
disables metadata cache (default)

I think I will remove it from v6, it was added because of webpack issues and by that time the defaults were quite different, and v6 also resolves some issues this was trying to solve.

Thanks @B4nan! Removing disableDynamicFileAccess: true solves the issue for me.


[SPARK-12934] use try-with-resources for streams

@liancheng please take a look

Test build #50041 has started for PR 10906 at commit e400a17.

Test build #50041 has finished for PR 10906 at commit e400a17.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/50041/
Test PASSed.

I guess the caller should close the stream?

Looking at current code, that is not the case.

Yeah, it's because only ByteArrayInputStream/ByteArrayOutputStream is used. I think we should document that who should close the stream.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/50056/
Test FAILed.

Merged build finished. Test FAILed.

ERROR: Timeout after 15 minutes
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from https://github.com/apache/spark.git

Jenkins, test this please.

Thanks, LGTM. I'm merging this.

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/SparkPullRequestBuilder/50059/
Test FAILed.


Switch PageableList over to using RenderList

This patch moves PageableList off HomogeneousViewport and onto RenderList and
friends, making it match the new ScrollableList.

@Hixie @HansMuller

LGTM if @HansMuller and travis have no objections.


[docs] Determine "core four" H2s for Component/Usage pages

Following both existing H2s on our component usage pages, along with popular patterns found on other design system sites, we should lead with the same four H2s.
All content will live under these, and any necessary expansion will live beneath them.

NO


Fix overflow issue on posts-collection

60ch might overflow on smaller screens (as see on the Supermaya demo page). Adding a max-width to it fixes it and there's no horizontal scrolls after that.

Hey, any updates on this?

Sorry, missed the notification


MAINT: Mayavi / NumPy dep

Upstream PR https://github.com/enthought/mayavi/pull/900

Okay this one ended up adding more than just the NumPy/Mayavi deprecation. It also bumped the NumPy version to one we could actually test (1.13.1) because the old one (1.12) was no longer available.

NumPy 1.13.3 was released fall 2017, so to help CIs be more likely to work (and to reduce maintenance burden) I bumped...
SciPy to 1.0.0 which was released fall 2017, and
Scikit-learn to 1.19.1 which was released fall 2017

Two others in fall 2017:

matplotlib 2.1
pandas 0.21


REST interface

Created https://github.com/abapGit/REST
as I'm starting to see some parts here and there implementing parts for a SICF handler, suggest making an official one, suggest https://github.com/larshp/ABAP-Swagger based

see the linked repo


feat: add popoverClassName

Increment version number @1.8.7

Codecov Report

Merging #142 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #142   +/-   ##
=======================================
  Coverage   38.38%   38.38%
=======================================
  Files           8        8
  Lines         198      198
=======================================
  Hits           76       76
  Misses        122      122

Impacted Files
Coverage Δ

src/defaultProps/selectFieldDefaultProps.js
100% <ø> (ø)
:arrow_up:

src/types/selectFieldTypes.js
4.16% <ø> (ø)
:arrow_up:

src/SuperSelectField.js
39.16% <ø> (ø)
: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 ef35750...235524f. Read the comment docs.

I went to your forked repo, it seems you made a merge after pushing your local popoverClassName branch ?
It is not needed for a PR here, just choose the popoverClassName

Oooops i forgot something important:
Can you add in your commit:

Increment version number @1.8.7

This will trigger the release CI process after i merge your PR

Ah right, thanks. Sorry, not really used to contributing, getting better :) I'll comment once I've done those steps.

Ok...  I have no idea how to add "Increment version number @1.8.7" to my commit. And also, the reason that merge commit keeps popping up is because I always click Resolve Conflicts in the checks. So I'm not going to click it now and leave it there and wait for your advice on what to do.
Thanks for your patience.

i committed your changes directly on my dev branch, closing your issue#139

Ok cool thanks


Support of Apple Tap to Pay

We would like to accept payments with Apple Tap to Pay - however, the SumUP SDK always searches for a card terminal, which is not required in this case. How can I accept Tap to Pay payments here?

As far as I know the SDK does not support that functionality. Although it would be absolutely awesome.
So the right question would probably be, if there will be an update anytime soon to enable tap to pay.

Hi folks, we have released the new iOS SDK v.6.0.0 with Tap to Pay on iPhone support! Please refer to the integration documentation!

Closing as duplicate of https://github.com/sumup/sumup-ios-sdk/issues/132


Merge tombstone pr

PR summary
This PR manually merges the api and implementation features on cas and eavs introduced by https://github.com/holochain/holochain-rust/pull/1363/files.
Review checklist

[ ] The story has unit or integration tests
[ ] No new bugs, and any tech-debt is identified and justified
[ ] There is enough API documentation (how to use)
[ ] There is enough code documentation (how the code works)

This looks good to me!


As a user I would like to see FAQs in the storefront so I can get started with EDS

something like this is a good placeholder for us :)
https://dev.azure.com/equinor-design-system/_git/Equinor Design System?path=%2FStorefront%2F06-help%2F03-faq.md&version=GBmaster&_a=contents

Added text from wiki in GitHub, we will fill this out much later when we know what kinds of questions arise
looks good, maybe add, what is a design system, who built it and why

Is this still relevant? @BeckyBrekke


Set up continuous integration

The original project used Travis CI.

This project is now using Github Actions, thus closing this issue.


[Discussion] : Approach to building website and documentation

Hi all,
I am opening this issue for us to discuss the approach we are to take on building the React UI website and documentation website.
Should we settle with building one platform with docusaurus  or build the home page with next.js and redirect to the docusaurus  site when a user needs to check documetation?
This two concerns ideally should be under one hood. Given that if we build a website separate from the documentation, this would mean the website would only have one purpose of a landing page (as of now) then all information would be under the documentation. This what is currently happening as the website that resides under website directory and documentation site resides under reactui-docs
The current tech stacks are;
reactui-docs

docusaurus - Features (Enables building with React, MDX, Ready for Translations, Documentation Versioning, Content Search by Algolia)

website directory

next.js - Features(SSR, SEO, React, etc)
tailwindcss

Ideally docusaurus  is enough to do the job, but next.js was built on board due to more familiarity with it but docusaurus  is React.js so it gives us the leaverage of jsx with mdx on top of other awesome features out of the box.
What do you think?

cc @OSCA-Kampala-Chapter/react-ui-team  @SoulSolomon21 @Rishav1707 @maddy020 @Abeinevincent @123MwanjeMike @SamEarth79 @ankitk26 @Pavan-Nambi

I thinks so we should build the homepage separate and then redirects to documentation

@HassanBahati its alright we can have the index(home) page separate and redirect to the docs

thank you! we shall proceed on with that:rocket:


Fix compliance message format bug

When specific numbers of users are found with the role, the compliance message was getting shortened incorrectly.
Refs:

https://issues.redhat.com/browse/ACM-8411

/hold
I need to write a test

This works, but I'm wondering about the reliability (mostly because I'm unfamiliar with IamPolicy). Maybe use this function here instead?
https://github.com/stolostron/iam-policy-controller/blob/5c89098348afd5d677350c39a64c4e90b04621f1/controllers/iampolicy_controller.go#L487

Actually, for that you'd need to specify a role wildcard and it might be too specific, so maybe simpler is better for this...

/unhold

/cherry-pick release-2.9


caddy 2.4.3 fails to parse root/caddy/Caddyfile

caddy 2.3.0 would parse the generated root/caddy/Caddyfile ok, but with a deprecation warning:
{"level":"warn","ts":1625168095.5196342,"logger":"caddy.logging.encoders.logfmt","msg":"the logfmt encoder is DEPRECATED and will soon be removed from the standard modules","recommendation":"switch to a log format that isn't broken","more_info":"https://github.com/caddyserver/caddy/issues/3575"}

caddy 2.4.3 now fails to parse the file with:
run: adapting config using caddyfile: parsing caddyfile tokens for 'log': /path/to/root/caddy/Caddyfile:10 - Error during parsing: getting module named 'caddy.logging.encoders.logfmt': module not registered: caddy.logging.encoders.logfmt

Downgrading to 2.3.0 via https://github.com/caddyserver/caddy/releases/tag/v2.3.0 resolves the issue. https://github.com/caddyserver/caddy/issues/3575 claims that "the logfmt module will still be available, but not by default, as it is essentially broken. Instead of sweeping the bug under the rug, this will call it out to attention, which is better." but that seems to conflict with this change in 2.4.3: https://github.com/caddyserver/caddy/commit/ef5448324948537bb4ce798567d79d0612d41220.

For apt users on Linux, after installing the 2.3.0 deb, you can keep the caddy site in your sources.list and pin caddy be creating /etc/apt/preferences.d/caddy.pref like so until this issue is resolved:
Package: caddy
Pin: version 2.3.0
Pin-Priority: 1001

@jdstrand this is actually an issue with the configuration file, not gopm. I will share a fix with you

@jdstrand this is actually an issue with the configuration file, not gopm. I will share a fix with you

Oh, yes, I would be interested. Are you referring to this section in my idpe.yaml:
filesystem:
  root: ${IDPE_CLUSTER_ROOT}
  files:
    - name: CADDYFILE
      path: caddy/Caddyfile
...
        log {
            output stdout
            level DEBUG
            format logfmt
        }
...

Whether it is that or something else in idpe.yaml, happy to take that and do a PR for contrib/gopm.

@jdstrand this is actually an issue with the configuration file, not gopm. I will share a fix with you

Oh, yes, I would be interested. Are you referring to this section in my idpe.yaml:
filesystem:
  root: ${IDPE_CLUSTER_ROOT}
  files:
    - name: CADDYFILE
      path: caddy/Caddyfile
...
        log {
            output stdout
            level DEBUG
            format logfmt
        }
...

Whether it is that or something else in idpe.yaml, happy to take that and do a PR for contrib/gopm.

Indeed, I can simply remove format logfmt from the log stanza and it works with 2.4.3. This will default to 'console' (human readable) if it detects a terminal or json otherwise. This results in different output for the access log (ie, hitting caddy's open port (8080 with idpe template config)):
# 2.3.0 'format logfmt'
ts=1625771456.3908355 level=error msg="handled request" requestError="unsupported value type" common_log="<IP_ADDRESS> - - [08/Jul/2021:14:10:56 -0500] \"GET / HTTP/1.0\" 404 0" duration=0.000112204 size=0 status=404 resp_headersError="unsupported value type"

vs
# default 'format'
http.log.access.log0	handled request	{"request": {"remote_addr": "<IP_ADDRESS>:39402", "proto": "HTTP/1.0", "method": "GET", "host": "localhost:8080", "uri": "/", "headers": {"User-Agent": ["w3m/0.5.3+git20190105"], "Accept": ["text/html, text/*;q=0.5, image/*, application/*, x-scheme-handler/*"], "Accept-Encoding": ["gzip, compress, bzip, bzip2, deflate"], "Accept-Language": ["en;q=1.0"]}}, "common_log": "<IP_ADDRESS> - - [08/Jul/2021:14:17:38 -0500] \"GET / HTTP/1.0\" 404 0", "duration": 0.00042133, "size": 0, "status": 404, "resp_headers": {"Server": ["Caddy"]}}

Personally, I think the json output is just fine since nothing is parsing the caddy access logs that I know of. I'll create a PR against IDPE.
Thanks!


Source Safe Integration

Can we please have Visual Source Safe integration?
Many of us have not bought into Git, or other 3rd party off-site source code control systems.
We like things simple.
Our code, safely in our network, behind closed doors, away from competitors.
But, we do not want the bloat of Visual Studio Enterprise or the crippled nature of VS Community edition.
Plus although VSS is old, it still works and is a no-nonsense source code control system, plus we have been using it for over 20 years, and have millions of lines of code held inside it.
Please?

This is why we have invested so much in an extensibility story, namely Source Control extensibility. If there is enough demand, there will be someone creating an extension for it. Maybe that someone is you? 😮
https://code.visualstudio.com/docs/extensionAPI/api-scm


kube-proxy free snat issue nodeport & loadbalancer backing same pod

potentially stale ct issue, needs investigation

rev nat entry first of nodeport
later on load balancer
needs doc entry as well into 'limitations'

@borkmann is this still relevant? Looking at the description, I don't think anyone would be able to work on it :grin: .

Closing for now, let's see if it comes back with more context.


(WIP) Multilabel random forest

(@halfak made this into a PR, but it's mostly @codez266's work)

Made this into a PR because it's easier to track this way :)


Add support for cardStyle prop

Currently it is not possible to set the style for an individual card in the CardStack when using the default StackNavigator. My proposal is to add cardStyle option to stackConfig.

Is it the same as https://github.com/react-community/react-navigation/issues/8 ?

Yes. This resolves #8

The proposed screenStyle is more universal, so if you need to support something like this in other navigators, it might be better to use screenStyle instead of cardStyle.

I don't think we want this in other navigators. Both tab and drawer navigators don't set a background color, and if user is able to override their styles, they'll break.

Ok, lets ship this!


Shoot, we're having troubles sending your payment

So far I haven't been able to do any payments, neither to Yalls or to Starblocks. To Yalls I have an open channel, which is found by the Network explorer. There Zap gives me "Shoot, we're having problems sending your payment".
I think I also have an open channel to Starblocks but Zap doesn't find a route for payment.

No, I'm still not able to do payments. I'm either getting "No route found", or the "Shoot, we're having touble!". Could this be some security setting?
Also, when running Zap, my MacBook's ventilation really starts to whir louder & louder - looks like it's doing a lot of work there.