Sometimes BottomSheet doesn't showing

Sometimes BottomSheet doesn't showing, I think it happens because of conflict with react-native-maps. When I build release APK and install it on Android, when you open application first time then bottom sheet doesn't show but if you close and reopen application then bottom sheet appears. Had anyone this problem?

I haven't attempted to repro in release, but I've been seeing this every now and again while developing my app. It's slightly unsettling...

I haven't attempted to repro in release, but I've been seeing this every now and again while developing my app. It's slightly unsettling...

Yep, you're right it happens with me in debug mode too(

Have the same in iOS. (Component is navigation screen)
Every new launch app bottom sheet doesn't show.
bottomSheetRef {current: null}

It appears only Refresh on debug mode. But in production you have not refresh.

"react": "16.12.0",
"react-native": "0.61.5",
"react-native-reanimated": "1.4.0",
"react-native-gesture-handler": "1.5.1",
"reanimated-bottom-sheet": "1.0.0-alpha.18",

There is problem with snapPoints prop! From documentation:
E.g. [300, 200, 0]. Points for snapping of bottom sheet coomponent. They define distance from bottom of the screen. Might be number or percent (as string e.g. '20%') for points or percents of screen height from bottom.

doesn't work in iOS firs launch with snapPoints=['50%', '100%', 0],
but it works with only numbers like snapPoints=[300, 500, 0].
Looks like something doesn't know what is 'device height' when you open app first time on iOS.

Problem not actually in snapPoints prop. It's about Dimensions.get('window')
Look at this:
https://github.com/osdnk/react-native-reanimated-bottom-sheet/blob/master/src/index.tsx#L125
I just add
console.log('HEIGHT!!', screenHeight);

after line 125 to see which it contains.
First launch app in iOS:

So, bug fix:
instead of
const { height: screenHeight } = Dimensions.get('window')

better use
const platformDimension: "screen" | "window" = Platform.select({ ios: 'screen', android: 'window'});
const { height: screenHeight } = Dimensions.get(platformDimension);

or
const platformDimension = Platform.OS === 'ios' ? 'screen' : 'window';
const { height: screenHeight } = Dimensions.get(platformDimension);

First launch app in iOS after:

Last News!
When Dimensions.get('window').height returns 0 – it's problem in AppDelegate.m with RNSplashScreen.
https://github.com/crazycodeboy/react-native-splash-screen#third-stepplugin-configuration
my code was:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
    [RNSplashScreen show]; // here

    // ...other code
    return YES;
}

worked:
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
    // ...other code

    [RNSplashScreen show];  // here
    // or
    //[RNSplashScreen showSplash:@"LaunchScreen" inRootView:rootView];
    return YES;
}

after that I have normal window.height value, not 0.

I have the same problem on Android.
The Bottom Sheet is on top of the react-native-maps that fill whole the screen. Most of the time it works but sometimes the bottom sheet is not showing up.
Is there any fix for that?

I had the same problem on android, but as I see there is a fix for that in the master branch. Its not too easy to use master because of the build steps, but it indeed fixes the problem (at least for me).

Probably not a full fix, however I seem to have solved this problem by adding a guard to the bottom sheet rendering.
Its seems to be a problem when combining the react-native-bottom-sheet, react-native-safe-area-context and react-native-maps modules where the safe area insets aren't correctly measured before rendering the bottom sheet. Thus, by doing something like
return bottomInset &&     <BottomSheet       ref={initialBS}...
I was able to correctly determine the inset and render after such was measured.
For those who are curious how I did this, I used expo-device to determine model and added 34 to bezelless and 30 to bezeled  devices initial snappoint. I assigned that to the bottomInset variable and had the component rerender when completed.
If anyone has a better solution to this work around please let me know.


Shortcut to minimize window

What  is the suggested method for when I want to hide a window, but don't want to quit the tile entirely? If no solution exists maybe a shortcut can be added to minimize the current focused tile.

The best way right now is to just use a ToggleFloatingMode keybinding. The problem with supporting minimize is what happens when you have 2 windows minimized in a workspace?

Couldn't minimized windows be brought back using Windows built-in Alt+Tab window switcher?

I think I misunderstood your feature request. Do you mean something like the CloseTile keybinding, but just for minimizing?

Yes that is correct. The shortcut in Windows is Window Key + Down Arrow twice which is really that great. So yes like CloseTile, but does not quit the window and minimizes to taskbar instead.

That's really simple then. I will add this alter today.

Latest dev build contains this feature.


SU Cakes behave weirdly in Singleplayer if the person is holding a cake and places it on an partially eaten cake

Define?

It's really hard to explain, if the player places a cake then places another cake on top, the cakes won't be able to be destroyed until the player switched to creative mode and eats the bottom cake

Fixed.


Add remove method update

This SHOULD just have changes in the Show/HIde LT-AddRemove functions.. It would change from renaming the "ProductName" value to setting the "SystemComponent" value to cause the program to be hidden...  Definitely a change from how you were handling it prior.

Pull request closed. Merged updates to ProxyAwareness branch and submitted new Pull request.


Adding translation for show excerpt

This translation for the schema locale files exists in Fetch & Gem but was missing from Expanse

Added in https://github.com/archetype-themes/locales/pull/18


Replace createHelp and includeHidden

Replaces ArgumentSet.init(_:creatingHelp:includeHidden:) with
ArgumentSet.init(_:visibility:). visibility intentionally does not
have a default value to ensure that callers only have the correct
arguments. As part of this change includeHidden has been replaced
throughout the codebase with visibility. This change also fixes a
bug where arguments with hidden visibility were being displayed in the
generated command usage string.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci Please test Linux platform

I'm not sure what's consistently crashing on Linux, hmm 🤔

@swift-ci Please test


fix: remove unused semantic release plugin

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

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Front-end: add a new module loader that loads explicitly built Swift modules

To support -disable-implicit-swift-modules, the explicitly built modules
are passed down as compiler arguments. We need this new module loader to
handle these modules.
This patch also stops ModuleInterfaceLoader from building module from interface
when -disable-implicit-swift-modules is set.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


MTL-1939 Initial Firmware page

Description

This refactors the verbose kernel arguments into their own page, and adds a new minimum firmware page.
The new page for BIOS/Firmware does not include interrogation steps, but it does mention the endpoints to talk to for advanced Redfish® users.
Checklist Before Merging

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[ ] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport main


Chore: Support external rules outside @sonarwhal

Fix #713

Pull request checklist
Make sure you:

[x] Signed the Contributor License Agreement
[x] Followed the commit message guidelines

For non-trivial changes, please make sure you also:

[ ] Added/Updated related documentation.
[ ] Added/Updated related tests.

Short description of the change(s)

We need to start documenting things :P

We need to start documenting things :P

https://github.com/sonarwhal/sonarwhal/tree/master/docs 😛
The issue has more details on what needs to be changed. This is more of a Chore than a Fix IMO though.

I have changed the title and the commit :)


upgrade(package): Bump dependencies

eslint 3.9.0 -> 4.0.0
jsdoc-to-markdown 2.0.1 -> 3.0.0
mocha 2.4.5 -> 3.4.2

Change-Type: patch

Just out of curiosity: Is this updating packages just to keep "up to date", or does this also get us fixes that we want / need??

just a heads up @jhermsmeier (or whoever merges this PR) you can apply the procbots/versionbot/ready-to-merge label to this PR instead of hitting the merge button. The versionbot will automatically add the changelog entries and cut a new version - note that npm publishing will still have to be done manually (at least for now)

@lurch Both – naturally, if there's a new version of something, that version has come about for a reason. For mocha there is a lot that changed, mostly fixes (see mocha/CHANGELOG.md@2.4.2), and I'd argue, too much to distill into a commit message (same for eslint).

Why does your comment link to the @2.4.2 section of the mocha changelog, when apparently we were already using mocha 2.4.5 ? *confused*

I added the label, let's see what happens :D

🎉

@hedss @lekkas Are there "standard" colours for the procbots labels? I'm fairly sure that in most other repos they're purple...?
It's obviously only a minor point, but standard colours make things easier to spot at a glance.

... and why did 4 out of 5 CI checks fail? Shouldn't that have stopped the merge?? Or has this repo been configured differently to other VersionBot-using repos? (and if so, is there a specific reason for that?)

@lurch because the merge & branch deletion happens before the builds can start, causing git fetch origin +refs/pull/176/merge to fail, because the ref doesn't exist anymore.

@lurch When it merged, nothing had failed. Another point, merges won't be prevented if the base hasn't been set up with a mandatory status check that fails it. Anything optional that doesn't actually stop the merge will be ignored.

@lurch currently we haven't set any specific rules for either colours or names of labels in general across resin.io . 'ready-to-merge' is a temporary label that is applied for a few minutes though, unlike others that are longer-lived (e.g. when categorising issues) and need to be more consistent . Till we have defined names/colours (that will ultimately have to be created using a cli tool) we can leave this up to the maintainer's taste :)

I just picked the same colour all of the other resin added labels had, as it seemed logical to me at the time.


social media buttons (...)

Twitter + Hacker news. I'm tempted to say just hacker news.

No it's not 2010


Align with Northbound API Spec v0.3.

The Northbound API v0.3 now contains fragments from this profile.

Sept 3 meeting - approved


Event Hubs Capture Replay

In the next steps - it would be handy to have some guidance on replaying captured events. For example azure function -> event grids with some C# code. The Capture Event Hubs data is great - but not great for C# developers. Bit more material around using captured data - I'm pretty sure I saw a sample on the EventGrid GitHub that related to replay

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

ID: 71093e2a-bbff-3a79-5f16-289a3a5f6cd7
Version Independent ID: e4e9873d-0ae7-25a4-16d1-5ecac6e84b91
Content: Overview of Azure Event Hubs Capture
Content Source: articles/event-hubs/event-hubs-capture-overview.md
Service: event-hubs
GitHub Login: @sethmanheim
Microsoft Alias: sethm

@GraemeSMiller Thanks for the feedback. We are actively investigating and will get back to you soon.

@sethmanheim we have a request to add more guidance on replaying captured events

@GraemeSMiller Thank you for the suggestions! Sorry for the slow response. We are actively updating the Event Hubs Capture guidance, so we will definitely take this feedback into account when updating the article.

#please-close

Great thanks. Just be better to explain how to get a more Kafka like experience of replaying all historic events.


Pool not generating full reward

Hello,
I am trying to setup z-nomp for VoteCoin mining. It is a zcash fork. Block reward should be 125 VOT.
I copied settings from zclassic.json.
When new block is found, it only adds 100 VOT instead of 125.
As you can see here:
http://pool.votecoin.site/stats
Example block:
http://explorer.votecoin.site/block/00000c6b87f7e982e40327b84971e19a24d793ac7ca4bf76a50fd8fb9ebea455
Mining with votecoind daemon on Linux properly gives 125 VOT.
But mining through the pool gives 100 VOT.
Are you aware of any configuration which is required to fix this?
I am expecting to receive 125 VOT reward, not 100.
Thank you

