Mask only secrets

The user has a possibility to decide if a variable should be masked.
If the user doesn't want to decrypt secret variable, then what's the point to mask encrypted value?
The problem is described here https://github.com/dkershner6/aws-ssm-getparameters-action/issues/42

In case of no actions here I will have to publish my fork as new GitHub Action on marketplace :-(

Sorry for the delay, been wrapped up in a new project.  I actually like the idea a lot.
I'll drop a new version now.


Photo under 'To manually onboard one or more machines ' is an old one, need to update as per how it's showing in the Azure portal.

Photo under 'To manually onboard one or more machines ' is an old one, need to update as per how it's showing in the Azure portal.
[Enter feedback here]

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

ID: e2598a3e-7cd9-70ce-dc56-4ce2ff539e32
Version Independent ID: 55f29cff-a71d-5d68-e6a7-2a0922549c07
Content: Use Microsoft Defender for Endpoint's threat and vulnerability management capabilities with Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/deploy-vulnerability-assessment-tvm.md
Service: defender-for-cloud
GitHub Login: @ElazarK
Microsoft Alias: v-ekrieg

@sakaldeepyadav I merged a fix for this issue. You can see the changes in the live docs.
Thanks for pointing out the problem!

#please-close


Prepare for Hacker News release 1.0.2

#237  👈 (View in Graphite)
main

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


Optimize first() and last()

This change makes these methods almost 2x faster, by reducing the number of tree traversals from two to one.

Thanks for the suggestion. I'm going to stick with this recursive
implementation for consistency with most of the rest of the code base, but
if you have any benchmarks on the overhead of the function calls, I'd be
very interested and open to changing if there's meaningful overhead
Sent from my phone
On Mon, Sep 30, 2024, 12:25 AM Adam Reichold @.***>
wrote:

@.**** commented on this pull request.
In src/tree_store/btree.rs
https://github.com/cberner/redb/pull/871#discussion_r1780568663:

   &self,

   page: PageImpl,

) -> Result<Option<(AccessGuard<'static, K>, AccessGuard<'static, V>)>> {

   let node_mem = page.memory();

   match node_mem[0] {

       LEAF => {

           let accessor = LeafAccessor::new(page.memory(), K::fixed_width(), V::fixed_width());

           let (key_range, value_range) = accessor.entry_ranges(0).unwrap();

           let key_guard = AccessGuard::with_page(page.clone(), key_range);

           let value_guard = AccessGuard::with_page(page, value_range);

           Ok(Some((key_guard, value_guard)))

       }

       BRANCH => {

           let accessor = BranchAccessor::new(&page, K::fixed_width());

           let child_page = accessor.child_page(0).unwrap();

           self.first_helper(self.mem.get_page_extended(child_page, self.hint)?)

I understand tree depth is somewhat limited, but this looks highly
amenable to an iterative implementation by basically putting all of this in
a loop and writing
page = self.mem.get_page_extended(child_page, self.hint)?;
here with a
return Ok(Some((key_guard, value_guard)));
above to avoid the any questions of call overhead and/or stack usage.
—
Reply to this email directly, view it on GitHub
https://github.com/cberner/redb/pull/871#pullrequestreview-2336610455,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGNXQG7WZSACU6NKGQD2FDZZD4GVAVCNFSM6AAAAABPCKJOAGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGMZWGYYTANBVGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


No license(s) specified

Some of the code in this repository appears not to be available under any license. Please could it be licensed under a GPL-Compatible Free Software license? I would suggest AGPLv3, so that people accessing forks/copies of the PeARS website over a network will automatically be entitled to the Four Freedoms in respect of any modifications that may have been made to those forks/copies.
Please could a content license also be specified? Ideally, please dual-license website content under CC BY-SA 3.0 and GFDL, for compatibility/interoperability with the many projects using one or other (or both) of those licenses, such as Wikipedia.
Thanks!

TODO  soon

@PeARSearch/all-pears could we possibly sort the license of the website, as requested by @sampablokuper? This issue has been lying around for a while...
The suggestions above sound good to me. But if anybody has other ideas, please share!

@minimalparts @nandajavarma , Let's go with AGPLv3.

Sounds good to me! Thanks for looking after this!

Done in 6857b73


customizations: add publicationStmt to customizations

This adds publisher and licence information into the customization ODDs.

@rettinghaus the source files are licensed under ecl 2.0 and here we have v1.0. Do we want to update version number here as well?

@musicEnfanthen Good thing you noticed, because there was an ambiguity in all files.

@bwbohl @rettinghaus shoot, having a second look, I see that the v1 reference was targetting the "derivation statement", i.e., the earlier versions that indeed were released under v1 of the ECL:
This is a derivative work based on earlier versions of the schema © 2001-2006 Perry Roland
and the Rector and Visitors of the University of Virginia; licensed under the Educational
Community License version 1.0.

So the statement was technically correct? (Sorry for the confusion)

I guess you're right again @musicEnfanthen. Now everything should be fine.

Thank you!


fix: isAIAction uses the wrong interface

Description
Fix type for isAIAction.
Fixes #33170
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[X] No

/build-deploy-preview skip-tests=true


Stale files in published packages?

It appears that some old files (from 5.x?) are being published in 6.1.3, see<EMAIL_ADDRESS>I don't see this file created if I build locally, and it references dependencies that are no longer used such as xmlbuilder:
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
/* eslint-disable camelcase, semi */
/*!
 * Sitemap
 * Copyright(c) 2011 Eugene Kalinin
 * MIT Licensed
 */
const xmlbuilder_1 = require("xmlbuilder");
const sitemap_item_1 = require("./sitemap-item");
const types_1 = require("./types");
const zlib_1 = require("zlib");
const url_1 = require("url");
const fs_1 = require("fs");
const utils_1 = require("./utils");
const sitemap_stream_1 = require("./sitemap-stream");
function boolToYESNO(bool) {
    if (bool === undefined) {
        return bool;
    }
    if (typeof bool === 'boolean') {
        return bool ? types_1.EnumYesNo.yes : types_1.EnumYesNo.no;
    }
    return bool;
}

weird. I'll take a look after I get done with my day job.

👍 I was upgrading some code and ran into this. If I remove the references to the legacy modules everything seems to work fine, possibly just need to add a git clean -xfd type of action to the publishing script?


Research bar

I doesn't see a research bar on the website.
I understand that a lot of people directly go on youtube to see your videos, but it could be usefull to add a research bar to the website. It would help people that want to see a specific tutorial video for instance

A search bar would be a nice idea. However, having Jekyll as the backend, it's not as straight forward to implement. Maybe this could be something for the "new" version?

@nilsweb Could you transfer the issues regarding to the new website to the new repo?

For some reason, I don't get the "Transfer this issue" button. Only in the new repo. @shiffman Do you have it?


Not showing product image properly in the order listing page in the admin panel.

Terms

[X] Before you openning this issue, i have checked if the issue has already been reported.

Bagisto Version(s) affected
2.0.0
Issue Description
In the Admin panel, Not showing proper product images if there are more than 3 products in a single order and the filter container should be opened.
Preconditions

Admin should be logged in.
Filter container should be opened.

Steps to reproduce

Go to 'Admin panel'
Click on 'sales '
Click on the orders
Click on the filter option
See the error

Expected Result
The images should be shown.
Actual Result
The image is not showing properly.Here
Screenshots
No response
Additional context
No response

This Filter option is moved in slide bar. Now issue is not occurring.
You can check Here


Pulling release into main to unblock main merging into release

Unblocks https://github.com/microsoft/FeatureManagement-Dotnet/pull/514

We shouldnt need to merge release to main.

 But it seems fine now? Closing this.


✨ [Feature request]: Add more Play Ideas

Is your feature request related to a problem? Please describe.
Right now, we have 24 Play Ideas. The ideas are good but there are not enough of them. We could use more ideas.
Describe the solution you'd like.
We should add more ideas. These play ideas should be more creative and unique. The ideas should help them develop their play or start a new one.
Describe alternatives you've considered.
We should add ideas that are creative and different, not just simple and common ideas people usually find online. This will help folks think about how they can make a play idea into a reality using their favorite Techstack. The ideas can inspire them to build something new.
Screenshot / Screenshare
No response
Additional context
No response
Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue

Code of Conduct

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

Do you have any play ideas in your mind? How do you plan to work on this, if it is assigned to you ?

We already have a play idea JSON. I am thinking of adding more ideas over there. As currently, we have only 24 ideas so, we can add more to it. The ideas we can discuss them with community members if any play ideas they want to add up we can add those too.

First we need to check how many of those 24 ideas have been implemented by contributors.
Then mark the ones that are implemented as built and link the play to it.
If there are no significant implementation, we should first encourage implementing the existing ideas.
Your idea is nice, but I believe this is manual work. What if we opened a form like testimonials, and gave its editorial access to @atapas and @priyankarpal? Maybe you can take this up as well.
let me know what you think

I agree with you @joshi-kaushal  That would be a better approach.
Also, in the future, we can make the system even more dynamic. The ideas that have already been implemented can automatically be linked to the relevant code. For ideas that have not been implemented yet, we can encourage people to build them out. This will help us avoid duplicating work and ensure all good ideas are eventually turned into reality.

The ideas that have already been implemented can automatically be linked to the relevant code.

Can you update me on the progress of this particular issue?

@priyankarpal I think, this issue needs a proper discussion as @joshi-kaushal mentioned here
Also, what's your thought on this @priyankarpal


Missing break statements after VALUE_FALSE in deserialize method

It looks like there is a missing 'break' after VALUE_FALSE.
Without it, the boolean value always tries to parse as a number, which of course will never succeed.
case VALUE_FALSE:
case VALUE_TRUE:
   value = new BooleanValue(p.getBooleanValue());
case VALUE_NUMBER_FLOAT:
   value = new FloatValue(p.getDecimalValue());
   break;
case VALUE_NUMBER_INT:
   value = new IntValue(p.getBigIntegerValue());
   break;
case VALUE_STRING:
   value = new StringValue(p.getText());
   break;
case VALUE_NULL:
   value = null;
   break;
default:
   throw new JsonParseException(p, "Non managed JSON token: " + p.currentToken());
			}

My suggestion:
case VALUE_TRUE:
   value = new BooleanValue(p.getBooleanValue());
   break;

I wanted to raise a PR for this but looks like I am not able to do so.

Please make sure you have the correct access rights and the repository exists.

Hello,
Thanks for the hint.
I think everybody may submit PR. To do this:

clone the project in GitHub, into your repositories.
do the change.
submit the PR

Étienne

And an additional note: I'd be happy to validate this PR.
What would be even greater, is if you add Junit test that would be ko before the correction, and become ok after it.

Question : do you plan to do this PR ?
Otherwise I commit the correction you pointed out.

Hey @etienne-sf unfortunately I have no access to raise a PR. Sorry for that : /

Ok, no problem
I'll commit this correction.
:)

Solved in the 2.3.1 release.
Along with a bug that would prevent to use alias on field which type is a custom scalar.


[Bug] Update the package to support Dart 3

Hello @iamriajul , this package is outdated. can you please update it to be compatible with Dart 3 and null safety

PRs are welcomed.

You can use the Prerelease as of now: adhan 2.0.0-nullsafety.2 | Dart Package (pub.dev)
I'm trying to make it a stable release, but because of time shortage, I couldn't give much time previously.
Soon I'll try to release a stable version with null safety support. InShaaAllah.

Dart 3 support released in stable channel.


Add a reference to existing event in page 10810 "Generate EFT Files"

Hello,
Could you please add a reference to the existing publisher OnAfterOpenPage in OnOpenPage trigger but before UpdateSubForm procedure:

There is already a similar code in a field BankAccountNo:

Accidentally created 2 issues.


How to Install crud admin generator without SSH

I was able to install crud admin generator in my local server (WAMP) but because SSH is not available on my shared hosting I'm unable to implement the same thing on my server (online). Also tried cPanel and ftp uploads of the locally installed files, that did not work either.
Please how can I get  crud admin generator to my server?
Thanks.

I have the same problem no SSH on my hosting how to install it.


✗ sync path configuration ("./clusters/staging") would overwrite path ("./clusters/my-cluster") of existing Kustomization

The following error occurs during the bootstrap: Any hints on this ?
$ flux bootstrap github --owner=${GITHUB_USER} --repository=${GITHUB_REPO} --branch=master --path=clusters/staging --personal
► connecting to github.com
✔ repository "https://github.com/xxxxxxx/flux2-kustomize-helm-example" created
► cloning branch "master" from Git repository "https://github.com/xxxxxxx/flux2-kustomize-helm-example.git"
✔ cloned repository
► generating component manifests
✔ generated component manifests
✔ committed sync manifests to "master" ("60adc00a8e500b024dc6059cbcb605297e10aa5c")
► pushing component manifests to "https://github.com/xxxxxx/flux2-kustomize-helm-example.git"
✔ reconciled components
► determining if source secret "flux-system/flux-system" exists
✔ source secret up to date
✗ sync path configuration ("./clusters/staging") would overwrite path ("./clusters/my-cluster") of existing Kustomization

You can’t change the path of an existing install, so either uninstall flux or use the same path as before to upgrade.

I am on a windows machine, and had unzipped this release flux_0.12.3_windows_386.zip and added to the path.
Could you please let me know what you meant by Uninstalling ? because removal of this exe would not recognize flux
or what is the upgrade you have mentioned above ?

You have Flux running on your cluster already, the error message tells you that you can’t change it to a new path.

@stefanprodan  thanks for pointing it out. Missed it. Works fine now.!

also had this issue, coming from a previous tutorial. might be worthwhile to include something like "if flux is already installed or coming from the main tutorial (which links here), please `flux uninstall"


test: Add integration testcase for testing ReferenceConfig and RegistryProtocol

What is the purpose of the change
see #8301
Brief changelog
Add integration testcase for testing ReferenceConfig and RegistryProtocol
Verifying this change

Checklist

[x] Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
[x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Add some description to dubbo-website project if you are requesting to add a feature.
[x] GitHub Actions works fine on your own branch.
[] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #8302 (ecbf47f) into 3.0 (d46f331) will increase coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                3.0    #8302   +/-   ##
=========================================
  Coverage     64.02%   64.03%
  Complexity      311      311
=========================================
  Files          1077     1077
  Lines         45525    45525
  Branches       6839     6839
=========================================
+ Hits          29147    29151    +4
+ Misses        13149    13137   -12
- Partials       3229     3237    +8

Impacted Files
Coverage Δ

.../remoting/transport/netty4/NettyServerHandler.java
61.36% <0.00%> (-9.10%)
:arrow_down:

...ubbo/rpc/protocol/dubbo/ChannelWrappedInvoker.java
43.47% <0.00%> (-4.35%)
:arrow_down:

...keeper/ZookeeperServiceDiscoveryChangeWatcher.java
88.88% <0.00%> (-3.71%)
:arrow_down:

...he/dubbo/remoting/transport/netty/NettyServer.java
70.17% <0.00%> (-3.51%)
:arrow_down:

...pache/dubbo/registry/support/AbstractRegistry.java
76.64% <0.00%> (-2.92%)
:arrow_down:

...org/apache/dubbo/rpc/protocol/AbstractInvoker.java
65.76% <0.00%> (-2.71%)
:arrow_down:

...java/org/apache/dubbo/remoting/api/Connection.java
76.59% <0.00%> (-2.13%)
:arrow_down:

...a/org/apache/dubbo/monitor/dubbo/DubboMonitor.java
87.61% <0.00%> (-0.96%)
:arrow_down:

...ava/org/apache/dubbo/common/utils/ConfigUtils.java
69.51% <0.00%> (-0.61%)
:arrow_down:

...n/java/org/apache/dubbo/common/utils/NetUtils.java
67.34% <0.00%> (-0.35%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


refactor(v2): exit with non zero exit code when there are warnings in build

Motivation
Crash the build whenever warnings are found and CI env is set to be true. This is after a comment mentioned in this issue #2448 . The implementation has been carried out in Create React App to make local builds faster. They also cause run eslint to tun with builds which we can probably do in another PR.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan

Remove hints: false, from packages/docusaurus/src/webpack/base.ts to force a warning about assets exceeding 250kb
In the root of docusaurus run yarn build and you will see that the build will run as normal without exiting
Run again but this time with Ci env set to true CI=true yarn build and the build will cause an error and exit

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

IMO my original use case should have been an error instead of a warning. I'm not sure how much control we have over that. It's effectively a reference error.
I do think treating warnings as errors may make sense. It has worked well for us in Create React App.

@yangshun apologies for the delay in getting back to you on this. I feel like we don't really have control over this specific reference error as it is a console.warn produced by MDX as part of the makeShortCode functionality here
I can't really see as part of the stats option in Webpack. So I'm not entirely sure how we can treat it as an error which can then enable us to subsequently exit the build.
What are your thoughts on this?

Yeah if they're only using console.warn i'm not sure how much we can do. It's unfortunate there isn't a more robust logging system that the docusaurus mdx loader could tap into to emit proper webpack stats.

It seems to me that this is quite easily solved when warnings is output to the console:
https://github.com/facebook/docusaurus/blob/3ad45508547aa9f5aeb0cced801f2615d0f29bd1/packages/docusaurus/src/commands/build.ts#L49-L51
We can catch such warnings (eg. via includes of String) and stop the building process with reject(err), right?

@lex111 This is what my thought process was but when that specific reference error occurs, we never really fall into the condition which checks for warnings in the first place. This is because if you check the docs here https://mdxjs.com/advanced/components under makeShortcode a stubbed component is returned... "It’s used in order to stub any components that aren’t directly imported so that there won’t be any ReferenceErrors.".
I am aware that MDX community is looking into only adding this function that returns a stubbed component optional. Because if it is not needed then we just simply won't use it if it is not required which will exit the build.


Blueprint name collision on module install

I have started a new module using cookie cutter, everything goes well until I restart the server. At this point I get:
AssertionError: A blueprint's name collision occurred between <flask.blueprints.Blueprint object at 0x7f37e6ca8610> and <quokka.core.app.QuokkaModule object at 0x7f37eb1b8e10>.  Both share the same name "quokka_events".  Blueprints that are created on the fly need unique names.
The same thing happens when I try install the shopping cart module.
Any help will be appreciated.

@pixiemars how did the fresh install go?

Verified installed all modules, no error found.


Windows run

How to run this or compile on windows?

You need to import the existing sources as a project into IntelliJ Idea. Other IDEs should work too.
I've compiled a standalone JAR file, you can download it here: https://timschneeberger.me/dump/SamsungServiceModeOTP.jar
To run it, open a new command line window in the same directory as the JAR and run it like this:
java -jar SamsungServiceModeOTP.jar MyKey123456789

Decrypted one-time password:<PHONE_NUMBER>
=> Key verified


add minichatbot to the website.

assign me , I like to work on this . @aditya-bhaumik

this issue has been solved, so we are closing this issue.


Problems getting number of connected clients

I've got code where I'm attempting to keep track of the number of clients connected using a prometheus Gauge.
metrics.ts
  export function clientConnected(projectId: string, ) {
    prom_currentConnections.inc({ ...baseLabelValues, projectId })
  }

  export function clientDisconnected(projectId: string, ) {
    prom_currentConnections.dec({ ...baseLabelValues, projectId })
  }

main.ts
  // projectid is something added to the client during authentication

  aedesInstance.on('client', (client) => {
    metrics.clientConnected(client.projectId);
  })

  aedesInstance.on('clientDisconnect', (client) => {
    metrics.clientDisconnected(client.projectId);
  })

the metrics.clientConnected and metrics.clientDisconnected basically just increment and decrement counters. There is not really any logic here.
If there are socket errors, it seems like the decrement is not always called. After heavy load testing, where all of clients connecting have been shutdown (not always gracefully) we find that this metric sometimes displays that there are clients connected, even when there isn't.

Thanks for reporting, would you like to send a PR with a fix?

Sure!
I’m still trying to diagnose right now. I need a way of getting it to reproduce without having to make thousands of connections.
I’ll comment with anything else I find.

I've been unable to find out what causes it, but I have found that Aedes internally doesn't realize the clients are still connected. I'm not sure if it's because of the long delays in authenticating a client, or if it somehow fails during authentication, or what. But the code below shows that each worker has more connections reported by Aedes than by the TCP Server and WS Server.
import aedes from 'aedes';
import net from 'net';
import http from 'http';
import wsStream from 'websocket-stream';
import { aedes_published, aedes_authorize_subscribe, aedes_authorize_publish, aedes_authenticate, AedesExtendedClient } from './broker';

export function startWorker(workerid?: string) {

  const aedesInstance: aedes.Aedes = aedes({
    authenticate: aedes_authenticate,
    authorizePublish: aedes_authorize_publish,
    authorizeSubscribe: aedes_authorize_subscribe,
    published: aedes_published,
    concurrency: 20000,
  });

  setInterval(async () => {
    const tcpConnProm = new Promise<number>((res, rej) => { tcpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    const wsConnProm = new Promise<number>((res, rej) => { httpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    console.log(workerid, aedesInstance['connectedClients'], await tcpConnProm, await wsConnProm)
  }, 5000);

  const tcpServer = net.createServer(aedesInstance.handle)
  const httpServer = http.createServer();
  const websocketServer = wsStream.createServer({ server: httpServer, path: '/mqtt' }, aedesInstance.handle as any);
  var tcpPort = 1883;
  var wsPort = 8883;

  tcpServer.listen(tcpPort, '<IP_ADDRESS>', function () {
    console.log(workerid, 'TCP server listening on port', tcpPort)
  })
  httpServer.listen(wsPort, '<IP_ADDRESS>', () => {
    console.log(workerid, 'WebSocket server listening on port', wsPort)
  });

}

5/13/2019 11:33:04 AM thread-1 19 0 0
5/13/2019 11:33:04 AM thread-2 18 0 0
5/13/2019 11:33:04 AM thread-3 21 0 0
5/13/2019 11:33:04 AM thread-4 20 0 0
5/13/2019 11:33:04 AM thread-5 18 0 0
5/13/2019 11:33:04 AM thread-6 23 0 0
5/13/2019 11:33:04 AM thread-7 17 0 0
5/13/2019 11:33:05 AM thread-8 23 0 0

@JohnCMcDonough  Could you check if either one of clientError, connectionError or keepaliveTimeout  events are being fired ?

I get clientErrors when they disconnect, but it's just ECONNRESET.
//...
  let clientErrorCount = 0
  let connectionErrorCount = 0
  let keepaliveTimeoutCount = 0

  aedesInstance.on('clientError', (c: AedesExtendedClient, e) => {
    clientErrorCount++
    console.log('clientError', e)
  })
  aedesInstance.on('connectionError', (c: AedesExtendedClient, e) => {
    connectionErrorCount++;
    console.log('connectionError', e)
  })

  aedesInstance.on('keepaliveTimeout', (c: AedesExtendedClient) => {
    keepaliveTimeoutCount++;
    console.log('keepaliveTimeout', c.id)
  })

  setInterval(async () => {
    const tcpConnProm = new Promise<number>((res, rej) => { tcpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    const wsConnProm = new Promise<number>((res, rej) => { httpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    console.log(workerid, aedesInstance['connectedClients'], await tcpConnProm, await wsConnProm, clientErrorCount, connectionErrorCount, keepaliveTimeoutCount)
    metrics.setConnectedClients((await tcpConnProm) + (await wsConnProm));
  }, 5000);
//...

thread-1 29 11 0 77 0 0
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM clientError { Error: read ECONNRESET
5/13/2019 12:41:50 PM at TCP.onStreamRead (internal/stream_base_commons.js:111:27) errno: 'ECONNRESET', code: 'ECONNRESET', syscall: 'read' }
5/13/2019 12:41:50 PM thread-5 20 0 0 75 0 0
5/13/2019 12:41:50 PM thread-4 20 0 0 104 0 0
5/13/2019 12:41:50 PM thread-3 22 0 0 51 0 0
5/13/2019 12:41:50 PM thread-6 22 0 0 69 0 0
5/13/2019 12:41:50 PM thread-8 23 0 0 54 0 0
5/13/2019 12:41:50 PM thread-7 19 0 0 77 0 0
5/13/2019 12:41:55 PM thread-2 19 0 0 87 0 0

The code below appears to reliably create the errors for me. I've removed as much domain specific code as I can.
import aedes from 'aedes';
import net from 'net';
import http from 'http';
import wsStream from 'websocket-stream';

function sleep(ms: number) {
  return new Promise(res => setTimeout(res, ms));
}

export function startWorker(workerid?: string) {

  const aedesInstance: aedes.Aedes = aedes({
    // authenticate: aedes_authenticate,
    authenticate: async (client: AedesExtendedClient, username, password, done) => {
      // simulate our network
      await sleep(60 * 1000 * Math.random());
      // simulate an auth failure
      if (Math.random() > 0.9) {
        let aedesError: aedes.AuthenticateError = new Error('A random auth failure occurred') as any;
        aedesError.returnCode = 4; // AuthErrorCode.BAD_USERNAME_OR_PASSWORD
        done(aedesError, false);
      } else {
        done(null, true);
      }
    },
    // authorizePublish: aedes_authorize_publish,
    authorizePublish: async (client, pcket, done) => {
      await sleep(500); // simulate latency writing to persistent store.
      done();
    },
    // authorizeSubscribe: aedes_authorize_subscribe,
    // published: aedes_published,
    concurrency: 20000,
  });

  let clientErrorCount = 0
  let clientsClosed = 0;
  let connectionErrorCount = 0
  let keepaliveTimeoutCount = 0

  aedesInstance.on('clientError', (c: AedesExtendedClient, e) => {
    clientErrorCount++
    console.log('clientError', e)
    c.close(() => {
      console.log('client closed successfully');
      clientsClosed++;
    })
  })
  aedesInstance.on('connectionError', (c: AedesExtendedClient, e) => {
    connectionErrorCount++;
    console.log('connectionError', e)
  })

  aedesInstance.on('keepaliveTimeout', (c: AedesExtendedClient) => {
    keepaliveTimeoutCount++;
    console.log('keepaliveTimeout', c.id)
  })

  setInterval(async () => {
    const tcpConnProm = new Promise<number>((res, rej) => { tcpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    const wsConnProm = new Promise<number>((res, rej) => { httpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    console.log(workerid, JSON.stringify({ brokerClients: aedesInstance['connectedClients'], tcpConn: await tcpConnProm, wsConn: await wsConnProm, clientErrorCount, clientsClosed, connectionErrorCount, keepaliveTimeoutCount }))
  }, 5000);

  const tcpServer = net.createServer(aedesInstance.handle)
  const httpServer = http.createServer();
  const websocketServer = wsStream.createServer({ server: httpServer, path: '/mqtt' }, aedesInstance.handle as any);
  var tcpPort = 1883;
  var wsPort = 8883;

  tcpServer.listen(tcpPort, '<IP_ADDRESS>', function () {
    console.log(workerid, 'TCP server listening on port', tcpPort)
  })
  httpServer.listen(wsPort, '<IP_ADDRESS>', () => {
    console.log(workerid, 'WebSocket server listening on port', wsPort)
  });

}

It's for sure some kind of race condition. If I cancel my HTTP requests to authenticate after 10 seconds, and just reject and let the device try again, I don't see any of these issues.

Does it relate to https://github.com/mcollina/aedes/pull/243 ?

@JohnCMcDonough Thanks for the report and a test. It is reproducible.
To adapt the recent change of type definition. I modified your test for another developers to have a test.
import * as aedes from 'aedes';
import * as net from 'net';
import * as http from 'http';
import * as wsStream from 'websocket-stream';

function sleep(ms: number) {
  return new Promise(res => setTimeout(res, ms));
}

export function startWorker(workerid?: string) {

  const aedesInstance: aedes.Aedes = aedes({
    // authenticate: aedes_authenticate,
    authenticate: async (client: aedes.Client, username, password, done) => {
      // simulate our network
      await sleep(60 * 1000 * Math.random());
      // simulate an auth failure
      if (Math.random() > 0.9) {
        let aedesError: aedes.AuthenticateError = new Error('A random auth failure occurred') as any;
        aedesError.returnCode = 4; // AuthErrorCode.BAD_USERNAME_OR_PASSWORD
        done(aedesError, false);
      } else {
        done(null, true);
      }
    },
    // authorizePublish: aedes_authorize_publish,
    authorizePublish: async (client, pcket, done) => {
      await sleep(500); // simulate latency writing to persistent store.
      done();
    },
    // authorizeSubscribe: aedes_authorize_subscribe,
    // published: aedes_published,
    concurrency: 20000,
  });

  let clientErrorCount = 0
  let clientsClosed = 0;
  let connectionErrorCount = 0
  let keepaliveTimeoutCount = 0

  aedesInstance.on('clientError', (c: aedes.Client, e) => {
    clientErrorCount++
    console.log('clientError', e)
    c.close(() => {
      console.log('client closed successfully');
      clientsClosed++;
    })
  })
  aedesInstance.on('connectionError', (c: aedes.Client, e) => {
    connectionErrorCount++;
    console.log('connectionError', e)
  })

  aedesInstance.on('keepaliveTimeout', (c: aedes.Client) => {
    keepaliveTimeoutCount++;
    console.log('keepaliveTimeout', c.id)
  })

  setInterval(async () => {
    const tcpConnProm = new Promise<number>((res, rej) => { tcpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    const wsConnProm = new Promise<number>((res, rej) => { httpServer.getConnections((err, count) => { err ? rej(err) : res(count) }); })
    console.log(workerid, JSON.stringify({ brokerClients: aedesInstance['connectedClients'], tcpConn: await tcpConnProm, wsConn: await wsConnProm, clientErrorCount, clientsClosed, connectionErrorCount, keepaliveTimeoutCount }))
  }, 5000);

  const tcpServer = net.createServer(aedesInstance.handle)
  const httpServer = http.createServer();
  const websocketServer = wsStream.createServer({ server: httpServer, path: '/mqtt' }, aedesInstance.handle as any);
  var tcpPort = 1883;
  var wsPort = 8883;

  tcpServer.listen(tcpPort, '<IP_ADDRESS>', function () {
    console.log(workerid, 'TCP server listening on port', tcpPort)
  })
  httpServer.listen(wsPort, '<IP_ADDRESS>', () => {
    console.log(workerid, 'WebSocket server listening on port', wsPort)
  });

}

startWorker("test")

Fixed in https://github.com/mcollina/aedes/pull/283


[Reply] Search page

This change implements Reply's search page.

Implement search page layout
Transition between home route and search route using shared z axis transition
Use named routes to navigate
Introduce rootNavKey to be able to call on the root navigator from any screen.
Introduce search icon button for desktop/tablet layouts

Desktop
Mobile

It looks like there's an unintended scaling animation for the search icon in the mobile layout when returning to the inbox


[Feature Request] Background playback

Please add background playback so the audio can continue playing in background after locking the screen.
Bonus: Add toggle option in Settings.

Done. https://github.com/OdyseeTeam/odysee-android/pull/124


Integration of anything similar like puppeteer-extra-plugin-stealth

Hello,
Our use case basically needs a OAuth Login like Chrome or facebook for a complete E2E testing.
We are using playwright and running it on lambda. The Normal Login works fine but the OAuth fails due to the headless mode. I found out the package puppeteer-extra-plugin-stealth which is used to bypass bot protection for OAuth.
Is there any way we can use the same plugin in playwright as its a fork from puppeteer?

Hey @sanudatta11. Awesome idea! playwright-aws-lambda is not trying to do anything more than just provide the tools necessary to run Playwright in the AWS Lambda environment. I think that additional tools could be leveraged with playwright-aws-lambda to accomplish what you're asking. It looks like puppeteer-extra-plugin-stealth is a plugin for puppeteer-extra. I'd love to see the community create a similar package for Playwright (e.g. playwright-extra). See a conversation here: https://github.com/berstend/puppeteer-extra/issues/144

Going to close this out as we do not intend to build this functionality into playwright-aws-lambda at this time. Thanks!

Hey @austinkelleher  - any idea on how to use this with playwright-extra?
https://github.com/berstend/puppeteer-extra/tree/master/packages/playwright-extra


change data to be an union, so that it can support uint64 data in 32-bit OS

change data to be an union, so that it can support uint64 data in 32-bit OS

The data member is a void* meaning you can put anything you like there, including your union.


Error

In ", no value was found for dictionary key 'choices'

Same error

Try changing the model from gpt-4 to gpt-3.5-turbo. It is possible your account doesn't have API access to GPT4 (yet).

It doesn’t work  Il giorno 1 apr 2023, alle ore 18:43, Revisor @.***> ha scritto:
Try changing the model from gpt-4 to gpt-3.5-turbo. It is possible your account doesn't have API access to GPT4 (yet).
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Yeah same error... i tried with a different account and a new API - and still its giving me that error... but it was working yesterday totally fine !

In my case, I forgot to check my balance in OpenAI account. If you didn't add payment method, Would you give it a try?

Yeah I can try
On Mon, Apr 3, 2023, 1:05 AM Jiwon Baek @.***> wrote:

In my case, I forgot to check my balance in OpenAI account. If you didn't
add payment method, Would you give it a try?
—
Reply to this email directly, view it on GitHub
https://github.com/Yue-Yang/ChatGPT-Siri/issues/98#issuecomment-1493667234,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZXSZHRJG6MLBZNZMXASWTTW7JLBLANCNFSM6AAAAAAWPITT7Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

In my side , it is the above error.


Fix BUILD: include ipp files

.ipp files will need to be included, or Bazel will have no knowledge of those files.

thank you


Display package version instead of assembly version on error page

The error page we have embedded shows the assembly version of hosting. But AFAIK that's the only place we display that information. If I depend on preview1-final today and then look a the error page it shows me a build number. Which immediately confused me and made me think I had made a mistake about depending on a pre-release somewhere.
Can we embed the -final version and use that here instead or as well as the build number?

@muratg

Did you save an example output when you hit this?
I wonder if we could add the package version on top or something. I suspect version info comes from the assembly itself through reflection for that error page.

We should still be able to get that version out of the assembly via reflection.


Parser becomes sad, dies when remote reference is wrong type

It's user error, but the parser should be a bit more lenient.  If you have a BodyParameter and that has a schema reference which is invalid--either not reachable, not parseable, or is of the wrong type--the parser throws a fit and walks away without any warning.  While we shouldn't go too far out of the way in this case, we should at least not quit, and possibly send a nice message that there's an issue.

Fixed by #412


Fix inconsistency in plugin name

Fix inconsistency between Plugin name and Plugin class name. For example: SimplePolicy is using SimplePolicyPlugin as class name, but using SimplePolicy as plugin name. This issue also could be seen on RpcSystemAssetTracker. I think it's also necessary to unify plugin class name on neo3 to avoid this issue.

But the name of the class is used?

Hi, Shargon. What do you mean?

For reproduce the error, what are the steps?
install plugin RpcSystemAssetTracker uninstall plugin RpcSystemAssetTracker
?

For reproduce the error, what are the steps?
install plugin RpcSystemAssetTracker uninstall plugin RpcSystemAssetTracker
?

Now only SimplePolicy and RpcNep5Tracker have this issue.
For example  install SimplePolicy, uninstall SimplePolicy.

Check my last changes, it works for me.

mmmm... i see two solutions, as you said.

1 Remove plugin.Name, and use the library name for the plugin

This avoid create two plugins in the same library

2 Use a file like plugins.json for store what plugins are installed or not.

This help when we need to remove hot-plugins (currently used)

mmmm... i see two solutions, as you said.

1 Remove plugin.Name, and use the library name for the plugin

This avoid create two plugins in the same library

2 Use a file like plugins.json for store what plugins are installed.

This help when we need to remove hot-plugins (currently used)

I think solution 1 makes sense for making plugins more regular.

@superboyiii, how is this PR? Should we merge this?

1 is good for me

If we want to remove the plugin name, this should be done in neo first

@superboyiii Can you test it again?

Sure

Here's my test steps and result.

install Plugins

Plugins are loaded successfully

Uninstall plugins

Plugins are deleted successfully.

Rename one of the plugin class name, make it different as type name.

build it and install it

restart neo-cli and uninstall it.

Plugin is deleted successfully. Test Pass.

By the way, Neo v3.0.0-CI00815 isn't compatible as a dependency in neo-plugins, the code of plugins should be adjusted.

And if neo-cli is using dependency of Neo v3.0.0-CI00815, RpcNep5Tracker and SystemLog will break.

Only these are OK.

Summary: Test Pass.
Warning: RpcNep5Tracker and SystemLog need adjust if apply the latest neo on neo-cli or neo-plugins.


Some suggestions, this could be improved still.

Hey, this is a pull request INTO your pull request.
There still might be some good work which could be done here.
It also occurred to me that if you were to put a "read counter" in:
https://github.com/arran4/golang-ical/blob/84e95bcb9f6760d1b288e655977a3fc5e2ae6fa9/calendar.go#L523-L533
https://github.com/ManoloTonto1/golang-ical/blob/84e95bcb9f6760d1b288e655977a3fc5e2ae6fa9/calendar.go#L523-L533
And put it in the function here;
https://github.com/arran4/golang-ical/blob/84e95bcb9f6760d1b288e655977a3fc5e2ae6fa9/calendar.go#L535-L590
https://github.com/ManoloTonto1/golang-ical/blob/84e95bcb9f6760d1b288e655977a3fc5e2ae6fa9/calendar.go#L535-L590
You could a line offset and with some smart refactoring a character offset inserted in the errors raised in:
https://github.com/arran4/golang-ical/blob/84e95bcb9f6760d1b288e655977a3fc5e2ae6fa9/calendar.go#L438-L521
https://github.com/ManoloTonto1/golang-ical/blob/84e95bcb9f6760d1b288e655977a3fc5e2ae6fa9/calendar.go#L438-L521
A bit like any other parser.
Anyway. Please review this, then make some improvements if you can find any and then we can merge upstream into master once done.

@ManoloTonto1 This is my "reverse" pull request, a PR into your PR to fix some changes. I haven't reviewed if they are still relevant just fixed the conflicts so you can. This PR goes into https://github.com/arran4/golang-ical/pull/73 which has stagnated.
I have replaced a couple of PRs with my own which tries to resolve issues with them and I will wait a short while before merging them myself (feel free to review them if you like.) I can take over yours ( https://github.com/arran4/golang-ical/pull/73 ) too and replace it with my own (I will be keeping your commits so in essence I will be duplicating this pr https://github.com/ManoloTonto1/golang-ical/pull/1 into mine. )

Actually rebased it with master too. This should improve things. You will have to enable actions on your fork to see if the tests works before accepting the merge into your pull request sorry these things tend to be a bit confusing. I wish github supported "suggest a change" like gitlab has

@ManoloTonto1 Fixed the failing test b/c of not picking up on the error wrapping of EOF. There are potentially some other of these issues around too.

Did a quick spot check. But there could be more issues here too. I'm not 100% on the format strings, but they will work.

@arran4 shall we merge it?

THis is a PR into your PR, so it's up to you. I suggest yes. But I can go around you and just merge it my branch into the "origin" repo.
I recommend that you merge it into yours for process sake. So feel free to request changes into your pr. :P

But thanks. Happy to wait for you.

@arran4 Merged 🚀

Alright, looks like some new conflicts have occurred. I will see where this leaves us.


:bug: Fix typo in workspace api

Summary
Fix typo.
Related issue(s)
Release Notes

NONE

/lgtm
/approve


Try catch issue in jvm code gen

Description:
Below code would not run the "getIntMethod"
import ballerina/io;

public function main() {
    int | error res = 100;
    res = trap getIntMethod();
    io:println("Result from pointer - ", res);
}

public function getIntMethod() returns int {
    io:println("--- invoking getInt");
    return 9;
}

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

subtask - #20175


nixos/hardware/intel: add opencl option

Description of changes
Part of https://github.com/NixOS/nixos-hardware/pull/573

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

OpenCL on intel is messy, I believe this is the support table as it currently exists:

pkg
CPU
GPU
Notes

intel-compute-runtime
no
yes
since Broadwell 5th gen, open source

intel-ocl
yes
no[^1]
since Ivy Bridge 3rd gen, closed source, deprecated

beignet
no
yes
since Ivy Bridge 3rd gen, open source, deprecated

intel-opencl-runtime
yes[^2]
no
newer releases are only available as an SDK, not available in nixpkgs

[^1]: package actually includes GPU driver, but the ICD isn't installed properly so it doesn't work.
[^2]: according to the arch wiki, it supports non-intel CPUs as well.

Thanks for the table! Should we make intel-ocl opt-in if unfree packages are allowed and have an option that we can turn off in future?

That is probably the best approach, perhaps another option to use beignet on older GPUs?

That is probably the best approach, perhaps another option to use beignet on older GPUs?

That then belongs into nixos-hardware propably.

we should also update https://github.com/NixOS/nixpkgs/blob/6f558d3009c20cd2decc5b36057f78a033a6ff11/nixos/doc/manual/configuration/gpu-accel.chapter.md#intel-sec-gpu-accel-opencl-intel and possible
https://github.com/NixOS/nixpkgs/blob/6f558d3009c20cd2decc5b36057f78a033a6ff11/nixos/modules/hardware/opengl.nix#L119

Done. Anything else?

LGTM, but this probably is too minimal to have its own module
I agree with NixOS/nixos-hardware#992 (comment) and I feel like small modules like this can be merged into a big and general intel module.

If we would make a cut and ignore anything older than broadwell, this could probably just be part of an igpu module instead? I am not sure how relevant opencl was in previous generations...

Perhaps this module could be moved as-is to gpu? Like nixos/modules/services/hardware/amdgpu.nix

Perhaps this module could be moved as-is to gpu? Like nixos/modules/services/hardware/amdgpu.nix
Edit: Oops, amdgpu is not under gpu directory, but maybe it should be?

Sounds good. If someone wants to take over, feel free. I might get back to this later otherwise.


[Bug]: Reopen in Devbox shell doesn't work with Cursor

Current Behavior (bug)
I use Cursor (cursor.sh) as my editor, with the Devbox extension installed. When I use the "Devbox: Reopen in Devbox shell environment" command, Cursor closes, but doesn't reopen again.
Expected Behavior (fix)
Cursor closes and reopens.
Additional context
devbox version -v
devbox version -v
Version:     0.8.1
Platform:    darwin_arm64
Commit:      a0bdff918b3dde5ebcfc488f72df5efdf3426253
Commit Time: 2023-11-07T21:43:27Z
Go Version:  go1.21.3
Launcher:    0.2.0

devbox.json
{
  "packages": [
    "rustup@latest",
    "libiconv@latest"
  ],
  "env": {
    "PROJECT_DIR": "$PWD"
  },
  "shell": {
    "init_hook": [
      "rustup default stable"
    ],
    "scripts": {
      "test": [
        "echo \"Error: no test specified\" && exit 1"
      ]
    }
  }
}

Hold on... I tried that command in VS Code Insider and VS Code, but it didn't work there either. Both editors are on their latest versions.

@mikenikles Can you share what OS you are encountering this issue on? We've seen some issues with macOS Sonoma, but haven't found a reliable repro

I recently upgraded to Sonoma 14.1.1, but I also saw it on whichever the previous OS version was. Now that I'm on Sonoma though and given it's a known issue, I'll accept that it doesn't work :)

I have the same problem on NixOS 23.11

@mikenikles @aacebedo We just released version 0.1.4 of the extension. It adds a setting called "Debug Mode" that if you enable, it will keep a log of events for "Reopen in Devbox Shell" feature. The log file is in ./devbox/extension.log. If your problem is still persisting, update the extension and enable debug mode and send me the content of this log file. This will help troubleshooting the issue significantly.

for reference:

@mikenikles @aacebedo We just released version 0.1.4 of the extension. It adds a setting called "Debug Mode" that if you enable, it will keep a log of events for "Reopen in Devbox Shell" feature. The log file is in ./devbox/extension.log. If your problem is still persisting, update the extension and enable debug mode and send me the content of this log file. This will help troubleshooting the issue significantly.

Go this on code-insiders 1.86 on NixOS, not sure it is very useful:
[Tue, 30 Jan 2024 13:58:14 GMT] Installing devbox packages
[Tue, 30 Jan 2024 13:58:14 GMT] Updating VSCode configurations
[Tue, 30 Jan 2024 13:58:14 GMT] Calling "devbox integrate" to setup environment
[Tue, 30 Jan 2024 13:58:14 GMT] child process closed with exit code: 1
[Tue, 30 Jan 2024 14:44:11 GMT] Installing devbox packages
[Tue, 30 Jan 2024 14:44:11 GMT] Updating VSCode configurations
[Tue, 30 Jan 2024 14:44:11 GMT] Calling "devbox integrate" to setup environment
[Tue, 30 Jan 2024 14:44:11 GMT] child process closed with exit code: 1
[Tue, 30 Jan 2024 16:19:59 GMT] Installing devbox packages
[Tue, 30 Jan 2024 16:19:59 GMT] Updating VSCode configurations
[Tue, 30 Jan 2024 16:19:59 GMT] Calling "devbox integrate" to setup environment
[Tue, 30 Jan 2024 16:19:59 GMT] child process closed with exit code: 1

I see the same output.
I also see the following when I select the Output tab, then "Extension Host":
2024-01-30 14:28:51.824 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-ssh, startup: false, activationEvent: 'onStartupFinished', root cause: jetpack-io.devbox
2024-01-30 14:28:51.867 [info] ExtensionService#_doActivateExtension jetpack-io.devbox, startup: false, activationEvent: 'onStartupFinished'
2024-01-30 14:28:51.878 [info] ExtensionService#_doActivateExtension ms-vscode.remote-explorer, startup: false, activationEvent: 'onCommand:remote-internal.setActiveFolders'
2024-01-30 14:29:16.560 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-01-30 14:29:56.720 [error] undefined devbox.reopen {"value":"jetpack-io.devbox","_lower":"jetpack-io.devbox"}

I see the same output.
I also see the following when I select the Output tab, then "Extension Host":
2024-01-30 14:28:51.824 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-ssh, startup: false, activationEvent: 'onStartupFinished', root cause: jetpack-io.devbox
2024-01-30 14:28:51.867 [info] ExtensionService#_doActivateExtension jetpack-io.devbox, startup: false, activationEvent: 'onStartupFinished'
2024-01-30 14:28:51.878 [info] ExtensionService#_doActivateExtension ms-vscode.remote-explorer, startup: false, activationEvent: 'onCommand:remote-internal.setActiveFolders'
2024-01-30 14:29:16.560 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2024-01-30 14:29:56.720 [error] undefined devbox.reopen {"value":"jetpack-io.devbox","_lower":"jetpack-io.devbox"}

@mikenikles On nixos ?
@mohsenari dld you check the extension on insiders build ?

I use Mac OS Sonoma

@aacebedo @mikenikles the changes I made to enable debug logs relied on a feature in devbox cli that wasn't released yet (my apologies). We now have released devbox version 0.9.0. Would you please update your devbox to newest version and retry this?

With devbox 0.9.0:
[Thu, 01 Feb 2024 17:20:16 GMT] Installing devbox packages
[Thu, 01 Feb 2024 17:20:16 GMT] Updating VSCode configurations
[Thu, 01 Feb 2024 17:20:16 GMT] Calling "devbox integrate" to setup environment
[Thu, 01 Feb 2024 17:20:16 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Thu, 01 Feb 2024 17:20:16 UTC] Computing devbox environment
[Thu, 01 Feb 2024 17:20:16 UTC] Signaling VSCode to close
[Thu, 01 Feb 2024 17:20:16 UTC] Re-opening VSCode in computed devbox environment
[Thu, 01 Feb 2024 17:20:16 UTC] stdout:
 stderr:
[Thu, 01 Feb 2024 17:20:16 UTC] exec: "code": executable file not found in $PATH
[Thu, 01 Feb 2024 17:20:16 GMT] child process closed with exit code: 1

That makes sense since Cursor doesn't have a code binary. I tried with alias code=/Applications/Cursor.app/Contents/MacOS/Cursor in my bash profile, but that didn't work.
I'll have to look into it in more detail later, but posting this for now in case anyone has ideas.

Fixed it with sudo ln -s /Applications/Cursor.app/Contents/MacOS/Cursor /usr/local/bin/code.
However, it gets weirder now 😕:
[Thu, 01 Feb 2024 17:37:18 GMT] Installing devbox packages
[Thu, 01 Feb 2024 17:37:18 GMT] Updating VSCode configurations
[Thu, 01 Feb 2024 17:37:18 GMT] Calling "devbox integrate" to setup environment
[Thu, 01 Feb 2024 17:37:18 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Thu, 01 Feb 2024 17:37:18 UTC] Computing devbox environment
[Thu, 01 Feb 2024 17:37:19 UTC] Signaling VSCode to close
[Thu, 01 Feb 2024 17:37:19 UTC] Re-opening VSCode in computed devbox environment
[Thu, 01 Feb 2024 17:37:19 UTC] stdout:
 stderr: node:internal/modules/cjs/loader:1085
  throw err;
  ^

Error: Cannot find module '/Users/m/projects/x/y/z'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1082:15)
    at Module._load (node:internal/modules/cjs/loader:927:27)
    at f._load (node:electron/js2c/asar_bundle:2:13377)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:96:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v18.15.0

[Thu, 01 Feb 2024 17:37:19 UTC] exit status 1

Possibly no longer Devbox related 🤔?!

If I add an empty index.js to the repo root and a "main": "index.js", entry to the package.json` file, I end up with this:
[Thu, 01 Feb 2024 17:42:51 GMT] Installing devbox packages
[Thu, 01 Feb 2024 17:42:51 GMT] Updating VSCode configurations
[Thu, 01 Feb 2024 17:42:51 GMT] Calling "devbox integrate" to setup environment
[Thu, 01 Feb 2024 17:42:51 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Thu, 01 Feb 2024 17:42:51 UTC] Computing devbox environment
[Thu, 01 Feb 2024 17:42:51 UTC] Signaling VSCode to close
[Thu, 01 Feb 2024 17:42:51 UTC] Re-opening VSCode in computed devbox environment

@mikenikles
I just installed cursor. And during first setup it asks you if you want to setup cursor to open with command line "code" or "cursor" I ignore that prompt on purpose. Then once cursor is opened, I did cmd + shift + p and ran "Shell Command: Install 'Code' command" .
After that I tried reopen in devbox and it worked correctly. Can you try that instead of sudo ln -s /Applications/Cursor.app/Contents/MacOS/Cursor /usr/local/bin/code?
When you see this line in the log: Re-opening VSCode in computed devbox environment, it basically means devbox cli is running the command code <path to workspace when IDE was closed>. So if cursor doesn't open it's equivalent to running devbox shell in a terminal then inside devbox shell running code .

Excellent!! That does the trick, I'm all set. Thank you 🙏!
Funny enough, running that "Shell Command: Install 'Code' command" does the following:
ll `which code`
lrwxr-xr-x 1 root wheel 56 Feb  1 14:29 /usr/local/bin/code -> /Applications/Cursor.app/Contents/Resources/app/bin/code

Looks like my symlink pointed to the wrong file :)
Leaving this open until @aacebedo confirmed it works for him too.

I saw the same issue because the binary for the insiders build is code-insiders and not code. I think devbox shall add the support of code-insiders or refactor the way the IDE are handled (like providers for instance).

@aacebedo that's a good suggestion. I can add in settings the path to binary that opens vscode so that it can be configurable.
For the time being making a symlink seems to be the workaround.

I'm experiencing a similar (or identical?) error. Host is Windows target is a VM connected via SSH remote. When executing "Devbox: Reopen in Devbox shell environment", the following error is displayed.

The contents of the .devbox/extension.log file isn't helpful
[Wed, 28 Feb 2024 15:40:04 GMT] Installing devbox packages
[Wed, 28 Feb 2024 15:40:04 GMT] Updating VSCode configurations
[Wed, 28 Feb 2024 15:40:04 GMT] Calling "devbox integrate" to setup environment
[Wed, 28 Feb 2024 15:40:04 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Wed, 28 Feb 2024 15:40:04 UTC] Computing devbox environment
[Wed, 28 Feb 2024 15:40:04 GMT] child process closed with exit code: 0
[Wed, 28 Feb 2024 15:43:10 GMT] Installing devbox packages
[Wed, 28 Feb 2024 15:43:10 GMT] Updating VSCode configurations
[Wed, 28 Feb 2024 15:43:10 GMT] Calling "devbox integrate" to setup environment
[Wed, 28 Feb 2024 15:43:10 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Wed, 28 Feb 2024 15:43:10 UTC] Computing devbox environment
[Wed, 28 Feb 2024 15:43:10 GMT] child process closed with exit code: 0
[Wed, 28 Feb 2024 15:45:52 GMT] Installing devbox packages
[Wed, 28 Feb 2024 15:45:52 GMT] Updating VSCode configurations
[Wed, 28 Feb 2024 15:45:52 GMT] Calling "devbox integrate" to setup environment
[Wed, 28 Feb 2024 15:45:52 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Wed, 28 Feb 2024 15:45:52 UTC] Computing devbox environment
[Wed, 28 Feb 2024 15:45:52 GMT] child process closed with exit code: 0
[Wed, 28 Feb 2024 16:20:45 GMT] Installing devbox packages
[Wed, 28 Feb 2024 16:20:45 GMT] Updating VSCode configurations
[Wed, 28 Feb 2024 16:20:45 GMT] Calling "devbox integrate" to setup environment
[Wed, 28 Feb 2024 16:20:45 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Wed, 28 Feb 2024 16:20:45 UTC] Computing devbox environment
[Wed, 28 Feb 2024 16:20:45 GMT] child process closed with exit code: 0
[Wed, 28 Feb 2024 16:22:38 GMT] Installing devbox packages
[Wed, 28 Feb 2024 16:22:38 GMT] Updating VSCode configurations
[Wed, 28 Feb 2024 16:22:38 GMT] Calling "devbox integrate" to setup environment
[Wed, 28 Feb 2024 16:22:38 UTC] Devbox process initiated. Setting up communication channel with VSCode process
[Wed, 28 Feb 2024 16:22:38 UTC] Computing devbox environment
[Wed, 28 Feb 2024 16:22:38 GMT] child process closed with exit code: 0

What error log (as mentioned in the error dialog) is relevant here to pin the error?

@tmeckel the functionality of Reopen in devbox shell environment doesn't work when you're connected to a remote env and also when called from Windows connected to WSL as a remote env. I explained the reason for it, with a bit more details here:
https://github.com/jetpack-io/devbox/issues/1781#issuecomment-2038136742

@mohsenari sadly to say, then devbox is not an option for me. Stick to DevContainers then.

@mohsenari does this might change anything?
https://github.com/microsoft/vscode-docs/blob/main/remote-release-notes/v1_89.md#wsl
I know they're talking about connecting to a WSL instance when you're connected to a Windows machine via SSH. But I think they might have changed the inner workings of WSL remote support for that.

@tmeckel I need to do some testing to see if there is a way to connect to WSL from VSCode's extension. Then spawn a subprocess, compute devbox env and lastly, reopen vscode from within WSL instance.
I'll play around on my windows machine and let you know if it's possible. It would be nice to have reopen in devbox shell work in Windows.

Can't wait about your results 👍🏼👍🏼 would be awesome to be able to use devbox in WSL

It would be amazing if at the same time it could be resolved on remove servers as well. as mentioned here: https://github.com/jetify-com/devbox/issues/1781#issuecomment-2038136742

@mikenikles vscode extension version 0.1.6 was published. With this version, reopen in devbox should work fine with Cursor. Closing this issue but reopen if the issue is not resolved.

@mohsenari still no luck with a devbox environment located on remote VM using SSH.
Debug log is not very helpful
[Sun, 06 Oct 2024 14:22:15 GMT] Installing devbox packages
[Sun, 06 Oct 2024 14:22:15 GMT] Updating editor configurations
[Sun, 06 Oct 2024 14:22:15 GMT] Calling "devbox integrate" to setup environment
[Sun, 06 Oct 2024 14:22:15 UTC] Devbox process initiated. Setting up communication channel with the code editor process
[Sun, 06 Oct 2024 14:22:15 UTC] Computing devbox environment
[Sun, 06 Oct 2024 14:22:15 GMT] child process closed with exit code: 0

Work around on remote environments:
https://github.com/jetify-com/devbox/issues/1781#issuecomment-2395511275


Given an example of ShardingSphere logs output to CloudWatch Log Group

Given an example of ShardingSphere logs output to CloudWatch Log Group
Aim
When a ShardingSphere cluster is running on AWS EC2, the application logs could be output to CloudWatch for further consumption.
Instructions

Create a ShardingSphere cluster on EC2.
Using CloudWatch to gather logs save them to a specific log group.

Hint

https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AgentReference.html
https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/QuickStartEC2Instance.html

Result
This work could be finished with a document under doc/ recorded the operating procedure.

This is solved in #151


Question: why are things like Babel included as production dependencies?

from package.json:
  "dependencies": {
    "array-find": "^1.0.0",
    "babel-cli": "^6.3.15",
    "babel-core": "^6.3.15",
    "babel-plugin-add-module-exports": "^0.2.0",
    "babel-plugin-transform-decorators-legacy": "^1.2.0",
    "babel-plugin-transform-es2015-modules-commonjs": "^6.7.4",
    "babel-preset-es2015-loose": "^6.1.3",
    "babel-preset-react": "^6.3.13",
    "babel-preset-stage-1": "^6.3.13",
    "exenv": "^1.2.0",
    "inline-style-prefixer": "^1.0.3",
    "rimraf": "^2.4.0"
  },
  "devDependencies": {
    "babel-eslint": "^6.0.0",
    ...

Just curious, why are all those deps in dependencies, not devDependencies?

So that we can build for you if you install directly from git: https://github.com/FormidableLabs/radium/blob/2fb6a0b79e0d2795608e68cfc8851050c5019169/package.json#L28
We've talked about removing this many times. I don't know for sure, but I'll bet git installs are a small fraction (1/1000?) of NPM installs.

+1 for removal, otherwise every "npm install" of radium pulls in a lot of cruft.

Over in Victory-land, we're considering doing what a lot of React projects are doing which is do a last minute git dirty swap with moving the postinstall-necessary dependencies to devDepencies on npm publish in a manner that are not committed to git source.
This has the nice effect of installations from npm are tight and have only what is needed while git installations still work with the existing postinstall flow.
Here's our current strawman: https://github.com/FormidableLabs/victory/issues/186#issuecomment-223872054  Only kink is utilizing various lifecycle things from publishing with npm version which I'm not sure we do here.

Stepping back here, we don't publish babel deps to npm. Just in git source. Looking at<EMAIL_ADDRESS>we have:
  "dependencies": {
    "array-find": "^1.0.0",
    "exenv": "^1.2.0",
    "inline-style-prefixer": "^1.0.3",
    "rimraf": "^2.4.0"
  },

Looking in git logs, it looks like @ianobermiller already did this months back. Am I perhaps missing something?

@ryan-roemer It does look like the npm install is quick and doesn't include any of the cruft, so maybe @callumlocke is not ware of the removal of babel dependencies before publishing to npm. If so, is this currently not an issue @callumlocke?

Closing this one in favor of #731. phew

@ryan-roemer Ah yes, I totally forgot about https://github.com/FormidableLabs/radium/commit/90f353b8c1845bed43b32bd2d5c9b6f8883d49b2


failed to enable loadbalancer

version: v1.1.0
steps:

install kind k8s cluster
install metallb
https://metallb.universe.tf/installation/
helm repo add metallb https://metallb.github.io/metallb
helm install metallb metallb/metallb -f values.yaml

configInline:
  address-pools:
   - name: default
     protocol: layer2
     addresses:
     - <IP_ADDRESS>/24

install harbor-operator v1.1.0
install sample harbor minimal_stack_fs.yaml

   expose:
     core:
-      ingress:
-        host: core.harbor.domain
-        controller: default
+      loadbalancer:
+        enable: true
       tls:
         certificateRef: sample-public-certificate
   internalTLS:

failed to curl loadbalancer ip

we still should add a new nginx component in order to route the traffic to core pods and portal pods.

we can't easily fix the problem that harbor install fail when enable minio.redirect and loadbalancer now. So currently we should revert loadbalancer support.
User can still install with nginx-ingress or contour-ingress, and apply loadbalancer manually.


Failing CI

CI is currently failing, see https://travis-ci.org/humbug/box/builds/636296244

Seems I can not reproduce it locally - this is either due to oudated dependencies or some other issue.


esp_http_client: Fix unsigned integer overflow (IDFGH-10477)

Fix unsigned integer overflow when content_length is -1.
The proposed change is to modify the format specifier for content_length from PRIu64 to PRId64, which will print the signed value as a 64-bit integer instead.

@hwqchi Thanks for adding the fix.

sha=482f6340b96a0a5ab5659ad7da95df32daf8f5e7


Support all sample template selection and project generation

Support all sample template selection and generate project according to selected sample templates

drop from plan, closing it


Analyzer unable to detect a generic type with a nullable type

This tracker is for issues related to:

Analyzer
Dart SDK Version: 2.16.2 on MacOSX and Linux

In the following code, it will throw an exception, but analyzer doesn't detect it. Not sure if it is spec, but it is not easy to spot the error by eyes. An analyzer option to detect it?
void f(Map<String?, int> values) {
  values[null] = 100;
}
void main() {
  f(<String, int>{});
}

Statically checking this requires variance support.
https://github.com/dart-lang/language/issues/524


Fix layout declaration for dashr-ncbi-explorer

This PR proposes to update app$layout such that the specification of components is contained with a list, which is wrapped within htmlDiv. The previous layout definition was supported prior to plotly/dashR#121, but now results in an error. The changes should restore the app's functionality.

Successfully deployed to dash-playground with required fixes.


Redirect to https by default for ua.daito.io

Reversed my commit for this, since this did not need a code change, but only a env var in heroku dashboard.


是不是已经含泪停止维护了

https://github.com/angcyo/CalendarView

@angcyo That's very nice of you~

https://github.com/angcyo/CalendarView

and you, my friend, are the real hero


Update index.js

Changes Unknown when pulling 4e8b7fa19b91922b3d2cb9787e83446bfb5b7f34 on test-use-strict into ** on master**.

Changes Unknown when pulling 5ea7470eba36bec1161649ce040797c5436d613e on test-use-strict into ** on master**.


Matmul narrow no simd

Disable SIMD when the dimension is known at compile time and is smaller than the simd width.
This PR responds to issue #1117

Also removed #def for debug and use LLVM_DEBUG now

Jenkins Linux ppc64le Build #2616 [push] Matmul narrow no simd (#... started at 10:21

Jenkins Linux s390x Build #3501 [push] Matmul narrow no simd (#... started at 10:14

Jenkins Linux amd64 Build #3509 [push] Matmul narrow no simd (#... started at 09:14

Jenkins Linux s390x Build #3501 [push] Matmul narrow no simd (#... passed after 43 min

Jenkins Linux amd64 Build #3509 [push] Matmul narrow no simd (#... passed after 1 hr 7 min

Jenkins Linux ppc64le Build #2616 [push] Matmul narrow no simd (#... passed after 1 hr 15 min


Swaprouter - Add AfterCFMMPoolCreated Hook

Background
See @p0mvn's comment here https://github.com/osmosis-labs/osmosis/pull/3607#discussion_r1038805065
Suggested Design
Since concentrated liquidity pools do not require gauges, we want to make a AfterCFMMPoolCreated hook that triggers gauge creation instead of how it is currently triggered on AfterPoolCreated.
Acceptance Criteria
TBD

Hi would I work with this

This is now completed by https://github.com/osmosis-labs/osmosis/pull/4838


vjjhvgg

Describe the feature that you would like added

What component or utility would this be added to

Have you discussed this feature with our team, and if so, who

Additional context/screenshots

no description present, closing this issue
cc: @Dhoot


Some translated SVG images render slow

Description
When the example svg shown here is included into the pdf using typst, it renders much slower and requires more cpu (tested with different pdf viewers) than an exported svg to pdf using for example chrome or edge (using ctrl+p, then print to pdf).
This is not really a bug since the output looks as expected, but it would be nice if the produced code would render faster (probably the code generation is less good).
Here are the two output files:
typst_svg_to_pdf.pdf
edge_svg_to_pdf_export.pdf
This is also seen with other svg figures (for example from lilypond), not just with the given svg figure.
The behaviour can be seen especially with Firefox (pdf.js) and SumatraPDF. It seems the runtime depend on the SVG figures included. Some render quite slow, some quite fast (I try to add more examples).
Update: it seems, the biggest slow down appears, when fonts are included (texts are currently drawn as paths). A single zoom in the document takes 10 seconds to render then (tested with svg images from lillypond).
Related: https://github.com/typst/typst/issues/689, https://github.com/typst/typst/issues/371
Use Case
Including PDFs would not slow down the PDF browsing that much and the overall PDF viewing experience would be better (assuming an SVG was included)

SVG conversion has been improved by a lot now, and I don't seem to be able to reproduce the slow rendering issue with the newest version, so I will close this. Feel free to comment again if you are still encountering issues and I will look into it.


Fix memory leaks in ValidateSchema

This pull request addresses the 4th one raised in #2469 .
The main change here is to move the pointers to the three xml api objects to the evaluate function as function-scope stack variables.  At each stage in the function where a return may occur, all so-far-relevant xmlSchemaFree functions are called to clean up allocated memory.
Some additional memory leak scenarios have been addressed. For examples (transaction->m_xml->m_data.doc == NULL) and (transaction->m_xml->m_data.well_formed != 1).  These two in particular have been dealt with by performing the checks at the beginning of the function.

Merged! thanks!


Validation bug

A host file supports a line like this
<IP_ADDRESS> domain1.com domain2.com domain3.com
If i use this format in Hozz. The line turnes red.

Works on the latest release


[BEAM-4322] Enforce ErrorProne analysis in protobuf extensions project

Enforces failOnWarning
Adds build/generated as an excluded error prone directory
Fixes error-prone, DefaultCharset warning. Just assumed to use utf-8

R: @swegner

LGTM. Can a committer help merge this? /cc @pabloem @iemejia

Done! : )


Information in dev/README.md appears stale, incorrect, or incomplete

The information under the Normal Testing heading doesn't seem right.
First, the link to the bosh-softlayer-cpi-release doesn't work. That appears to be due to the recent project move. Ignoring that, I can't find a Vagrantfile or any other instructions or information in the release on testing.
Updating the documentation to more clearly explain test approaches would help those of us that are trying to use or contribute to the project.

Hey, @sykesm, thanks for feedback. We added a bug #120648861 in the tracker for address this.

Also @cunnie and I submitted PR 149 on bosh-docs which will contain (eventually) all authoritative docs to get started.
/cc @mattcui and @jianqiu

@sykesm https://github.com/cloudfoundry/bosh-softlayer-cpi/blob/master/dev/README.md has been updated.


Firefox crashed and now Better Bibtex doesn't work: no citation keys

While working this morning, Firefox unexpectedly crashed (crash report: https://crash-stats.mozilla.com/report/index/22a3185f-c46d-4e65-9108-9f7b02160627). Once I brought it back up, all my citation keys were gone. I completely uninstalled all Zotero add-ons as well as Zotero itself, rebooted computer, and still, when I bring it all back up and reinstalled with latest versions, there are no citation keys. When I run an export using Better Bibtex, I get an error saying that the file could not be exported. When I run export without Better Bibtex, it works fine. When I run autoexport using Robert Kühn's plug-in, it also works fine. But I still have no citation keys with Better bibtex and cannot export with it. I sent a Better Bibtex bug report. Please assist. Thanks!

What was the ID of the bug report?

I've found at least one problem that could affect you -- could you try https://github.com/retorquere/zotero-better-bibtex/releases/download/builds/zotero-better-bibtex-1.6.66-circle-2596.xpi ?

I’m afraid I didn’t not the ID number. Is there a way I can find it? Thanks
SNS

On Jun 27, 2016, at 7:38 AM, retorquere<EMAIL_ADDRESS>wrote:
What was the ID of the bug report?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/retorquere/zotero-better-bibtex/issues/526#issuecomment-228733697, or mute the thread https://github.com/notifications/unsubscribe/ATO6HxbmoiyALFZBAKm_ILe3wcwLGPWxks5qP8RhgaJpZM4I_DED.

Nope, once submitted, the ID is discarded. But specially for you, retries are free :)
Just install the debug version from https://github.com/retorquere/zotero-better-bibtex/releases/download/builds/zotero-better-bibtex-1.6.66-circle-2596.xpi, and if the problem still exists, submit a new error report.

It looks like that fixed it. I had found a discussion thread that talked about BBT database becoming corrupt. Is that what happened here? I want to try to understand what happened so I can be wary in the future and avoid it. Thanks for your help. Sorry for missing the ID.
SNS

On Jun 27, 2016, at 8:25 AM, retorquere<EMAIL_ADDRESS>wrote:
Nope, once submitted, the ID is discarded. But specially for you, retries are free :)
Just install the debug version from https://github.com/retorquere/zotero-better-bibtex/releases/download/builds/zotero-better-bibtex-1.6.66-circle-2596.xpi https://github.com/retorquere/zotero-better-bibtex/releases/download/builds/zotero-better-bibtex-1.6.66-circle-2596.xpi, and if the problem still exists, submit a new error report.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/retorquere/zotero-better-bibtex/issues/526#issuecomment-228744429, or mute the thread https://github.com/notifications/unsubscribe/ATO6H-NJHAYUmjBw522q7J8-XIzFvq2mks5qP89mgaJpZM4I_DED.

No, this was a different issue. I don't know what caused Firefox to crash, but what stopped BBT from working is an error in the upgrade-detection. I would expect that (unless you deleted your profile) the citekeys should just reappear now.
I've scheduled a new release, .67 should be out soon, but it's just the release of the version you have now.

Ok. Good to know. Yeah, all citekeys are back and everything is functioning normally. Thanks for all your work and help on this!
SNS

On Jun 27, 2016, at 8:31 AM, retorquere<EMAIL_ADDRESS>wrote:
No, this was a different issue. I don't know what caused Firefox to crash, but what stopped BBT from working is an error in the upgrade-detection. I would expect that (unless you deleted your profile) the citekeys should just reappear now.
I've scheduled a new release, .67 should be out soon, but it's just the release of the version you have now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/retorquere/zotero-better-bibtex/issues/526#issuecomment-228745982, or mute the thread https://github.com/notifications/unsubscribe/ATO6H3q4yiW7keqVwY3WC5fDFNrAwWMyks5qP9DPgaJpZM4I_DED.

No worries, and sorry for the disruption.

(Since that error report on DB corruption, BBT has gone back to using the Zotero database facilities. That should take care of DB corruption, even if data loss as a result of such hard crashes is still possible)


While pressed home button and tap on push message, nothing happened. It should invoke the application

Hi,
Thanks in advanced.
Whenever i minimize the app by pressing home button, notifications received but when i tap on the message nothing happened. It should launch the app again or invoke the current page where i minimized the app. Please suggest.
Expected Behaviour
push event handler should not be called when new push message received when app is in foreground.
Actual Behaviour
push event handler are called when new push received when app is in foreground
Reproduce Scenario (including but not limited to)
Just send push message when app is in foreground and see pushObject.on('notification') is called
Steps to Reproduce
Just send push message when app is in foreground and see pushObject.on('notification') is called
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Android 7.1.0
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
Mi Not 4 (Android 6.0.1)
Cordova CLI version and cordova platform version
cordova --version                                   8.0.0
cordova platform version android                    android 7.1.0
Plugin version
cordova plugin version | grep phonegap-plugin-push   # 2.2.2
Sample Push Data Payload
{
"message": "This offer expires at 11:30 or whatever",
"title": "Test Notification",
"additionalData": {
"id": "class_id"
}
}

Sample Code that illustrates the problem
pushObject.on('notification').subscribe((notification: any) => {

  this.storage.get('showPush').then((val) => {

    if (val) {
      console.log('Your age is', val);
      console.log('New notification!', JSON.stringify(notification));

      let room_id = notification.additionalData.room_id;
      console.log(notification.additionalData.room_id);
      this.navCtrl.push(DetailsPage, { room_id: room_id });

    }
  });

}

);

Logs taken while reproducing problem
Not available

@shri1983 check out the info on Chinese manufactured Android phones:
https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/PAYLOAD.md#chinese-android-phones
Also, I need to see the payload you are sending, not the one you received. Log would really help in this case.

Hi Mac,
Thanks for your response. Here is the information that you have requested:
Actual;  When i tap on push message, it called pushObject.on('notification') callback from background.
Expected: It should invoke my application.
Logs:  When i tap on push message
detail.","additionalData":{"pushFor":"ROOMPUBLISH","dismissed":false,"room_id":" avalid room id","coldstart":false,"foreground":false}}
And Payload that we are sending is:
PayloadData {
data [
"title": "hi has been published.",
"message": "hi has been published. Please click to view room detail.",
"pushFor": "ROOMPUBLISH",
"room_id": "43e85674b65f8a3"
]
}
Also I examined the link that you have send, but this link explained the problem when we force close the application, but in my case i am not force closing instead just minimize the app by pressing hardware home button.

@shri1983 can you open the AndroidManifest.xml and tell me what launchMode is set to?

Hi Mac,
Thanks for your valuable time and response.
My launch mode is android:launchMode="singleInstance". Please suggest what launch mode we should use for this.
and below is my android manifest  tag code:

See https://github.com/phonegap/phonegap-plugin-push/issues/1690


[Security] Update library vulnerability

[Security] Update library vulnerability

The code vulnerability was fixed in commit id f50479c


beam/fetchMixDeps: disable --only flag when mixEnv is empty

beam/fetchMixDeps: disable --only flag when mixEnv is empty

mixEnv being empty will include all dependencies.

Brief documenting because it's useful for loading tests dependencies.

I'm a bit unsure about how to document this... Still thinking.
(Actually, tests should be documented in Elixir.)

Thank you !

@happysalada Hi.
I'm sorry to inform you there is an issue in this patch I proposed.
As it is, when fetchMixDeps is executed without mixEnv argument. In installPhase, env vars are as:

MIX_ENV => prod
mixEnv =>
Which causes default behavior to include all dependencies and not just prod.
Still knowing this, I couldn't properly figure out why this is going on, because:

attrs (which included mixEnv) is merged to attrs. I suppose, mixEnv should be there and with prod value. Odd isn't it? I'm missing something.

I'm not proposing a solution yet. Just letting you about this.

Good catch !


Use tilde (~) instead of carrot (^) in version 1

I just discovered that carrot (^) would not work on really old Node.js versions, tilde (~) should be used instead on version 1. Major release is needed to drop old Node.js versions, even really old Node.js versions.
P.S. README shows a version 1.5.1 which does not really exist due to my own error. This should be removed from README at the same time.

FYI version 1.14.5 mostly passes its test suite on deprecated Node.js versions 4.0, 0.12, and 0.10. Newer 1.x releases of this package should also be able to pass most of its test suite on these deprecated Node.js versions.


no sidebar, no topbar in Demo

Hello
I have a problem with getting jupyter-book to run correctly. While jupyter-book create mybookname --demo does execute, as does jupyter-book build mybookname, the resulting build lacks sidebar and topbar. The topline of "Books with Jupyter" reads: -- interact_link: content/intro.ipynb kernel_name: python3 has_widgets: false title: |- Home prev_page: url: title: |- next_page: url: /guide/01_overview.html title: |- Getting started suffix: .ipynb comment:
PS: initially, the installation of jupyter-book failed completely (error messages involving nbconvert), but conda install anaconda and conda update --all seemed to work.
I have: jupyter --version: jupyter core : 4.5.0 jupyter-notebook : 6.0.1 qtconsole : 4.5.5 ipython : 7.8.0 ipykernel : 5.1.2 jupyter client : 5.3.3 jupyter lab : 1.1.4 nbconvert : 5.6.0 ipywidgets : 7.5.1 nbformat : 4.4.0 traitlets : 4.3.3
The OS is macOS 10.14.2. Jupyter runs correctly. jupyter-book as been installed with pip install jupyter-book
Many thanks for your suggestions.

hmmm - could you add a link to your repository? that's a strange bug!

Thanks for getting back. I am new to github, so I do not understand the request (sorry).
The first few lines of the Demo generated intro.html are:
interact_link: content/intro.ipynb
kernel_name: python3
has_widgets: false
title: |-
Home
prev_page:
url:
title: |-
next_page:
url: /guide/01_overview.html
title: |-
Getting started
suffix: .ipynb
comment: "PROGRAMMATICALLY GENERATED, DO NOT EDIT. SEE ORIGINAL FILES IN /content"

hi @ChristianSchluter  !
Sorry, to be explicit -- how are you viewing your book ? Did you use the Docker image, a local Ruby install, or are you hosting it on GitHub pages ?

Hello,
I am looking directly at the intro.html using my browser (Firefox), in the same way I would look at the index.html which would have been generated by bookdown and R notebooks.

Ah, got it, thank you ! Unfortunately you won't be able to open it that way -- please see the docs here on creating your book:

building locally
building online

If there's anything that's unclear, there, I'd be happy to help troubleshoot !

Closing as this should be superceded by beta.jupyterbook.org


Visualization with HoloViews

Notes

Reset github actions

Reset github actions

Too many commits behind develop, replacing with #54 and future PRs


[DON'T MERGE UNTIL 2.19.0][RE-236] Update Nomad and Docker versions

Update Nomad and Docker to the versions used by cloud.
Also, we don't run multiple datacenters, and us-east-1 was a lie. Cloud always used default so we have hardcoded that value in schedulerer.

I am going close this card in favor of https://github.com/circleci/enterprise-setup/pull/173.  Changing the branch name to server-2.19 will allow for easier tracking by the the Release Engineering team.


[WIP] Compute conflict/IIS

First step for https://github.com/JuliaOpt/JuMP.jl/issues/1035: implement the IIS/conflict within the CPLEX package.
For now, quite basic: call the conflict refiner, store the information it returns in a structure (allocated only when needed, so that the overhead for people not using it is just one pointer per model).
Next, I will implement MOI attributes that call these functions (if the conflict member of Model is nothing, call the conflict refiner and retrieve its result; if the member is already available, just return the data from it). One question I have for now: I guess the model object may be reused; what happens when it is updated (for instance, the first model is infeasible; the user removes the culprit constraint, then resolves; say they call the conflict refiner again, how is the model reset?).

Why not just call refineconflict inside the c_api_getconflict function, and return the conflict struct? Given that the model is infeasible, I don't think we need to worry about the performance of unnecessarily calling refineconflict multiple times. This also resolves your updating questions: we just call refineconflict every time.

I got to the MOI attribute step. As suggested in https://github.com/JuliaOpt/JuMP.jl/issues/1035, I tried to be consistent with the existing API: an attribute per constraint and per variable indicating whether they participate in the conflict or not. I could not find an example in MOI where an attribute returns a full-fledged data structure.
Following the tutorial https://github.com/blegat/JuMP-dev_2019_tutorial/blob/master/Defining new attributes.ipynb, I defined the attributes as is_set_by_optimize: the value of these attributes should not come from the cache, I think.
To work with that, I added a function to start the conflict refiner (a function that could move to MOI at some point). I feel bad about calling the conflict refiner each time such an attribute is retrieved (that would mean a very large number of calls to the conflict refiner, while only once is enough).
About the status codes, I used what is already available, even though that looks a bit painful in the eye (I use MOI.INFEASIBLE to indicate that the conflict refiner found no solution because of feasibility…). I could find no mapping for the contradiction status returned by CPLEX (due to the previous use of MOI.INFEASIBLE). Would it be better to add a new enumeration to cover these cases, even when this enum could overlap many termination statuses?
For now, I completely ignore rowstat and colstat. I think these should not really be available to the user as such, but rather through the existing interface (one attribute per variable/constraint): these arrays indicate, when the conflict is not minimal, whether a constraint/variable has been proved to be in/out the conflict, or no proof has been found.

I've addressed the majority of your comments, I think, except for the automatic call to c_api_getconflict, as the computed conflict should be wiped out whenever the model changes: your way, the conflict will never be computed again if the model is modified. Or did I miss something?

If we're making compute_conflict public, it needs a docstring.

Shoudln't we also reset the conflict member every time the model is updated, to avoid problems (even though this might have a very slight performance impact)?

Shoudln't we also reset the conflict member every time the model is updated

Potentially, but that opens up a can of worms. Let's just force the user to call compute_conflict for now.

While I was working again on this, I wonder whether VariableConflictStatus actually makes sense: getting through the documentation of both CPLEX and Gurobi, they both have an attribute for variables, but only indicating whether their upper/lower bounds are included in the conflict/IIS. So I'm thinking of deleting it. What do you think of it?
(For the rest of your comments, I'm still working on them, focusing more on correctness than niceness for now.)

If it is only for bounds, then yeah, we probably don't need VariableConflictStatus. This is one reason why we're prototyping this in a package first before adding it to MOI.

For me, I consider that this is done (I was surprised that affine-in-interval constraints are not supported). Or did I miss something?

Is it possible to test a model when the ConflictStatus is not MOI.OPTIMAL somehow?

That revealed an awkward situation, where compute_conflict would error… I added a try-catch to avoid this (while c_api_getconflict is as close as possible to CPLEX' behaviour).

Better this way? (There is still a discussion about the POSSIBLE codes that needs to be resolved before merging.)

Can we test the try-catch please?

Isn't that what https://github.com/JuliaOpt/CPLEX.jl/pull/233/files#diff-d6eba113d1d7863964be035e6eada3a5R270 is about?

Oops. I didn't see that test.

Locally (Windows 10 x64, Julia 1.1.0 x64, CPLEX 12.8.0 x64), they do.

It seems no one has more comments for this PR; maybe it should be merged?

It seems to have conflits. You have to rebase it by git fetch origin master && git rebase origin/master

When I finished working on this PR, there was no conflict at all.

Here is the rebase. Could this be merged soon?

@odow @blegat up

Sorry @dourouc05, on it now.

Great, thanks!


Two cards with the same year were played

Since the resolution of dates seems to only be down to the year, it seems that ties should be awarded either way. In the screenshot below, I placed Scala before Death Grips, both counted as 2010, but the game considered it incorrect.

It's currently meant to just avoid giving cards that have the same year as any that are already played, so that's a bug!

By the way, I believe in the card game "Chronology", if the events happened in the same year, the player is allowed to put them in either order.

Hmm that would be another way of handling it, yeah.

Same issue

could be sorted based on month/day if present or if not in any order

Some wikidata items don't have have accuracy down to month/day, only year.

Not only it was the same year, it was also the same day.

Same issue

 same issue here too !

Same issue here

As above, so below :)
this game is a lot of fun, thanks for writing it.

There's no need to add screenshots of the same problem, please just add a thumbs up on the top post if you also see the issue.

This should be fixed by https://github.com/tom-james-watson/wikitrivia/pull/57!


Modal visibility when screen is between 640px to 1027px

Please find the image below:
Modal is not showing in a certain range of screen sizes.

Changes made:

Output:

@Ujairul-CX-git I would look at modifying the actual source files instead of the generated dist/ like here
I would also in the future keep an eye on https://github.com/acidjazz/nuxt-tailvue since most of our progress is now moving to this package

@Ujairul-CX-git I would look at modifying the actual source files instead of the generated dist/ like here
I would also in the future keep an eye on https://github.com/fumeapp/tailvue since most of our progress is now moving to this package

Sure will do that! Thanks for pointing it out @acidjazz!

@Ujairul-CX-git I would look at modifying the actual source files instead of the generated dist/ like here
I would also in the future keep an eye on https://github.com/fumeapp/tailvue since most of our progress is now moving to this package

Sure will do that! Thanks for pointing it out @acidjazz!

@acidjazz Can you please review this fix please? Thanks in advance!

@nilanjan-codelogicx sure! do me a favor and remove the compiled file changes in dist/ and then i'll have those generated when i issue a release

@nilanjan-codelogicx sure! do me a favor and remove the compiled file changes in dist/ and then i'll have those generated when i issue a release

@acidjazz I have made the changes you requested. Please let me know if any other changes you want here.

@Ujairul-CX-git https://github.com/acidjazz/tv-modal/releases/tag/v1.0.25 👏


Update the Guidelines component to handle empty props

Currently, the component takes 'heading', 'description' and 'guidelines' as three props to render accordingly, but if we pass an empty prop like we don't pass the 'guidelines' array, the component might give an undefined error.
So, it makes sense to handle empty props passed to the component separately.
I am working on this and will soon generate a PR for the same :)

Resolved!