This is my votecoin.json file in coins folder:
{
    "name": "votecoin",
    "symbol": "VOT",
    "algorithm": "equihash",
    "requireShielding": true,
    "peerMagic": "24e92764",
    "percentFoundersReward": 0,
    "payFoundersReward": false,
    "txfee": 0.0000
}

And in pool_config, I have
"rewardRecipients": {
},

"paymentProcessing": {
    "minConf": 10,
    "enabled": true,
    "paymentMode": "pplnt",
    "_comment_paymentMode":"prop, pplnt",
    "paymentInterval": 20,
    "minimumPayment": 1,
    "maxBlocksPerPayment": 3,
    ...
    ...

Aah, I think I found the problem.
I forgot (in the sources of forked zcash) to return proper block reward and founders reward on the RPC API, so it returned wrong reward. I'm now recompiling the sources to see if this is fixed after returning correct reward. Will close this issue if this is correct.

Yeah that was it. Sorry for blaming your ingenious software :) Closing this issue.

Hey @Tomas-M Sorry for bothering you, but I saw your pool working (I wish i could say same for mine)
I build zclassic pool with z-nomp. It works good, no warnings at all.
Just no reward at all either :) :)
The pool calculates for me 2.5 days luck (with 4.2 KSols/s) and I am mining already pretty much 2 days and I don't have even single orphaned block discovered :(
All I read inside debug log repeating over and over again is:
2017-10-04 19:26:26 UpdateTip: new best=00000001fb955f21b5ce2525bf1e870565416b015984505b7e900e62add34dec  height=189099  log2_work=45.871881  tx=463886  date=2017-10-04 19:25:11 progress=0.999992  cache=0.0MiB(35tx)
2017-10-04 19:26:26 keypool reserve 4
2017-10-04 19:26:26 CreateNewBlock(): total size 1000
2017-10-04 19:26:26 keypool return 4
2017-10-04 19:26:45 keypool reserve 4
2017-10-04 19:26:45 CreateNewBlock(): total size 2943
2017-10-04 19:26:46 keypool return 4
2017-10-04 19:27:06 keypool reserve 4
2017-10-04 19:27:06 CreateNewBlock(): total size 4886
2017-10-04 19:27:07 keypool return 4
2017-10-04 19:27:12 keypool reserve 4
2017-10-04 19:27:12 CreateNewBlock(): total size 6829
2017-10-04 19:27:12 keypool return 4
my conf looks like this:
addnode:8133=dnsseed.zclassic.org
addnode:8133=dnsseed.rotorproject.org
addnode=<IP_ADDRESS>:8133
addnode=<IP_ADDRESS>:8133
other peers
rpcuser=long username
rpcpassword=long long password
daemon=1
rpcport=8232
blocknotify=node /root/z-nomp/scripts/cli.js blocknotify zclassic %s
npm block is boring too:
2017-10-04 19:24:37 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:25:32 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:26:02 [Payments]	[zclassic] Finished interval - time spent: 6ms total, 2ms redis, 3ms daemon RPC
0|npm      | 2017-10-04 19:26:26 [Pool]	[zclassic] (Thread 1) Block notification via RPC polling
0|npm      | 2017-10-04 19:26:27 [Pool]	[zclassic] (Thread 1) Block notification via blocknotify script
0|npm      | 2017-10-04 19:27:21 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:28:16 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:29:02 [Payments]	[zclassic] Finished interval - time spent: 19ms total, 4ms redis, 12ms daemon RPC
0|npm      | 2017-10-04 19:29:11 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:30:06 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:31:01 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:31:56 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:32:02 [Payments]	[zclassic] Finished interval - time spent: 7ms total, 3ms redis, 4ms daemon RPC
0|npm      | 2017-10-04 19:32:51 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
0|npm      | 2017-10-04 19:33:46 [Pool]	[zclassic] (Thread 1) No new blocks for 55 seconds - updating transactions & rebroadcasting work
Everyone tells me it is completely normal but...
I don't know how to really test it does it work :(
I am so close to order nicehash hard artillery to test it out at the end..
Any help would be highly appreciated !

If you have doubt and want to test, use testnet.
But your log doesnt show anything weird, hash is just low VS net hash. It just takes time to find a block

@sennevb
I am not sure what peers to use for testnet zclassic. It is a bit hard with the documentation there. Do you know them by chance?

@sennevb I did try with the production ones but they simply refused to connect (as expected)

@sennevb It works! Thank you!


Sync calendars across services

https://github.com/davralin/cluster-ops/commit/f4ad62ab055ba0d06be27e389dc9c35d51fe7da2

Why though.


Feature: New plugin for FlagsOverTime widget

Feature Details

Currently, the FlagsOverTime widget in the gsm kri report only shows the most recent 12 months of data (due to report size concerns). Adding a gsm.app plugin that allows for the user to view the full history of all flags over time for all site-kri combinations would allow the risk advisors to dive deeper into the data when needed.
Possible Implementation

Additional Comments

Will probably want to include a toggle similar to what was used here: https://github.com/Gilead-BioStats/gsm/blob/5cc2056e004f9196ef3ebf71ce2c339409577b23/inst/htmlwidgets/Widget_FlagOverTime.js#L16-L60


duniverse loses opam patches

I was experimenting with duniverse and found this failure:
File "duniverse/shared-block-ring.2.5.0+1/example/jbuild", line 1, characters 0-0:
Error: jbuild files are no longer supported, please convert this file to a
dune file instead.

There is a shared-block-ring.2.5.0+1/files/0001-dunify.patch which is a backport of some commits from master that converts jbuilder to dune (https://github.com/xapi-project/xs-opam/blob/master/packages/upstream/shared-block-ring.2.5.0%2B1/files/0001-dunify.patch).
This is present in the opam file like this:
https://github.com/xapi-project/xs-opam/blob/master/packages/upstream/shared-block-ring.2.5.0%2B1/opam#L40-L48
patches: [
    "0001-dunify.patch"
]
extra-files: [
  [
    "0001-dunify.patch"
    "md5=37841bb6a3eeb0c1721bbc153f647311"
  ]
]

It looks like duniverse fetched the sources, but didn't apply the patches, which is how I ended up with the jbuild failure.
In this case I could probably pin the package to master to solve the issue, but in general it would be good to apply the patches from opam, since might contain important build fixes or backports.

Hi,
Do you have a plan to re-apply patches given by opam into downloaded sources? This can be a significant security issue when a distribution decides to apply a hotfix via this mechanism.

Regarding 2. I agree that the patch should ideally be inlined into our dune port. Adding CI support is possible, but I think this should be raised as a point to duniverse-lint and/or our CI in general. We're currently not set up to monitor the upstream opam-repository for any changes at all.
Regarding 1. this is more tricky than one would imagine, due to the fact that the OPAM file is evaluated in the lock stage (so access to patches is available there) but the pull stage (rightfully) just uses the created lockfile and does not need to consult OPAM-Repository. This means that patches need to be recorded at the lock stage and applied in the pull stage. It raises the question on how to record the patches: referencing them by filename in wherever the patch came from (most likely opam-repository) is not a good way because by the time the repo is pulled the patch might have changed. Putting the patches in the repo is somewhat ugly so the best alternative I currently see is to inline the patches into the lockfile (which again potentially raises some issues with line endings) and then apply them after pulling.

Upon further inspection I have to say that the patching mechanism of OPAM seems to work differently than I expected:

Unpack source
Unpack patches
Apply patches

This means that patches can be part of the OPAM upstream tarball and do not have to be provided by opam-repository (e.g. usb.1.3.1 where the patches/ folder is actually in the upstream tarball) so it needs to be handled slightly smarter - maybe by having an ADT like type patch = Repo_provided of string | Tarball_provided of Fpath.t.


Format notification missing in packaged version

This isn't showing up when the entered name doesn't match the pattern:

cc @yhahn

Still nothing as of v0.20.7 of atom-shell.

@camilleanne - what about creating a ticket at atom-shell tracker?

https://github.com/atom/atom-shell/issues/1043

Looks like we're going this one on our own:
https://github.com/atom/atom-shell/issues/1043#issuecomment-70952338

I think we should remove all html input pattern validation altogether. The regexes for the file browser in particular are quite limiting and we should just keep it simple by showing all files and depending on mapnik-omnivore to throw if they are not valid to be opened - refs #1149.

Hrm, we use html 5 input validation for more things than just file browser filetypes. We'll have to mull on a good approach to this one.

I agree with @yhahn because of issues like #1123. So we can make our own notifications (I've already looked into this, it's not that bad), or we can make the change source interface better.

@camilleanne @yhahn - any thoughts on what is lowest hanging and feasible to move on here? #1342 reminds me of how nice it would be to fix this so that errors are not silent.


Should we install a stale-bot to this repo?

@papasmile suggested installing https://github.com/marketplace/stale on this repo in #1652.
We can discuss this here.

A stale-bot may reduce the number of open issues. But the problem with Handlebars is that a lot of issues simply remain unanswered. I don't have the resources to answer every single one and there are almost no other maintainer who have resources...
It seems wrong to automatically close issues, just because noone answers the initial question. If the issue-author does not respond to questions or proposals, that is another matter.
I think, what we need in this repo is a bit of triaging.

Stale-bot will easily allow you to ignore certain labels.  You could mark any issues you think need attention with a special label (e.g. 'needs answer') then turn it on...

I am very strongly in favour of adding a stale bot. Having lots of open issues is noise that actively gets in the way of contributions. It's impossible to tell what's important and what's not.
I hear what you're saying about questions, but we can solve that easily IMO by adding issue templates. I would add one for questions that strongly encourages people to post usage questions on stackoverflow for the simple reason that they tend to get answered there cos that's where the community of people who want to answer questions go.
GitHub is more oriented towards maintainers, contributors and people with bugs or feature requests. IMO everyone has a better experience when these two things (maintenance and support) are separate.
That being said, I think we can and should use a very slow/lenient bot with nice big timeframes cos this is a fairly slow moving ship and that's not a bad thing 🙂

FYI another side effect of adding a stale bot would be getting community members to chime in again on any of their issues that are breaking changes that we should take time to handle before releasing master.


External breakpoints

Hi there,
is there any way to set external breakpoints? It would come in very handy when testing ABAP code incorporated in a SAP Standard business process (e.g. when implementing a BAdI).
Thank you.
Kind regards
Christoph

Pretty easy, just click on the left of the code and start the debugger with F5. See here.
No sapgui debugging though, only RFC/HTTP/abap unit

Hi Marcello,
thank you for your quick response.
Overall, the plugin is really impressive.
The challenge and question I am having is: I am triggering a process out of SAP GUI or a web service (e.g. to create an account). This process (e.g. account creation) invokes a BAdI implementation. The process is executed with my user, but obviously not out of VS Studio. In SAPGUI I can set an external breakpoint for this user, so whenever this user invokes the BAdI implementation via the execution of this particular process, the system stops at the external breakpoint for this user.
I am unusre how to do this with your plugin.
Thank you for your help.
Kind regards
Christoph

It's not supported
That requires controlling the sapgui and I'm not quite sure how.
If you call it over rfc/http or an unit test triggered in the plugin it
does, but no sapgui
On Mon, 29 May 2023, 19:36 maggiv8, @.***> wrote:

Hi Marcello,
thank you for your quick response.
Overall, the plugin is really impressive.
The challenge and question I am having is: I am triggering a process out
of SAP GUI or a web service (e.g. to create an account). This process (e.g.
account creation) invokes a BAdI implementation. The process is executed
with my user, but obviously not out of VS Studio. In SAPGUI I can set an
external breakpoint for this user, so whenever this user invokes the BAdI
implementation via the execution of this particular process, the system
stops at the external breakpoint for this user.
I am unusre how to do this with your plugin.
Thank you for your help.
Kind regards
Christoph
—
Reply to this email directly, view it on GitHub
https://github.com/marcellourbani/vscode_abap_remote_fs/issues/190#issuecomment-1567415467,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASW6HLLYFKNN7PDHJOKUSLXITUDJANCNFSM6AAAAAAYTAB22U
.
You are receiving this because you commented.Message ID:
@.***>


Added scripts to add/remove users easily

vpn_setpsk:
Usage: vpn_setpsk [psk]
Description: Set PSK for L2TP/IPSec authentication
vpn_unsetpsk:
Usage: vpn_unsetpsk
Description: Unset PSK for L2TP/IPSec authentication
vpn_adduser:
Usage: vpn_adduser [name] [password]
Description: Add a user, removes existed user with [name]
vpn_deluser:
Usage: vpn_deluser [name]
Description: Remove a user with [name]
vpn_apply:
Usage: vpn_apply
Description: Apply l2tp-secrets and ipsec.secrets, then invoke ipsec rereadsecrets

This is awesome!

@mariotaku I guess the next step is to bundle all the scripts including run in a bin/ subfolder and update the Readme.


ctrl key sucks

im using ubuntu 16.04
in hyper ctrl key not work and i cant use it for copy pase and ... (ctrl+c , ctrl+v)

when i select some text if i press ctrl then hyper deselect them.
is it a bug or i missing something?
sorry for my poor english :-)
Hyper 1.1.0
Electron 1.4.7
linux x64 4.4.0-59-generic

@ph98 the shortcut for copy/paste in hyper is ctr+shift+c and ctrl+shift+v

@stefanivic i know that :-)
but the problem is ctrl key when I'm trying to copy and paste ...
it not work for me!
i try to disable all plugin i have but still the problem not solved

@ph98 yeah, this was fixed in : https://github.com/zeit/hyper/pull/1406 So you can either build from source or wait for the 1.2.0 update.

close in #1876


pulldown-cmark FILE sits idle

https://github.com/raphlinus/pulldown-cmark/commit/d7b536963f6dfe9e571603eb3be44376d00a4e5d#r32812766

In my experience, I've only been able to render from standard input (eg. pulldown-cmark < README.md > README.html).

Yup, this is a documentation bug. We should fix this soon.


Enforce prepared statement usage for simple query

It will make sense to add a configuration property (Predicate<String> preferPreparedStatement) to enforce prepared statement usage? We have a similar feature in R2DBC MS SQL although there we control cursor execution (https://github.com/r2dbc/r2dbc-mssql/blob/master/src/main/java/io/r2dbc/mssql/MssqlConnectionConfiguration.java#L67)
Originally posted by @mp911de in https://github.com/mirromutth/r2dbc-mysql/issues/89#issuecomment-563113937

Thanks, add useServerPrepareStatement=true in the connectionString solved my issue.


Provide way to deprecate commands and options

Currently I can't find any way in DSL to specify that given command (or option) should be considered as deprecated. I mean something like:
desc 'Add new entry'
deprecate 'This will be removed in version 1.3. Please use "create" command instead.'
command :add do |c|
# ..
end

command :list do |c|
  c.desc 'List tasks'
  c.switch :all, deprecated: 'Will be removed in 1.4'
  c.flag :filter, deprecated: 'Will be removed in 2.0. Use --query instead'
end

This could alter help output and print warnings when deprecated commands / flags are being used.
What do you think?

Closing as old.  Re-open if you still need this.


[Bug]: Evaluate hangs inside of embedded PDF frames

Minimal, reproducible example
import puppeteer from 'puppeteer';

const sleep = t => new Promise(r => setTimeout(r, t));
const url = `file://${process.cwd()}/example.pdf`;

const browser = await puppeteer.launch({
    headless: 'new',
});

const page = await browser.newPage();
await page.goto(url);
await sleep(5000);

const frames = page.frames();
for (const f of frames) {
    console.log(`Evaluating in ${f._id}, ${f.url()}, ${f.isOOPFrame()}`);
    await f.evaluate(() => 1 + 1);
}

console.log('Done');
await browser.close();

Error string
no error
Bug behavior

[ ] Flaky
[ ] PDF

Background
In new headless or headful mode (i.e., when PDFs are rendered in the browser), attempting to evaluate inside of the PDF frame hangs indefinitely. This is true for any methods which attempt to use the frame's execution context. From some limited debugging, it seems that puppeteer is waiting indefinitely for an execution context that doesn't exist.
Possibly related (?): the CDP event "Page.frameDetached","params":{"frameId":"31218988D67AB9B8AC1BD6140FCC9433","reason":"swap"} is fired which, according to the FrameManager code, means that the frame should now be an OOPIF frame, but frame.isOOPFrame() returns false.
Debug: hang.log
PDF used (any will work): example.pdf
Expectation
Either:

Evaluation to succeed inside of the PDF context, or
Puppeteer to throw an error stating that the execution context was destroyed.

Reality
Program hangs on frame.evaluate. More specifically, it hangs when waiting for the deferred execution context (https://github.com/puppeteer/puppeteer/blob/main/packages/puppeteer-core/src/util/Deferred.ts#L74).
Puppeteer configuration file (if used)
No response
Puppeteer version
21.0.1
Node version
18.16.1
Package manager
npm
Package manager version
9.5.1
Operating system
Linux

The new headless mode is still in beta and there may be stability and compatibility issues.
You probably already know this, but just in case, if you're looking for ways to render PDFs while using a headless browser, a reliable solution is:

using the old headless mode
capturing the download, and
converting the downloaded PDF to PNG images using ImageMagick.

It's a few steps, but it reliably renders PDFs.
However if you're looking specifically to evaluate JS code in the context of PDFs for some "Chrome PDF viewer" plugin enhancement, this method directly help you. That being said, using the convert method described here will enable you to build your own "PDF viewer" fairly simply.
For some reference code that works in production (albeit using the underlying DevTools protocol rather than a Puppeteer API, to which you'd need to convert if you wish to use pptr), take a look here for the convert to PDF code; and here, here and here for the capture download and spawn convert process code.
All the best @liamdalg !


fix: don't use decorateRequest with reference types

Fixes https://github.com/SerayaEryn/fastify-session/issues/137
Also see:
https://github.com/fastify/fastify/pull/2688
https://github.com/fastify/fastify/issues/2598

Coverage remained the same at 100.0% when pulling 0372e067a592f541df1ceda843394108f3d9b1ab on DRoet:master into e201f78fc9d7bd33c6f2e84988be7c8af4b5a8a3 on SerayaEryn:master.

@SerayaEryn can we merge this? (:

@SerayaEryn can we merge this? (:

Closing this in favor of https://github.com/SerayaEryn/fastify-session/pull/143 and/or https://github.com/SerayaEryn/fastify-session/pull/147


Make response variable readily available in browser JS Console

To test ideas or do quick snippets of code would be nice to have the result of the call done in the REST Console readily available in the browser JS Console too.
I'm thinking something similar to this:

I do a query
The response triggers a console.log in the JS Console
The message says something like: "Returned object available with the name ret." (always the same variable, the text work just as a reminder of the variable name, but can also use different variables for each query, incrementally ret1, ret2, etc).
From that moment on I can use and manipulate ret in the JS console

Should be simple enough.
I can also provide a function in the console so you can send requests via the browser's console and see it get logged along with the others.

Ohhh that would be nice :D

It looks like logging is already supported.
In the console:
send({ path: '/me' })

And it will show up in the request log.

Wohoo! :D


Use singlequote instead of doublequoe on Webview components of Android, iOS

The style for JSX props is to use double quotes so I'm going to close this, but thank you for the PR though!


Question about autolab-core and autolab-preception

When I ran the code in python3 ,I encountered this error:
(pointnetgpd) klxue@dell-XPS:~/code/PointNetGPD/apps$ python generate-dataset-canny.py
WARNING:root:autolab_core not installed as catkin package, RigidTransform ros methods will be unavailable
Traceback (most recent call last):
File "generate-dataset-canny.py", line 13, in
from dexnet.grasping.quality import PointGraspMetrics3D
File "/home/klxue/code/dex-net/src/dexnet/init.py", line 24, in
from dexnet.api import DexNet
File "/home/klxue/code/dex-net/src/dexnet/api.py", line 42, in
import dexnet.database.database as db
File "/home/klxue/code/dex-net/src/dexnet/database/init.py", line 22, in
from dexnet.database.hdf5_factory import Hdf5ObjectFactory
File "/home/klxue/code/dex-net/src/dexnet/database/hdf5_factory.py", line 39, in
from perception import RenderMode
ImportError: cannot import name 'RenderMode' from 'perception' (/home/klxue/anaconda3/envs/pointnetgpd/lib/python3.7/site-packages/perception/init.py)
I  changed from perception import RenderMode into from autolab_core import RenderMode ,but encountered this error:
(pointnetgpd) klxue@dell-XPS:~/code/PointNetGPD/apps$ python generate-dataset-canny.py
WARNING:root:autolab_core not installed as catkin package, RigidTransform ros methods will be unavailable
WARNING:root:Failed to import gqcnn! Grasp2D functions will not be available.
WARNING:root:Failed to import mayavi
WARNING:root:Failed to import mayavi
WARNING:root:Failed to import mayavi
WARNING:root:Failed to import mayavi
WARNING:root:Failed to import mayavi
WARNING:root:Failed to import OpenRAVE
WARNING:root:Failed to import mayavi
WARNING:dexnet.grasping.grasp_sampler:Failed to import rospy, you can't grasp now.
WARNING:dexnet.grasping.grasp_sampler:Do not have mayavi installed, please set the vis to False
Traceback (most recent call last):
File "generate-dataset-canny.py", line 13, in
from dexnet.grasping.quality import PointGraspMetrics3D
File "/home/klxue/code/dex-net/src/dexnet/init.py", line 24, in
from dexnet.api import DexNet
File "/home/klxue/code/dex-net/src/dexnet/api.py", line 42, in
import dexnet.database.database as db
File "/home/klxue/code/dex-net/src/dexnet/database/init.py", line 22, in
from dexnet.database.hdf5_factory import Hdf5ObjectFactory
File "/home/klxue/code/dex-net/src/dexnet/database/hdf5_factory.py", line 46, in
class Hdf5ObjectFactory(object):
File "/home/klxue/code/dex-net/src/dexnet/database/hdf5_factory.py", line 226, in Hdf5ObjectFactory
def rendered_images(data, render_mode=RenderMode.SEGMASK):
NameError: name 'RenderMode' is not defined
Could someone help me? Thanks very much!

from meshpy import RenderMode


How can Train KAN on batches of data

While training KAN using entire samples say 10000, end up in memory overflow issue. Instead of giving entire data at once on "dataset" dict, can we train KAN on small batches of data like normally do on ANN?

Hi, you can pass the batch argument in train: https://github.com/KindXiaoming/pykan/blob/master/kan/KAN.py#L761

thanks @KindXiaoming, got it 👍

@KindXiaoming can you explain how does the batch argument works in case of KANs. It seems only training and testing on the batch size specified per step. Or i got it wrong?

I am still having problems OutOfMemoryError with large datasets. Is it possible to modify the code to use Dataloader and pass train_loader and test_loader to train instead of dataset?
So edit this line
def train(self, dataset, opt="LBFGS", steps=100, ......

@sparcycram please try the speed mode model = model.speed(). tutorial: https://github.com/KindXiaoming/pykan/blob/master/tutorials/Example_2_speed_up.ipynb. You need to update to the most recent version 0.2.0


Try running eagleye with llh_source_type=sensor_msgs/NavSatFix ( without RTKLIB and nmea_msgs::sentence topics)

Hi,
I'm trying to get eagleye (develop-ros2 branch) to work with my bags, which contain the following data:

/can_twist (vehicle speed from can)
/gnss_rear/nmea_sentence (only rmc sentence data is available in the topic)
/gnss_front/navsatfix (sensor_msgs/NavSatFix)
/gnss_rear/navsatfix (sensor_msgs/NavSatFix)
/imu_data

My configuration file looks like this (And use_multi_antenna_mode is set to true)
/**:                                               #GNSS cycle 5Hz, IMU cycle 50Hz.
ros__parameters:
# Estimate mode
use_gnss_mode: NMEA
use_can_less_mode: false
# Topic
twist:
  twist_type: 0 # TwistStamped : 0, TwistWithCovarianceStamped: 1
  twist_topic: /can_twist
imu_topic: /.../imu
gnss:
  velocity_source_type: 1 # rtklib_msgs/RtklibNav: 0, nmea_msgs/Sentence: 1, ublox_msgs/NavPVT: 2, geometry_msgs/TwistWithCovarianceStamped: 3
  velocity_source_topic: /.../gnss_rear/nmea_sentence
  llh_source_type: 2 # rtklib_msgs/RtklibNav: 0, nmea_msgs/Sentence: 1, sensor_msgs/NavSatFix: 2
  llh_source_topic:  /.../gnss_rear/navsatfix

sub_gnss:
  llh_source_type: 2 # nmea_msgs/Sentence: 1, sensor_msgs/NavSatFix: 2
  llh_source_topic:  /.../gnss_front/navsatfix

The terminal show me that:

Eagleye can't estimate the final pose
It seems eagleye doesn't use the latLonAlt info from sensor_msgs/Navsatfix for estimating the position (x, y, z).
I tried looking at the code to understand the problem. The function position_estimate can only be used for rtklib_msgs and nmea_msgs formats and not for sensor_msgs. If I'm right, that means we can use eagleye with sensor_msgs/NavSatFix. I hope my wrong.
void **position_estimate**(const rtklib_msgs::msg::RtklibNav, const geometry_msgs::msg::TwistStamped, const
eagleye_msgs::msg::StatusStamped, const eagleye_msgs::msg::Distance, const eagleye_msgs::msg::Heading, const geometry_msgs::msg::Vector3Stamped, const PositionParameter, PositionStatus*, eagleye_msgs::msg::Position*);

void **position_estimate**(const nmea_msgs::msg::Gpgga, const geometry_msgs::msg::TwistStamped, const eagleye_msgs::msg::StatusStamped, const eagleye_msgs::msg::Distance, const eagleye_msgs::msg::Heading, const geometry_msgs::msg::Vector3Stamped, const PositionParameter, PositionStatus*, eagleye_msgs::msg::Position*);

Kind regards
Please let me know if you want my bag and the modifs I did from eagleye.

Sorry, there might be a bug with the combination of velocity_source as nmea_sentence and llh_source as nav_sat_fix. Does nmea_sentence include GGA? If it does, you should specify nmea_sentence for llh_source.

Thank you. You can close this issue


renderAndGetWindow and virtualConsole option

Is your feature request related to a problem? Please describe.
I test a client part code under environment: Jest + Nuxt by using the method renderAndGetWindow. My project uses the Vuetify. But when i call:
let window = await nuxt.renderAndGetWindow(`${nuxtConfig.env.baseUrl}/`)

i got crash test because:
    console.log
      [error] Error: Could not parse CSS stylesheet
          at Object.<anonymous>.exports.createStylesheet (/home/perlover/src/my-project/node_modules/jsdom/lib/jsdom/living/helpers/stylesheets.js:34:21)
          at HTMLStyleElementImpl._updateAStyleBlock (/home/perlover/src/my-project/node_modules/jsdom/lib/jsdom/living/nodes/HTMLStyleElement-impl.js:68:5)
          at HTMLStyleElementImpl._poppedOffStackOfOpenElements (/home/perlover/src/my-project/node_modules/jsdom/lib/jsdom/living/nodes/HTMLStyleElement-impl.js:42:10)
          at OpenElementStack.Object.<anonymous>.OpenElementStack.pop (/home/perlover/src/my-project/node_modules/jsdom/lib/jsdom/browser/parser/html.js:43:12)
          at Object.endTagInText [as END_TAG_TOKEN] (/home/perlover/src/my-project/node_modules/parse5/lib/parser/index.js:2153:20)
          at Parser._processToken (/home/perlover/src/my-project/node_modules/parse5/lib/parser/index.js:657:55)
          at Parser._processInputToken (/home/perlover/src/my-project/node_modules/parse5/lib/parser/index.js:684:18)
          at Parser._runParsingLoop (/home/perlover/src/my-project/node_modules/parse5/lib/parser/index.js:440:18)
          at Parser.parse (/home/perlover/src/my-project/node_modules/parse5/lib/parser/index.js:344:14)
          at Object.parse (/home/perlover/src/my-project/node_modules/parse5/lib/index.js:10:19)
          at parseIntoDocument (/home/perlover/src/my-project/node_modules/jsdom/lib/jsdom/browser/parser/html.js:216:17)
          at parseIntoDocument (/home/perlover/src/my-project/node_modules/jsdom/lib/jsdom/browser/parser/index.js:31:10)
          at new JSDOM (/home/perlover/src/my-project/node_modules/jsdom/lib/api.js:42:5)
          at /home/perlover/src/my-project/node_modules/jsdom/lib/api.js:142:16
          at processTicksAndRejections (internal/process/task_queues.js:97:5)
          at renderAndGetWindow (/home/perlover/src/my-project/node_modules/@nuxt/server/dist/server.js:122:22) .theme--light.v-application {
...
      .v-virtual-scroll__item {
        left: 0;
        position: absolute;
        right: 0;
      }
      /*# sourceMappingURL=vuetify.css.map*/

      at formatLogObj.width (node_modules/consola/dist/consola.js:1:15971)

This happens as i understand because the cssom module cannot parse CSS from Vuetify. I used a fresh version of cssom but it didn't helped to me. So i think cssom will not parse the Vueitify's CSS a long time yet.
After researching your code i cannot resolve this problem beause:

If i use virtualConsole option of renderAndGetWindow as false i get error from JSDOM that the virtualConsole should be object (it other problem of your doc - i cannot use virtualConsole as false but your doc tells to me that i can do it)
If i do my own instance of virtualConsole with ignoring of (virtualConsole = new jsdom.VirtualConsole().sendTo(consola, { omitJSDOMErrors: true }) ... await nuxt.renderAndGetWindow(${nuxtConfig.env.baseUrl}/, {virtualConsole}) ) i got crash again because your code of renderAndGetWindow redefines jsdomError event by on calling to my instance to your jsdomErrHandler in anyway.

https://github.com/nuxt/nuxt.js/blob/dev/packages/server/src/jsdom.js#L45
Describe the solution you'd like
I think the line https://github.com/nuxt/nuxt.js/blob/dev/packages/server/src/jsdom.js#L45 should be upped in block of if before https://github.com/nuxt/nuxt.js/blob/dev/packages/server/src/jsdom.js#L43 line. if you create an instance object of virtualConsole yourself, only in this case you should add handler jsdomError to it otherwise the developer is not able to fully use the option of virtualConsole for own instance.

We are approaching the Nuxt 2 EOL date (June 30, 2024) - see this article for more information. I'm closing this issue as it's marked as a Nuxt 2 related enhancement and it's not a critical issue.
That doesn't mean it might not be relevant for Nuxt 3. If it is, please feel free to open a new issue (or just comment, and I can reopen it). 🙏
Thank you for your understanding and for your contribution to Nuxt! 🎉


Inability to navigate back

Once you go into a nested folder, it is not possible to navigate backwards. For example:

I can't get back to the Adding Pages folder or to the root folder support-documentation.
I always have to restart the process again.

@sanjawirch You can either click on breadcrumbs (Amazone S3:// support-documentaion /adding new page)
Or you can press browser's back both should work. (This is useful during multipage pagination )
Does this help's you?

The breadcrumbs don't work. They aren't clickable links.. neither does the back button. It's greyed out.

@sanjawirch I don't think you are using MyS3Browser. This is how it is supposed to look like. You screenshot look deferent

Yep.. you're right.. My bad. Sorry about that. I've been trying so many different ones to see which works best and must have confused that with yours.
Is there a way to delete an unwanted folder? I don't want to have the one that says Google + Webmaster

The only way to delete a folder in AWS is to delete everything inside it. :)

Ok, I will have a look. Will you be interested in opening a new GitHub issue for delete specific problem?


Fixes for Sphinx API demo documents

This PR contributes a few formatting fixes for PR #424 by @jeffrey856

Codecov Report

Merging #442 into jeff-sphinx-pages will not change coverage.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           jeff-sphinx-pages     #442   +/-   ##
==================================================
  Coverage              85.44%   85.44%
==================================================
  Files                     39       39
  Lines                   1862     1862
==================================================
  Hits                    1591     1591
  Misses                   271      271

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 fceeb5d...bb1f2cf. Read the comment docs.


Drop ctx argument from functions that don't need it

Drop the unused JSContext argument from several oft-used functions.
Non-functional change (strip build/qjs && ls -l build/qjs is the same before and after) but improves legibility, IMO. No change to the public API either.

JS_NewInt32 and js_int32 are the same, what is the reasoning for having "duplicate" implementations? Is it the force-inline?

Shall we drop JS_DupValueRT now?

JS_NewInt32 and js_int32 are the same, what is the reasoning for having "duplicate" implementations? Is it the force-inline?

No, it's purely stylistic / unclutter.
If we're okay with backwards-incompatible API changes, or versioning the API somehow, we could make the change directly to quickjs.h.

Shall we drop JS_DupValueRT now?

Good point! I was meaning to eradicate the two remaining calls from quickjs.c but I forgot. I'll fix that.
As to your general question: it serves no purpose so... yes?

JS_NewInt32 and js_int32 are the same, what is the reasoning for having "duplicate" implementations? Is it the force-inline?

No, it's purely stylistic / unclutter.
If we're okay with backwards-incompatible API changes, or versioning the API somehow, we could make the change directly to quickjs.h.

Shall we drop JS_DupValueRT now?

Good point! I was meaning to eradicate the two remaining calls from quickjs.c but I forgot. I'll fix that.
As to your general question: it serves no purpose so... yes?

I am somewhere near +0.5, I guess if we are doing a new thing might as well drop the baggage? OTOH, having existing compile as-is looks like a big plus, so let's have it!

I'll go ahead and merge this and then ponder for a bit whether or not to change the public API.


middleware "before" not working

All middleware is applied after the route or controller output. The middleware system needs to be improved in general. It is a WIP. So, if anyone wants to suggest/make improvements, please do.

It looks as if you were working off an example, could you share the source? I might be able to get namespaces working.

No example...I just hacked at it up to this point.
What do you mean regarding namespaces? Everything works for me, except middleware is only applied after the route or controller response changes. We may need another issue for your situation and namespaces.

I meant to say middleware, sorry.

@Cleanse NP. I am hacking at it some more. Have not made much progress.

completed with PR #130


Scalar from random issue

When we create a Scalar object from Random data, it doesn't have the same input validation as FromBytes, this seems like a bug, (but I'm not sure because the input it's different).
https://github.com/neo-project/Neo.Cryptography.BLS12_381/blob/844bc3a4f7d8ba2c545ace90ca124f8ada4c8d29/src/Neo.Cryptography.BLS12_381/Scalar.cs#L44
https://github.com/neo-project/Neo.Cryptography.BLS12_381/blob/844bc3a4f7d8ba2c545ace90ca124f8ada4c8d29/src/Neo.Cryptography.BLS12_381/Scalar.cs#L60-L74
Note: The same happens with FpX

See check the Unit Test They all checkout.

They are different, as wide means wide, it takes longer input, please check out the original implementation here:
https://github.com/zkcrypto/bls12_381/blob/4df45188913e9d66ef36ae12825865347eed4e1b/src/scalar.rs#L300

please check out the rust implementation here: https://github.com/zkcrypto/bls12_381/blob/4df45188913e9d66ef36ae12825865347eed4e1b/src/scalar.rs#L300

But if you initialize from bytes and you have a restriction, if you init from random bytes, you should have the same restriction, isn't it?

class MyRand : RandomNumberGenerator
{
    public static readonly byte[] INVALID = new byte[]
    {
        1, 0, 0, 0, 255, 255, 255, 255, 254, 91, 254, 255, 2, 164, 189, 83, 5, 216, 161, 9, 8,
        216, 57, 51, 72, 125, 157, 41, 83, 167, 237, 115
    };

    public override void GetBytes(Span<byte> data)
    {
        INVALID.CopyTo(data);
        INVALID.CopyTo(data.Slice(Scalar.Size));
        //base.GetBytes(data);
    }

    public override void GetBytes(byte[] data) => throw new NotImplementedException();
}

[TestMethod]
public void TestBug()
{
    Assert.ThrowsException<FormatException>(() => Scalar.FromBytes(MyRand.INVALID));
    Assert.ThrowsException<FormatException>(() => new Scalar(new MyRand()));
}

if you debug the test, you can see that the first construction fail (Scalar.FromBytes), and the second one (new Scalar(new MyRand()) create internally a Scalar object with the same arguments of the firstone, without any failure.

Here is more clear
If we create the same method, but fixed inside the Scalar class:
public static Scalar FromBytesWide(ReadOnlySpan<byte> data)
{
    if (data.Length != Size * 2)
        throw new FormatException($"The argument `{nameof(data)}` should contain {Size * 2} bytes.");

    ReadOnlySpan<Scalar> d = MemoryMarshal.Cast<byte, Scalar>(data);
    return d[0] * R2 + d[1] * R3;
}

public static Scalar FromBytesWideFixed(ReadOnlySpan<byte> data)
{
    if (data.Length != Size * 2)
        throw new FormatException($"The argument `{nameof(data)}` should contain {Size * 2} bytes.");

    // create calling the safe constructor
    var d0 = FromBytes(data);
    var d1 = FromBytes(data.Slice(Size));
    return d0 * R2 + d1 * R3;
}

[TestMethod]
public void TestBug2()
{
    Assert.ThrowsException<FormatException>(() => Scalar.FromBytes(MyRand.INVALID));

    // It works! :S
    Scalar.FromBytesWide(MyRand.INVALID.Concat(MyRand.INVALID).ToArray());

    // It fail
    Assert.ThrowsException<FormatException>(() => Scalar.FromBytesWideFixed(MyRand.INVALID.Concat(MyRand.INVALID).ToArray()));
}

Your FromBytes method must be wrong?

Because Random does not mean random, it has format:
        ReadOnlySpan<Scalar> d = MemoryMarshal.Cast<byte, Scalar>(data);
        return d[0] * R2 + d[1] * R3;

You can not really generate a scalar here.

Because Random does not mean random, it has format:
        ReadOnlySpan<Scalar> d = MemoryMarshal.Cast<byte, Scalar>(data);
        return d[0] * R2 + d[1] * R3;

You can not really generate a scalar from arbitrary bytes here.

Look at my last sample, without random data

it has format

It could be, but different constructors with different formats, they should detail why those restrictions are not present there.

Well, i cant say you are wrong here, looks like it should exist a size check, but to be honest, having it or not will not cause any bug here, it will be converted to scaler span and only the first scaler will be used. So..... coding issue, not a bug.


core: apply Real affinity on columns stored as int

Values in sqlite3, as expected, can be stored in different formats to optimize disk usage. In this case, a 79.0 float will be transformed to a u8.
sqlite3 deals with this by adding a RealAffinity op after each column that might need it. Therefore, in this pr we do exactly that :).
Fixes #114

hmmm why is test failing?
> select * from users, products limit 1;
<EMAIL_ADDRESS>Johnson Rest Suite 322|West Lauriestad|IL|35865|94|1|hat|79.0

nevermind, it was missing a commit from cli/main.rs


Clear hour/minute/seconds display area before going to sleep

When i activate clock it is usually shows old time (which was at before sleep) and real time will be shown after delay for redraw (half of second or so).  This is quite annoying as i have to remember to wait for the screen redraw.
As hotfix i've added ttgo->tft->fillScreen() right before ttgo->displaySleep() in lowEnergy() function but this clears whole screen which is not needed. I think, better way is to clear only box where hour/minute/seconds are displayed and redraw them first, then all other fields but that will require to implement a function in every skin code.

This is mainly a problem with the Lily-Go watch face because that code is
so slow.
You could call ttgo->tft->fillRect() and clear the area where the time is
printed.
Bill Dudley
This email is free of malware because I run Linux.
On Sat, Apr 10, 2021 at 10:06 AM vasimv @.***> wrote:

When i activate clock it is usually shows old time (which was at before
sleep) and real time will be shown after delay for redraw (half of second
or so). This is quite annoying as i have to remember to wait for the screen
redraw.
As hotfix i've added ttgo->tft->fillScreen() right before
ttgo->displaySleep() in lowEnergy() function but this clears whole screen
which is not needed. I think, better way is to clear only box where
hour/minute/seconds are displayed and redraw them first, then all other
fields but that will require to implement a function in every skin code.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wfdudley/T-watch-2020/issues/37, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI4VYU2N6B4QIWYFEABDUGTTIBLN5ANCNFSM42WRK7GA
.


[New Port Request]

Library name: OIS
Library description: Cross Platform Object Oriented Input Lib System. Meant to be very robust and compatiable with many systems and operating systems.
Source repository URL: https://github.com/wgois/OIS
Project homepage (if different from the source repository): /
Anything else that is useful to know when adding (such as optional features the library may have that should be included): /

I'll see if i can make this port

Since this port has been added, I'm going to close this issue for now.
@vpaladino778  Thanks for your efforts to this issue.


Tidy up dependencies

Tidy up a couple of unneeded dependencies to reduce install load on users:

migrate from underscore to the more common lodash
Remove less as a dependency from @jpmorganchase/perspective

Thanks for the PR!  Changes looks good


Removed type from outputs

Here are two drawbacks of exposing type in outputs.

it’s in Terraform context, not friendly to Golang/Kubernetes
it’s complicated

Fix #274
Signed-off-by: Zheng Xi Zhou<EMAIL_ADDRESS>

LGTM


qwik for qwind is not as fast as expected.

https://qwind.pages.dev/ is as fast as my nextjs app but is nowhere close to https://qwik.builder.io/  which is very strange.
Given that qwik.builder.io uses same tailwind and quik , qwind should be closer to it.
I guess we are missing something, we haven't fully got the performance that we came here for.
Even your other templates like https://astrowind.vercel.app/ or https://onwidget.com/ or https://tailnext.vercel.app/ are faster.
Documenting last 5 measured scores on https://pagespeed.web.dev

Page
Mobile Speed
Median Mobile Speed
Desktop Speed
Mobile Desktop Speed

https://qwind.pages.dev/
83,96,95,96,96
96
100,100,100,100,100
100

https://qwind.vercel.app/
95,95,95,95,95
95
100,100,100,100,100
100

https://qwik.builder.io/
99,98,100,93,98
98
100,100,100,100,100
100

https://astrowind.vercel.app/
99,100,99,100,100
100
100,100,100,100,100
100

https://tailnext.vercel.app/
94,97,92,87,95,92,91,93,94
93
77,78,99,96,90,99,78,100,100
96

https://onwidget.com/
90
90
98
98

I tried both https://qwind.pages.dev and https://qwind.vercel.app to ensure the issue is not with hosting.
All your astro homes are superfast. As per most benchmarking is concerned qwik is the quickest. I expected qwik to be faster than astro but maybe for simple single page landing page astro beats qwik.
Anyway I would suggest keep this issue open unit we find out what's slowing it down.

Hi @ishandutta2007
Thank you very much for this report.
Qwind is certainly a bit abandoned. Qwind had 100% Page Speed but after several Qwik version updates it has been lost. And perhaps it is not a problem on Qwik but of changes that Qwind needs to adapt to the new versions. There are also updates that are needed from the interface point of view, talking about the way the code is organized.
As I told you before, Qwind certainly needs an update. We'll be on it soon.
Thanks again for this. We'll be in touch.

@prototypa Ahh great to know Qwind had a 100 too . do you remember which version should I revert it to try for a 100, were there any breaking changes introduced for updating the version to 1.2.13 or was it just updated to keep up with latest release ?


feat: communicate to runner about rate limit backoff

Opening this here but likely some other issues would be needed.
The basic problem is that if a connector hits a rate limit and is waiting for X amount of time to try again, Cloud should be aware of this waiting time and not charge for any credits.
We would need a way to communicate from the tap to the runner (cloud) that this wait is happening. Maybe a new message type?

These types of use cases where it'd be useful for the tap or target to communicate with the caller (metrics, backoff, etc.) are a bit hard to accomplish with the present design of the Singer CLI protocol.

Maybe a new message type?

An improved design would be, for example, for them to expose some kind of interface (grpc, REST, etc.) as soon as they start running that allows for that kind of information to be communicated to the caller. Similar to the proposal in https://github.com/MeltanoLabs/Singer-Working-Group/issues/7#issuecomment-1370959226


Create a landing page for the app

Fixes #146

@brafdlog Please set the gh-pages branch as the location of Github Pages in the repo settings, then you can review it.

Available in https://brafdlog.github.io/hiuvi/


Collect anonymous data action fixes

Previous the checks would not honor the flags so reworking that to handle the flags correctly.

Validate st2.call_home with both st2::collect_anonymous_data set and unset.

Merging.


AutoClosingReferenceStream and its Int,Long,Double variants does not support Java9

The methods Stream::takeWhile and `Stream::dropWhile' are not implemented in said classes.

See TakeWhileAction


Actions: Enhanced GitHub Actions Usage Metrics and Insights

Summary
Organization and Enterprise Admins can now better understand what is driving their GitHub Action use by repo, workflow and Organization. Organization Admins can now interact with information empowering them to answer questions like which repo is using the most minutes, which workflows have changed resulting in more use and how their split of minutes usage compares across different operating systems.
Intended Outcome
Previously, Admins had to look across a range of un-supported data sources extracting information and then still struggled to answer questions like ‘which workflow is driving the most use across all of my runner types’ or ‘which of my repositories are triggering workflow runs and how are those workflows being triggered’. Understanding how the answers to these questions change over time or in comparison to another repository’s usage required even more custom tooling. Enhanced Usage Metrics solves these problems and more.
How will it work?
The Actions Usage Metrics dashboard is customizable by date range and provides several filtering and summation tools for an organization's repositories.
Included metrics:
Billable minutes
User counts
Usage trends
Total usage forecasts
Data sorting column header
Data export (.csv format)
Successful workflow runs by invoking event (PR, Push, Merge, etc)
Successful workflow runs by runtime (macos, ubuntu, windows, etc)
Successful workflow runs by runner type (self hosted, hosted, custom)
Successful workflow runs by repository visibility (public or private)

This has shipped to a private beta!


Support file based recommendations in virtual workspaces

Support file based recommendations in virtual workspaces

Should we close this? What are virtual workspaces? What's the use case?

Examples of virtual workspaces are GitHub repos opened in Desktop without cloning. Use case is if I open a repo in GitHub and open a python file. We shall recommend extensions supporting the python file in virtual workspace.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


More dv queries supported for file/link suggestions

I started this PR as a result of a conversation on the Obsidian Discord (https://discord.com/channels/686053708261228577/1014259487445622855/1067595344671682621).
First I tried to write the dvjs query to achieve it. Here it is
```dataviewjs
[...dv.pages().map(p => p.subject).distinct()].reduce((acc, cur) => { if (cur) {return [...acc, cur]} return acc }, [])
```

It was messy and i kept having errors. So I took a look in the code and noticed that the getFiles method of FileField.ts and MultiFileField.ts expected the getResults() function to return an object with a values field.
I still don't understand what the proxy target returned by dv.pages() contains because at first glance, the .values property looks like a perfectly normal array but I can't call .filter() on it without triggering an error for some reason :/. I can't call instanceof Proxy to differentiate it from a normal array but I found another way to find out: If results.values is an object then results is a proxy, otherwise it is a regular array (I'm doing a reduce to remove the undefined results in that case).
On top of that, I simply put additional if checks inside the map callback so that if the dataview query written by the user returns an array of TFile, then it will work (as before) but if they want to call the .map method next to the dv.pages() to return an array of Link instead, that will also work.
To summarise: Before this pr, the only thing you could write inside the optional dv query of a file/multiFile field was a single dv.pages() with a predicate inside. So you couldn't implement custom filtering that fetches its values on the fly. Now the following should also work:
```dataviewjs
// For MultiFile field
[...dv.pages().map(p => p.subject)].flat()

// For SingleFile field
dv.pages().map(p => p.subject)
```

Also, I couldn't help but isolate this piece of shared logic into its own file, then import it into both FileField.ts and MultiFileField.ts ^^'
I'd be happy to hear your comments on this.

Hi, that's a great improvement. could you add some user documentation for it here: https://github.com/mdelobelle/metadatamenu/blob/master/docs/settings.md#file-multifile-options ?

To reduce friction on the end-user side, I rewrote the getFiles function so that it can handle tricky situations (instead of assuming that the end user will figure it out on his own...)
For the following example, I assume that the end user wants to force the suggester to show him only links he has already defined on a specific field in his vault.
Let's assume that what's below is what is set as dv query in the field manga's settings
dv.pages().map(p => p.manga)

So, in my previous commit, if you had, in a file, a property containing an array of links like that manga:: [[One Piece]], [[Naruto]], nothing appeared in the suggestion because Arrays weren't supported by the getFiles function. So the end user had to modify its dv query as follows to make it work:
[...dv.pages().map(p => p.manga)].flat()

For a non-developer, this introduces some error-prone weird syntax, so I think it's better to have it handled directly in the codebase. And that's what I did. Now the first query works as expected for the end user.

Looking through the code, I also noticed how similar FileField.ts and MutiFileField.ts are. About 95% of their content is identical. At first I didn't really understand the point of separating these two field types, but I kind of get it now. Although it would be much cleaner to abstract most of their code inside a common file, what do you think?

Also I've fixed the sorting part example in the documentation

Thanks a lot, i'll merge that and release in 0.4.18

Looking through the code, I also noticed how similar FileField.ts and MutiFileField.ts are. About 95% of their content is identical. At first I didn't really understand the point of separating these two field types, but I kind of get it now. Although it would be much cleaner to abstract most of their code inside a common file, what do you think?

You're absolutely right, it was pure lazyness 🙂 . I've refactored the common code in AbstractFileBasedField and included your FileFieldUtils in it.


Fixed hostname for compute GUI

Fixed hostname for compute GUI

@sasikeda Can you please merge the PR.


Type substitution: When substituting SILFunctionTypes we substitute u…

…nbound Objective-C generic for bound ones
IRGen does so. So don't assert on this case.
rdar://63509292

@swift-ci Please test

IRGen's behavior has caused problems in the past. I think it's a bit of a hack. This fix is totally fine but it would be nice if we could wean IRGen off of UnboundGenericTypes entirely. They should not exist after type checking.

IRGen creates it here:
// Get the type that exists at runtime to represent a compile-time type.
CanType IRGenModule::getRuntimeReifiedType(CanType type) {
  // Leave type-erased ObjC generics with their generic arguments unbound, since
  // the arguments do not exist at runtime.
  return CanType(type.transform([&](Type t) -> Type {
    if (CanType(t).isTypeErasedGenericClassType()) {
      return t->getAnyNominal()->getDeclaredType()->getCanonicalType();
    }
    return t;
  }));
}

Yeah, it seems like whoever consumes the result of that is unable to handle a BoundGenericType whose decl is an Objective-C generic class. It seems like it would be easier to fix that code to instead ignore the generic arguments there, rather than performing this transformation in the right place.

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@slavapestov Part of the issue is that we (at least historically) rely on the type identity being the same for types that are equivalent at runtime in parts of IRGen. There's likely to be better ways to do that, though.

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please test linux

Build failed
Swift Test Linux Platform
Git Sha - 532f0cb865cccae01abb5b1c933b8510b27dcd81

@swift-ci Please smoke test linux


ko install not working in github actions.

I was debugging suddenly starting to fail installations of ko in our github.com/knative-sandbox/eventing-rabbitmq kind e2e tests. After trying a few different things, I just created a clean repo with no code in it and a single github action that install go and ko. This also fails. I had seen a few issues with folks installing and maybe having conflicts, or old installations, but since this is just running github actions and there's nothing else going on, seems like it's a real issue? Or am I just holding it wrong?

The work around seems to be to install it manually by fetching it via curl as done here:
https://github.com/knative-sandbox/.github/pull/81/files
If this is not how it should be done, should we maybe document that for github actions you should curl & install it (readme sez to go get it still).

The work around seems to be to install it manually by fetching it via curl as done here:
https://github.com/knative-sandbox/.github/pull/81/files
If this is not how it should be done, should we maybe document that for github actions you should curl & install it (readme sez to go get it still).

simpler example
$ docker run -e GO111MODULE=on -t golang:1.15 go get github.com/google/ko

simpler example
$ docker run -e GO111MODULE=on -t golang:1.15 go get github.com/google/ko


Can an API on CompletionQueue return an iterator of CQEs?

Should CompletionQueue::wait_for_cqes and IoUring::wait_for_cqes actually return a vector of completion events, and then advance the queue by count entries?
Consider the following example, where I send 16 NOPs and then wait for 16 events, 16 times.
fn wait_multiple() {
    let mut iou = IoUring::new(16).expect("Can't create queue");
    let (mut sq, mut cq, _) = iou.queues();

    for _ in 0..16 {
        let mut sqe = sq.next_sqe().unwrap();

        unsafe {
            sqe.prep_nop();
        }
    }

    // I'd expect the second iteration to block, but it doesn't
    for n in 0..16 {
        println!("[{}]: Waiting for 16 events", n);
        let cqe = cq.wait_for_cqes(16).unwrap();
    }
}

It looks like Iou is correctly sending count entries, but then it just wraps the first result, which automatically advances the CompletionQueue by one entry when dropped.
I took a crack at returning an array of completions which seems to work, although I'm not sure if advancing by 1 for each dropped event in the vector is the right strategy, or even sound.

The correct way to use this API would be to then call peek_for_cqe 15 times. Returning a vec would require a heap allocation, which is not ideal.
We could find a way to drop the CQEs as one modification instead of 16, to reduce the number of allocations. Probably we'd expose the io_uring_cq_advance function as an (unsafe?) API on IoUring and CompletionQueue and then users would have to mem::forget their CQEs and call that explicitly.
We could also possibly add an API which constructs an Iterator of CQEs. Not sure how to optimize advancing in that case.

Oh OK that totally make sense, thank you for the clarification!

I do think an iterator of CQEs is possible, and possibly it can even advance once, instead of N times.
I think we could even use the same iterator type for a "wait" and "peek" multiple interface, by having the wait one just call the wait API before constructing the iterator.
I'm going to re-open and re-name to track this possibility.

The tricky bit:
Iterators have to be able to return multiple of their items with overlapping lifetimes. That is, you would have to get multiple CQEs out of the iterator. This is problematic with the way that CQE advances when it drops, because you could drop them in a different order from the order they actually appear in. So it would have to solve the drop once problem.
We'd want to make CQEs contain some flag to check whether they should advance, and only advance in their drop based on the setting of the flag. Possibly this flag could be simply whether or not the pointer to the io_uring is null or not. Not too hard.
Then, we'd need to track the number of CQEs we have returned in the iterator impl, so that it knows how far to advance.
This all seem plausible to me. And an iterator interface would be much nicer than the one we have now. I'll mess around and think about it more.

That sounds really cool.  Happy to help test if it does prove feasible.

The problem is that it can't be an iterator because each CQE needs to borrow from the iterator, to make sure that cq_advance is not called until after all the CQEs have dropped. It's still a better interface though. I have a branch, you can write code like this essentially:
while let Some(cqe) = ring.wait_for_cqes(n) {
     // process CQE
}

// OR

ring.wait_for_cqes(n).for_each(|cqe| {
    // process CQE
})

This will be implemented in iou 0.3


Question about binary head

Thanks for your great work and high-quality open-source code! I have some questions regarding the paper.
Since the open vocabulary problem can only access the annotation of the base categories during training, how are the ground-truth labels (i.e., y^{b} in Eq(4) of the main paper) indicating the base and novel categories set when calculating the binary loss (Eq(4) of the main paper)? Theoretically, any information about the novel class should be unseen during the training.

Hello, we regard all unannotated points other than base-categories as the novel categories points. We think it will be better to recognize this as unseen category points

Thanks for your timely reply! My question is solved.


plugins: Add ccc (new PR)

The option `plugins.ccc.default_color' does not exist.
What does this error mean?

The test is malformed. Probably an issue with my suggestion. I suspect you need to nest your non-enable options in a settings block;
plugins.ccc.settings.*

I think I need to create a new pull request. At least I don't see how I could append to this one

You would've been able to either push up more commits implementing the changes or used one of many methods of amending history followed by a --force push.
History can be edited several ways, such as

git commit --amend to update the latest commit, git reset --soft <some ref>
git reset --mixed <some ref>, followed by making a new commit
git rebase --interactive <some ref> to do more advanced stuff

You can also use lazygit's interface to abstract a lot of that.
I'd highly recommend learning some of gits fundamentals and advanced features when you get chance.

Note that we can squash the commits when merging too

I changed the option to enum and addressed some of the comments on formatting. I wasn't sure how to format the text, went with 80 char max line width were it seemed appropriate. Is there a guideline for such styling?


[zh] translate content/zh/docs/reference/scheduling/policies.md

Problem:
https://kubernetes.io/zh/docs/reference/scheduling/  is missing in Chinese version.
See  more: https://kubernetes.io/zh/docs/reference/scheduling/
Proposed Solution:
Add /docs/tasks/configmap-secret/ to zh version with three articles to be translated.

[x] /zh/docs/reference/scheduling/policies.md

Page to Update:
https://kubernetes.io/zh/docs/reference/scheduling/policies

/assign @tengqm @tanjunchen

/assign @tengqm @tanjunchen

@chenrui333 please take a look 😭 , it has been stuck for two days...

/lgtm
/approve


increase nps survey probability

LGTM.  Please merge and create a port request.  In interest of time and simplicity of the code I'd recommend not waiting for CI to complete (they'll run in release branch in any case).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.002%) to 42.196%

Files with Coverage Reduction
New Missed Lines
%

extensions/machine-learning/src/common/processService.ts
3
77.78%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
27752

Relevant Lines:
61529

💛  - Coveralls


"pluginname:command" is considered invalid

Let's say, for example, I register the command "test" in my plugin "testplugin".
I can now use the command "/test" and everything works fine.
However, if I try to type "/testplugin:test", it even shows up in auto-completion, but when executed it states "Invalid command: testplugin:test" (Just in plain text, not as brigadier error or something like that).
So the command seems to get registered correctly even in the mentioned form, but it is still considered invalid in some way
An example from a current project of mine:

(Just "/checktarget" works fine in this case)

I have also noticed, that the auto-completion for the mentioned form of a command is displayed to a player even if they do not have the specified command permission, in oppose to the normal format, which is completely hidden in that case

That's indeed a bug. I'll look into it when I get a chance. Thanks for the notice.

Seems to be fixed in https://github.com/Revxrsal/Lamp/commit/c54fcfbcb9139fcccb8f5bb3f0e3f49bcaf66901. Thanks for the report!


issue links on CHANGELOG.md are not directed to ibm/kui/issues

We should change the the link address from starpid/kui/issues to ibm/kui/issues.

should be resolved now


Add park table

In this PR I added requisite files for implementing a table for park objects. The files passed all local tests.

dont merge until I fix the coverage issue


Index Out Of Bound.

Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: Index 64 out of bounds for length 64 	at com.paritytrading.philadelphia.FIXValue.setString(FIXValue.java:261) 	at com.paritytrading.philadelphia.FIXConnection.prepare(FIXConnection.java:251) 	at com.paritytrading.philadelphia.FIXConnection.prepare(FIXConnection.java:232) 	at org.jvirtanen.coinbase.fix.Example.main(Example.java:120) 	at org.jvirtanen.coinbase.fix.Example.main(Example.java:34)
Please help me to sort out this issue.

Hi @kavikumarN! It looks like the field capacity should be increased from 64 to something suitable, e.g. 128, with FIXConfig.Builder#setFieldCapacity(). Would you like to open a pull request for this?


Add Xamarin support to NLog packages

Currently the NLog packages can't be used in a Xamarin.iOS project. NuGet throws the following error when trying to install the Common.Logging.NLog41 package, even when using Beta2:
Could not install package 'Common.Logging.NLog41 3.4.0-Beta2'. You are trying to install this package into a project that targets 'Xamarin.iOS,Version=v1.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
For me it looks like the NLog package is a .Net library only. That may be the cause.

Confirming that NLog 4.1 only support full .NET Framework (see https://www.nuget.org/packages/NLog/4.1.0).  Closing this issue accordingly.

I'm not sure what you're referring to but according to http://nlog-project.org/ NLog supports the following platforms:

.NET Framework 3.5, 4, 4.5 & 4.6
Xamarin Android
Xamarin iOs
Windows Phone 8
Silverlight 4 and 5
Mono 4
ASP.NET 4 (NLog.Web package)
ASP.NET Core (NLog.Web.AspNetCore package)
.NET Core (NLog.Extensions.Logging package)

I've successfully used Common Logging in conjunction with NLog (not directly using the NuGet Packages but building the projects on my own). Can I provide any help?

[Re-opening this issue]
Actually, yes.  If you're willing it would be helpful if you could assist in confirming/validating several of our conclusions.

For clarity, our conclusion as to NLog support for other TFMs than the full .NET Framework is specifically about NLog 4.1.  We'd focused on that version of NLog b/c the original post referenced a repro that involved that specific version of NLog.  When we installed the NLog 4.1 NuGet package into a new/empty folder (e.g., "nuget.exe install nlog -version 4.1") the resulting /lib/ folder structure contains binaries for the full .NET Framework and SL4 + 5, but definitely not Mono.  Could you attempt to add NLog 4.1 to a Mono project (not involving Common.Logging at all) and advise whether this is supported?  We suspect not, hence the closure of this issue, but we may well be wrong too :)

I'm not certain, but I believe that list of supported TFMs for NLog you are referencing is in re: the latest version of NLog (i.e., 4.4.11, https://www.nuget.org/packages/NLog/4.4.11 or even perhaps 5.0 beta).  Could you attempt to add Common.Logging.NLog4411 (https://www.nuget.org/packages/Common.Logging.NLog4411/3.4.0) to a Mono project and advise your results?  With the (recent) release of Common.Logging 3.4 to GA, Common.Logging.NLog4411 is expected to be a combination of dependencies that should properly support Mono.

Thanks in advance for you willingness to assist on this!

You are totally right: NLog 4.1 does not support Xamarin.iOS but 4.4.11 does. I tried to install the according NuGet Packages into an iOS project.
Installing NLog 4.1 returns the error: Could not install package 'NLog 4.1.0'. You are trying to install this package into a project that targets 'Xamarin.iOS,Version=v1.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Installing NLog 4.4.11 is successful. But installing Common.Logging.NLog4411 (version 3.4.0) returns the error: Could not install package 'Common.Logging.NLog4411 3.4.0'. You are trying to install this package into a project that targets 'Xamarin.iOS,Version=v1.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author..
Common.Logging.NLog4411 contains only a dll for net40, non for Xamarin.iOS10.

Thanks for the input and the error report.
I'll take a look @ the Common.Logging.NLog4411 package and see what went wrong.  Clearly there's a packaging problem on our end; if NLog 4411 supports those broader list of targets then we should be providing a matching binary in Common.Logging.NLog4411 for each as well.  I'll dig into it shortly and advise.
When (we think) we've got it fixed, we'll release a set of 3.4.1-Alpha1 packages.  We'd appreciate it if you'd be willing to test this again once that's pushed to NuGet, as I've not got Xamarin installed on any of my systems running Visual Studio and I'd rather not spend the ~40GB in disk space for 20 versions of Java just to test the NuGet installer results if I can avoid it :)
Thanks again!

Sure. Just let me know and I'll test your NuGet Beta packages.

@MKuckert I'm trying to determine specifically what PCL profile(s) are needed for Xamarin support.  From this section in the Xamarin docs comes the following excerpt (emphasis mine):

The Xamarin column reflects the fact that Xamarin.iOS and Xamarin.Android supports all the profiles shipped with Visual Studio 2013 and above, and the availability of features in any libraries you create will only be limited by the other platforms you choose to support (such as Windows Phone or Windows Store).
This includes profiles that are combinations of:

.NET 4 or .NET 4.5
Silverlight 5
Windows Phone 8
Windows Store Apps

If that's correct, then it would seem on its surface that the binary in the Common.Logging.NLog4411 package (e.g. in the net40 folder) should be compatible with Xamarin (?)  If this is true, then it would seem that just a change to the NuGet package to place the same binary into a Xamarin.iOS folder would be all that's required to properly support Xamarin.
Would you be willing to perform the following test and advise results?

Grab the binary from the Common.Logging.NLof1411 package (net40 folder)
Reference it (by hand, not via NuGet) into your Xamarin project.
Build/run and report results

If Xamarin.iOS is really a superset of net40 as this reference doc excerpt implies, its not at all clear to me why NuGet wouldn't accept the net40 binary package into a Xamarin.iOS-targeted project.  But if this section is correct, then a simple adjustment to the structure of the NuGet package would seemingly be all that's needed here.
Thanks in advance for you (continued) help~!

I just tested the referencing as suggested and you're right: I can successfully reference and leverage the Common.Logging net40-dlls from within my iOS project. The NLog adapter can be used with this setup 👍 But I have to target NLogs Xamarin.iOS to work – the net40 dll throws any type not found exception otherwise. But that's no problem in the case of installing via NuGet.
So yes, you should be able to use the net40 dll when bundling the NuGet package to target Xamarin.iOS projects as far as I understand.

Thanks for the validation.  We've pushed 3.4.1-RC1 packages to NuGet.
As a final test/verification before we release this change formally, would you be willing to attempt to add this pre-release version of the Common.Logging.NLog4411 package to your Xamarin project and report results?
Assuming you report OK, we'll move to 3.4.1-GA and publish that shortly (along with a similarly-configured package for NLog 4.4.12, which we noticed has just been released in the last week).
Thanks again for your continued assistance on this; its much appreciated~!

Looks very good! I can successfully install the NuGet package 3.4.1-RC1 in an iOS project. The NLog dependencies are successfully resolved and installed. 👍

Excellent; we'll release this to NuGet (along with parallel support for NLog 4.4.12) later today.
Thanks again~!

Resolved in https://github.com/net-commons/common-logging/tree/3.4.1.GA


Increase coverage

By running tox -e coverage it is possible to obtain a coverage html report which contains interactive pages of the showing tested and untested lines.
It would be interesting to increase overall skaero coverage by adding more tests, which would give us more flexibility if a reformat of the code is needed.

I will try to work on this during this week!


InvalidOperationException: JSRuntime must be set up correctly and must be an instance of JSRuntimeBase to use DotNetObjectRef.

I have created a blazor server app in Visual studio preview 2019 and Blazor.Extensions.SignalR (0.2.0). Getting an error when I am trying to listen the signalR message and reloading the table.Do I missed any namespace or something else?
Here my code is,
ViewLog.razor file
@page "/ViewLog"
@using Telerik.Blazor;
@using Telerik.Blazor.Components.Grid;
@using Microsoft.WindowsAzure.Storage;
@using Microsoft.WindowsAzure.Storage.Table;
@using System.Threading.Tasks;
@using WcomLogViewerBlazor.Models;
@using Microsoft.Azure.Documents;
@using Blazor.Extensions;
@using Microsoft.AspNetCore.SignalR;
@using Microsoft.Extensions.DependencyInjection;
@using System.Net.Http;
@using Microsoft.JSInterop;
@using Newtonsoft.Json;
[Inject] private HubConnectionBuilder _hubConnectionBuilder { get; set; }
private HubConnection connection;
private IJSRuntime _runtime;
// Listen SignalR messages and update table
protected override async Task OnInitAsync()
{
    var BaseUrl = "http://localhost:7071/api/SignalRInfo";
    var resonse = await client.GetStringAsync(BaseUrl);
    var responseInfo = JsonConvert.DeserializeObject<Models.ConnectionInfo>(resonse as string);
    var URL = responseInfo.URL;
    var token = responseInfo.AccessToken;
    this.connection = this._hubConnectionBuilder
        .WithUrl(URL,
        opt =>
    {
        opt.LogLevel = SignalRLogLevel.Trace; // Client log level
    opt.Transport = HttpTransportType.WebSockets; // Which transport you want to use for this connection
}) .Build();
    connection.On<string>("TableUpdated", this.OnBroadcastMessage);
       await this.connection.StartAsync();
}

startup.cs
        services.AddTelerikBlazor();
        services.AddTransient<HubConnectionBuilder>();
        services.AddSignalR();

Project.csproj file

Hello, thanks for the info.
However, I think you are on the wrong place here. You are using the official Microsoft Client for SignalR. That is only available on Blazor Server Side.
This repo here however, only focus on the client side.
Thank you! I'm closing the issue.

Thanks for your replay .I have just installed "SignalR.Client" namespace but I never used that namespace anywhere in my project.I suppose to uninstall it. Actually I have created Hub in Azure function serverless application.Here In Blazor application ,sending request to get a connection info from Azure serverless Application and pass the "SignalR Service URL" to establish the conncetion .
Here is code where I used for Hub creation :
public static class SignalRInfo
{
[FunctionName("SignalRInfo")]
public static IActionResult Run(
[HttpTrigger(AuthorizationLevel.Anonymous)] HttpRequest req,
[SignalRConnectionInfo(HubName = "ViewLogger")] SignalRConnectionInfo connectionInfo,
ILogger log)
{
return new OkObjectResult(connectionInfo);
}
}
Function for sending Message to SignalR:
public static void Run([QueueTrigger("logqueue")]string myQueueItem,
[Table("LogJournal"), StorageAccount("AzureWebJobsStorage")] ICollector<Models.LogItem> items,
[SignalR(HubName = "ViewLogger")] IAsyncCollector signalRMessage,
ILogger log)
This is output for azure serverless Apllication:
Http Functions:
    SignalRInfo:  http://localhost:7071/api/SignalRInfo

    WriteLog: [GET,POST] http://localhost:7071/api/WriteLog

[14/08/2019 14:29:18] Host lock lease acquired by instance ID '0000000000000000000000000A68584A'.


Deployment checklist

Let's enumerate the steps that are needed to get this project to a "deployable" state. I'll start with a high-level list and then work on turning each item to its own issue.
For reference, here is the database diagram we created to map out the different entities we will need.

[ ] #14
[ ] #11 - this is a required foreign key for recipe_runs
[ ] #12 - this is a required foreign key for recipe_runs
[ ] #15 (add, update, delete, etc); needed for bakeries / workflows to be able to securely post their runs
[ ] #16 for Heroku

I've added the deployment checklist label to

[ ] #8

This is not an especially heavy lift, and it seems worth making these improvements to the recipe run table pre-deployment. If any aspect of this turns out to be especially involved (e.g. output field) we can always just complete a subset of this to start.

Looks like #15 is the last thing left on this checklist 🎉


Asset licenses?

Are your assets (like art) licensed the same way as your code, or differently?

Short answer - No. Art in this game is owned by stremena.com. For sound & music please check the relevant assets links.


merge gingko feature

hi @albsch sorry I intended to send this PR to the vaxine repo before it's merged - it needs further work! I'll close this & re-open it when we're ready.


Add wrapper functions for parsing and serializing

Add basic sanity tests

I think we have enough of a feature set to ship 1.0 with this :D

LGTM


initial base class setup, apply_shuffle method

Thanks, @bsweger !  Do you want to re-review based on changes in 19d4a5a?  I am going to be lazy in this moment and fix up documentation later.  And am holding off on changes to set up for text fixtures until I see what ends up being put in place in the next couple of rounds of updates.


Issue with HTML5 player

Well I got just forcefully switched over to HTML5 (firefox), could change it back to Flash in Youtube Center, but that's not my issue as I would love to just be able to delete Flash.
My issue is that I have a 16:10 monitor, and apparently youtube's HTML5 player doesn't like 16:10 aspect ratio as when I go in full screen the video itself is shoved to the bottom and a big black bar at the top.

instead of the normal/usual black bars top&bottom with the video in the center of the screen

I know this isn't exactly a Youtube Center issue, but would be great if YTC could fix that as I doubt google will even care, considering that issue has been there for a long time now.
I tried with Chrome, this issue doesn't happen there, only on Firefox.

Can't test this issue because I don't have a 16:10 monitor to test the fullscreen behavior, but the player adjusts itself to the screen wether or not you set the AR to 16:10. Try setting it to 16:9 instead.
Also try the latest developer version if you haven't already, it can be downloaded from here: https://github.com/YePpHa/YouTubeCenter/wiki/Developer-Version


fix race conditions in ratelimit

Proposed Changes

fix race conditions (concurrent map writes) in MultiLimiter
minor improvement with closing token channel
adds -race flag in github action build workflow
Commented/removed SleepandReset method due to since it is not stable and needs improvements and has race conditions (requires entire change of logic)
adds AddandTake(opts *Options) method #23
resolves https://github.com/projectdiscovery/nuclei/pull/3257

closes

#23
#26

New Changes

time is now roundoff to Millisecond accuracy in MultiLimiter
time comparsion is done in nanoseconds (int64)


Minor doc edits

Made the "Run it with" paragraphs for pip-compile and pip-sync
consistent.
Removed the extraneous "Run it with" paragraph for pip-sync.

Contributor checklist

[ ] Provided the tests for the changes.
[x] Assure PR title is short, clear, and good to be included in the user-oriented changelog
[x] Assure one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
[x] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

The Label should be docs and the Milestone should be the next release (6.2.1 or 6.3.0).


Update httpclient.coffee

Does this PR correlate with this issue? https://github.com/KasperDeng/Hubot-WeChat/issues/25


Rename "paramKey" → "key" for paramChanged

#simplify

Clean up P5Project while we're at it (remove public next to resized)


Implement system level export operation

Adding the system level /$export operation, which should include all resources within the Project that the user has access to.

Coverage: 94.03% (-0.03%) from 94.057% when pulling 3160890b39db97c7db9d3076f80339b087fb6992 on system_export into 60ce7962269d3cbbcbb32bc61e913707cf2d4982 on main.

Looks like Sonar doesn't like that these blocks are duplicated:
  // Update the BulkDataExport
  await systemRepo.updateResource<BulkDataExport>({
    ...bulkDataExport,
    meta: {
      project: (res.locals.project as Project).id,
    },
    status: 'completed',
    transactionTime: new Date().toISOString(),
    output: Object.entries(exporter.writers).map(([resourceType, writer]) => ({
      type: resourceType as ResourceType,
      url: getReferenceString(writer.binary),
    })),
  });

  // Send the response
  res
    .set('Content-Location', `${baseUrl}fhir/R4/bulkdata/export/${bulkDataExport.id}`)
    .status(202)
    .json({
      resourceType: 'OperationOutcome',
      id: randomUUID(),
      issue: [
        {
          severity: 'information',
          code: 'informational',
          details: {
            text: 'Accepted',
          },
        },
      ],
    });

We could fix by moving some into the BulkExporter class as utilties (i.e., set status to completed on finished inside the class).
We could create a new constant accepted OperationOutcome here along with other constant OperationOutcome resources: https://github.com/medplum/medplum/blob/main/packages/core/src/outcomes.ts
The OperationOutcome
We can also file those as a follow-up task.


Add #[default]

Where T::Default, unsure how to annotate it for a function.

Hi, thank you for creating the issue! If you are looking for an attribute that makes the argument for a function optional, then there is such an attribute. It's called #[builder(default)]. Here is an example of how it can be used:
use bon::builder;

#[builder]
fn greet_user(
    #[builder(default)]
    level: u32,

    // The expression of type `&'static str` is automatically
    // converted to `String` here via `Into` thanks to `#[builder(into)].
    #[builder(into, default = "anon")]
    name: String,

    // Any complex expression is accepted
    #[builder(default = bon::vec!["read"])]
    permissions: Vec<String>,
) -> String {
    format!("Hello {name}! Your level is {level}, permissions: {permissions:?}")
}

let greeting = greet_user().call();

assert_eq!(greeting, "Hello anon! Your level is 0, permissions: [\"read\"]");

Here are the docs for this attribute in the reference. If you found it hard to find in the docs, and you have any ideas how to improve its discoverability, I'd be happy to hear them 🐱

I see, thanks!