"private fields are not currently supported" error in browser

With Firefox (89.0) I'm getting the following error message:
Uncaught SyntaxError: private fields are not currently supported

Importing the js file created with deno bundle<EMAIL_ADDRESS>

It works using the file from client/dist/remote.js.

Thanks for reporting @retog . I will add a more browser compatible bundle in the next release. I will also minify it.

Just for the record, I run the deno bundle command with this tsconfig.json file:
{
  "compilerOptions": {
    "removeComments": true,
    "lib": ["esnext", "dom", "dom.iterable", "dom.asynciterable", "deno.ns"], // include "deno.ns" for deno namespace
    "experimentalDecorators": true,
    "importsNotUsedAsValues": "preserve",
    "strict": true /* Enable all strict type-checking options. */,
    "noFallthroughCasesInSwitch": false /* Report errors for fallthrough cases in switch statement. */
  }
}

To make it compatible with older Safari versions I will run babel with:
{
  "presets": [
    [
      "@babel/env",
      {
        "modules": false
      }
    ]
  ],
  "plugins": ["@babel/plugin-proposal-class-properties"]
}

Then I will use terser to minify it.
I would welcome additional recommendations.

Thanks, @timonson!
I'm totally new to deno and haven't found out how client/dist/remote.js is generated. Using the pre-generated file the example seems to work.
Unrelated to this issue: do you plan on adding support for more type? Will a method like '() => { [Symbol.asyncIterator](): AsyncGenerator<{ hostname: string; addresses: string[]; }, void, unknown>; }'be supported?

Hi, I am definitely open to add abstractions. Unfortunately I am not sure if I understand your example/method correctly. Would you mind adding a little bit more context (what is the goal?) or an example to it? Thanks a lot!

If methods could return async-iterators this would allow for things like live updated news or messaging feeds. Ideally, it would support both iterators of json-objects as well as iterators of Uint8Arrays for efficient binary applications.

In this folder are the compiled files. Only the https.js file supports legacy browsers. https://github.com/timonson/gentle_rpc/tree/master/client/dist


Added method return chaining, custom matchers and a helper class “Is”.

Wow quite a bit of functionality here, thanks! :+1:
Would you mind adding a summary comment and updating your title here to describe what you've added support for ('is' support?) and some background etc.
@comic96 is on holiday at present, but i'll for sure give him a heads up when he returns to review this excellent submission!
Thanks again!

@afawcett – thanks for looking at this for me, much appreciated.  :)
I’d say this pull request has 3 main areas of change.

Method return chaining. A simple change that allows us apex peeps to call a mocked method a number of times and get different returns.

Custom matchers. Currently you mock a method by saying, when method X gets called with param Y return Z. With custom matchers you can say, when method X is called, check the param and see if it matches some custom logic. If true, return Z. Also, these matchers preserve the param you called with. Very handy for asserting that an inner private method say, called you mock with the param “Zebra” or you can get the SObject passed and assert is had certain properties set. I know you can work around this by having well structured code. But for brown field development, this is very useful!

A helper class “Is” to provide some pre built matchers. For example, Is.AnyInteger() or Is.AnyThing(). Sometimes you don’t care what got passed in. You just need to know it was called. Or what if you don’t know what’s going to get passed in? Some randomness or external method etc.

Hope this helps

@comic96 any views on this?

Cheers @DanielTempleUK. Good spot. Just fixed that now.

@afawcett and @comic96
There seems to be some interesting features here.
Any thoughts about when the PR can be reviewed and merged in??
Cheers!
cc: @cwilkinsonffdc

Hi @cwilkinsonffdc as discussed, closing this PR since the implementation style is not in keeping with the overall design goal of ApexMocks being as close to Mockito as possible.


Modularize the program

Refactor and separate the algorithms from the charting.
This is important because we do not want the charting to interfere with timing our algorithms. Charting will naturally add some miscellaneous time into our data and we want to avoid it.

Also another nice thing to modularize is the data sample creation process. This way we can create different types of data samples without coupling too much with the algorithm code.


chore: make data tables composable components

Closes #207

:tada: This PR is included in version 1.11.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Refine the thumbnail module a bit

Oops, I should have pushed this branch to my own repo. Will re-open a PR from there.


missing options for a true unattended run

When i run letsencrypt.exe (1.9.1) on a clean machine (windows 2012R2) and i haven't run the letsencrypt client on it, i'm still being asked a few questions
letsencrypt.exe --accepttos --manualhost [fqdn] --webroot c:\inetpub\wwwroot
I'm being asked for an e-mail address (should be an additional parameter --email)
i'm being asked whether i want to install the task (--installtask  ? )
i'm being asked which user the task should run  (--taskuser or the user which is running the letsencryptclient )
i'm being asked what the password for the user should be (--taskpass ?)
For this tool to truly run attended i feel that the options above should be added to the tool.

+1
I looked to this tool because it had unattended options.  Clearly this does not support unattended in its present state.

I created a pull request:
https://github.com/Lone-Coder/letsencrypt-win-simple/pull/325


Problem with WWW and non WWW

As i check and investigate, for non www working. with www not working. This is happen when you have alot of domain in 1 cpanel. Example
Primary domain - abc.com
BUT you install def.com for ssl, so the Lets Encrypted registered your def.com as def.abc.com
so www.def.com cannot be access. You only can access your SSL on www.def.abc.com
Im not sure this plugin working on subdomain or not

It happened with me also, the plugin took the internal subdomain rather then the main domain :(
I was able to install to main domain from the WHM panel GUI

Yes, it is because of when you create subdomain, cPanel will automatically add www.subdomain.maindomain.com and subdomain.maindomain.com to the system and when I api calls, both will return as valid domain.
Will add an option to select domains when you click on install certificate button, so that these types of issues can be avoided.


Disconnect token fails without user feedback

Prerequisites

Connected to a Token
Token only has channels in state settleable or settling

Steps to Reproduce

Go to http://lightclient.raiden.network
Click Connect
Click on Token
Click Disconnect Token
Click Confirm

Expected Result

Token is disconnected and I receive a confirmation
If disconnecting from Token did not work, I receive feedback why it failed

Actual Result

No feedback in UI

Additional Infos (Optional)
Console error action channelCloseFailed:

Error: channel for "0x67b0Dd5217dA3F7028e0c9463FdaFBF0181e1E0A" and "0xbdb4a827588A292354EA4e6C67492e34eEB98bB7" not found or not in 'open' or 'closing' state
at MergeMapSubscriber.eval [as project] (webpack-internal:///../raiden-ts/dist/channels/epics.js:673:19)
at MergeMapSubscriber._tryNext (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/operators/mergeMap.js:71:27)
at MergeMapSubscriber._next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/operators/mergeMap.js:61:18)
at MergeMapSubscriber.Subscriber.next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/Subscriber.js:63:18)
at WithLatestFromSubscriber._next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/operators/withLatestFrom.js:71:34)
at WithLatestFromSubscriber.Subscriber.next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/Subscriber.js:63:18)
at FilterSubscriber._next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/operators/filter.js:42:30)
at FilterSubscriber.Subscriber.next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/Subscriber.js:63:18)
at TakeWhileSubscriber.nextOrComplete (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/operators/takeWhile.js:50:25)
at TakeWhileSubscriber._next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/operators/takeWhile.js:45:14)
at TakeWhileSubscriber.Subscriber.next (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/Subscriber.js:63:18)
at Notification.observe (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/Notification.js:27:50)
at QueueAction.ObserveOnSubscriber.dispatch (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/operators/observeOn.js:48:22)
at QueueAction.AsyncAction._execute (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/scheduler/AsyncAction.js:68:18)
at QueueAction.execute (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/scheduler/QueueAction.js:31:18)
at QueueScheduler.AsyncScheduler.flush (webpack-internal:///../raiden-ts/node_modules/rxjs/_esm5/internal/scheduler/AsyncScheduler.js:47:32)

Channel Close is now gracefully handled


Create a Ruuter service to link text input with national holidays common services

[!NOTE]
This is a sub-issue of #63 and #60

AS A Product Owner
I WANT TO test if text input initiates applicable national holidays common services
SO THAT I could verify its intended functionality
Acceptance Criteria

[ ] Every endpoint of #60 is triggered by 1 specific keyword

E.g. "#prev_national_holiday" would trigger /calendar/national-holidays/previous

[ ] All #keywords are hard-coded in Ruuter DSL /calendar/national-holidays/search
[ ] Use Ruuter's conditional switch functionality to trigger applicable endpoints based on input
[ ] Based on triggering keyword, a request to an appropriate endpoint is made

DSL

[ ] Service provided via Ruuter's /calendar/national-holidays/search endpoint

Example
Request
curl localhost:8080/calendar/national-holidays/search
   -H "Content-Type: application/json"
   -d '{"keyword": "#prev_national_holiday"}'

Response
{
    "response": {
        "date": "2024-08-20",
        "name": "taasiseseisvumispäev"
    }
}

https://github.com/buerokratt/Common-Services/issues/64

Won't Do!
Issue has been solved by other technical solution


Flame not remembering settings i keep setting it up how i need it but after restart all jumbled up

Flame not remembering settings i keep setting it up how i need it but after restart all jumbled up.
I have reset it about 3 times but keeps forgetting
Docker Compose latest version in Portainer

I have the same problem. Docker on Orange pi (armbian). Latest version.

In docker, all the config is stored in the /app/data folder, in the config.json and db.sqlite, you can mount that folder as a volume to preserve the config between redeployments
Ref: https://github.com/pawelmalak/flame/blob/master/utils/loadConfig.js


wf test

@bgruening
It turns out that secrets are hidden by default to PR workflows. I deleted the login from PR WF and now it works.

Ah that makes sense. Cool thanks! Nice work! We will use that for the regular notebook as well.


SPIN performance

SPIN is really really really slow.
Investigate which cases are slow and which cases are more acceptable.

Small vs. large datasets.
complex/multiple rules vs. few/simple
multiple transactions vs single transaction
incremental

Update documentation to reflect which use cases of SPIN is slow so that users don’t build critical systems assuming it will scale.

@jeenbroekstra I think the most important thing is to document which use cases of SPIN are not recommended. So users don’t invest time and money if it won’t scale to their needs. There might be use cases where SPIN performance is acceptable compared to the complexities of developing something else, so those should be documented too. Looking at the tests I have a hunch that SPIN is best for semi large datasets and batch processing.


Adding StorageClass documentation to istio-dex installation

Resolves #1782
This PR documents setup of a default StorageClass for on-premise systems with dynamic provisioning for kfctl_istio_dex.yaml configuration based deployments.

Adds docs to check if on-premise installation has a default StorageClass with dynamic provisioning
Setup instructions for default StorageClass with dynamic provisioning
Reorganizes Troubleshooting guide and unifies them under one header

This change is

/assign @sarahmaddox @yanniszark

Preview: https://deploy-preview-1834--competent-brattain-de2d6d.netlify.com/docs/started/k8s/kfctl-istio-dex/

Thanks @krishnadurai!
/lgtm
/approve


Make pairing URI spec compliant

ah i see #105 now

the old amethyst was using it. thanks for the PR!! I will make sure this is shipped.


Added create_issue action for GitHub pack

Action name: create_issue
Parameters:

title (string)
description (string, optional)
repo (string)
user (string)
assignee (string, optional)

Updated README and increased pack version number to 0.2

Very nice. Just a few small things, I think, and then we can merge this in and plug in into the community room.


Mobile feature tabs dropdown

Background
https://github.com/user-attachments/assets/9443ccb6-d7c0-4d02-a3c3-4736f3bb0cf4
Description
I'm not proud of this code, but I'm not a fan of importing 2 Radix alternative components and hiding them based on the viewport.
I styled the tabs to be a dropdown select on mobile viewports so we don't have a duplicate state management. (And we ship less JavaScript).

Merging as we have https://github.com/kamilkisiela/graphql-hive/pull/5492 with a fix.


[DOC] Incorrect and invalid links

What's the document you plan to update? Why? Please describe
Some links on the best-practice page in different Longhorn versions are invalid (e.g., https://longhorn.io/docs/1.6.2/best-practices/):

Recurring backups: Create recurring backup jobs for mission-critical application volumes.

Some links on the same page point to the wrong version:

For applications with replication capability, periodically delete all types of snapshots.

Links should use relative paths instead of the actual HTTP URLs. For example, this. And the suggested change:
-- **Storage network**: Use a [dedicated storage network](https://longhorn.io/docs/1.6.0/advanced-resources/deploy/storage-network/#setting-storage-network) to improve IO performance and stability.
+- **Storage network**: Use a [dedicated storage network](../advanced-resources/deploy/storage-network/#setting-storage-network) to improve IO performance and stability.

We should review all documents and correct the links.
Additional context

None

cc @longhorn/doc


Support internal non-pointer references

According to 8.3.2, $ref might not be a JSON pointer, eg:
   {
       "$id": "http://example.net/root.json",
       "items": {
           "type": "array",
           "items": { "$ref": "#item" }
       },
       "definitions": {
           "single": {
               "$id": "#item",
               "type": "object",
               "additionalProperties": { "$ref": "other.json" }
           }
       }
   }

Currently, the schema viewer errors with Invalid JSON pointer. (it's trying to resolve #item as a JSON pointer, while in fact it's just an internal reference, pointing to http://example.net/root.json#item)

Hi @madbence ,
Two quick things:

There is no definition for #item only for #items (missing an s)
The other.json reference does not look valid.

This tool should support any fully-internal references. 😄 Let me know if that still does not work.

@robertmassaioli I took the example from the RFC, so I think it's valid (sure, the other.json reference is external, which isn't supported, and that is fine)
The #item reference in #/items/items/$ref is a valid reference (to #/definitions/single), as described in the RFC:
   When an implementation encounters the <#/definitions/single> schema,
   it resolves the "$id" URI reference against the current base URI to
   form <http://example.net/root.json#item>.

   When an implementation then looks inside the <#/items> schema, it
   encounters the <#item> reference, and resolves this to
   <http://example.net/root.json#item>, which it has seen defined in
   this same document and can therefore use automatically.

   When an implementation encounters the reference to "other.json", it
   resolves this to <http://example.net/other.json>, which is not
   defined in this document.  If a schema with that identifier has
   otherwise been supplied to the implementation, it can also be used
   automatically.

A more complex example that I was trying to examine: https://raw.githubusercontent.com/usnistgov/OSCAL/main/json/schema/oscal_assessment-results_schema.json
The following change kinda resolved the issue (yes, it's an ugly hack, and doesn't care about the base URI, or nested definitions):
--- a/src/lookup/index.ts
+++ b/src/lookup/index.ts
@@ -62,7 +62,10 @@ export class InternalLookup implements Lookup {
       return undefined;
     }

-    const result = pointerGet(this.schema, ref.slice(1));
+    if (ref === '#') return this.getSchema(this.schema);
+
+    const result = ref.includes('/') ? pointerGet(this.schema, ref.slice(1)) : Object.values((this.schema as any).definitions).find(a => a['$id'] == ref) as any;

     if (result === undefined) {
       return undefined;

Okay, I've had a sit down and read through the schema. Essentially, the "$id": "#<identifier>" format overrides standard JSON Pointer logic and becomes the first lookup for within the file.
That's fairly annoying but not impossible to replicate, we would just need to generate a map when we first load the schema for usage in follow-up references.


Bzlmod CI

Another extraction from #238.
Obviously there isn't much Bzlmod going on on main right now, but we can already add the matrix dimension for it.
Note that the "required" checks in main branch protection rules have to be updated for this to land

IMO, this should be a part of the PR that introduces bzlmod.


Disable interrupts while doing flash_op, explicit_buy, and chain_image

For flash_op and explicit_buy, disable interrupts if running a flash binary. This prevents calling interrupt routines in flash while the flash is being accessed directly (eg when explicit_buy does a flash erase), which would cause a bus fault. I haven't added the same to the other flash functions, because those are generally lower-level, whereas flash_op is a higher-level function so it's nice to be able to call it without additional configuration.
For chain_image, always disable interrupts before chaining, to prevent interrupt routines interrupting the chaining.

You should use this
/**
 * \brief Execute a function with IRQs disabled and with the other core also not executing/reading flash
 * \ingroup pico_flash
 *
 * \param func the function to call
 * \param param the parameter to pass to the function
 * \param enter_exit_timeout_ms the timeout for each of the enter/exit phases when coordinating with the other core
 *
 * \return PICO_OK on success (the function will have been called).
 *         PICO_ERROR_TIMEOUT on timeout (the function may have been called).
 *         PICO_ERROR_NOT_PERMITTED if safe execution is not possible (the function will not have been called).
 *         PICO_ERROR_INSUFFICIENT_RESOURCES if the method fails due to dynamic resource exhaustion (the function will not have been called)
 * \note if \ref PICO_FLASH_ASSERT_ON_UNSAFE is 1, this function will assert in debug mode vs returning
 *       PICO_ERROR_NOT_PERMITTED
 */
int flash_safe_execute(void (*func)(void *), void *param, uint32_t enter_exit_timeout_ms);

Added - but this does now add a dependency on pico_flash for all binaries that use pico_bootrom, which I think gets included in pico_stdlib (ie all binaries now depend on pico_flash)

I think that is probably OK (it doesn't necessarily pull in that much by default - you could check) ... or perhaps it makes more sense to move the bootrom wrapper funcs for this into flash.h - perhaps i'm leaning towards the latter

I think that the explicit_buy wrapper shouldn't be moved into flash.h - it's just a rom function that happens to touch flash, and therefore needs the flash_safe stuff. Probably fine as is, I checked that pico_flash doesn't seem to add much extra, so it's fine to be included

We either need to
a) make the struct.typedef and helper function names a bit more scoped or outline this stuff into the C file
b) the problem with C file is that we open ourselves up to problems with executing code from flash - so probably leave them as inline but tack a rom_helper_ or similar on the front.

I've inlined the helpers, and renamed them (eg rom_helper_flash_op with rom_helper_flash_op_params_t)


feat: add loadingStatusErrorMessage to state

Probably naive first attempt to expose error message in case of rejected script load

Great work @dtjones404! 💯


How can we help?
I would like someone else to build the manifest.
Please read and ensure the following

[X] The installer meets the above requirements

Please provide the following information
Download Page Url: https://sourceforge.net/projects/syncterm/files/syncterm/
Publisher: Stephen James Hurd
Package Name: SyncTERM
Description: A cross-platform ANSI-BBS terminal designed to connect to remote BBSs via telnet, rlogin, or SSH. Supports ANSI music and the IBM charset when possible.
Package Version: 1.1
Installer URL: https://sourceforge.net/projects/syncterm/files/syncterm/syncterm-1.1/SyncTERM-1.1-setup.exe

@AsciiWolf

It will publish in #113259


Style : Add responsiveness to "Opensource Programs" webpage

Category

[ ] Documentation
[ ] Resource Addition
[ ] Codebase
[x] User Interface
[ ] Feature Request

Description
The "Opensource Programs" webpage is not responsive, all the text divs shift to the left when the screen size is shrunk

You're assigned.

Solved in PR #341


Mumble Client NullReferenceException in MumbleClient.AddDecodingBuffer()

Hi,
Thanks so much for making this client!  I have brought the latest code from this repo into a brand new Unity project (using version 2021.2.13f1) and have the following error when connecting to a local murmur server on same machine:

The config of my MumbleTester and MumbleMic scripts are as follows:

The client initially connects successfully to the server, but we're unable to send any audio (we use the official Mumble Desktop app to verify this).
The error above shows up almost immediately on startup and then not too long after we get disconnected from the server without the mumble client even noticing that we're disconnected.  To be sure, I went back to an older Unity version where I'm confident this client worked back in 2021, but now it doesn't even work in that version.
What could be causing this?
Thanks so much for your help!
Cheers,
Danrae

Hmm, any chance that you could try with a non-localhost murmur server?

Hmm, any chance that you could try with a non-localhost murmur server?

Thanks for the quick response - yes, I tried with a non-localhost (remote) murmur server and saw the same thing.  I've also tested that the servers (local & remote) can receive connections from the official mumble clients.
Also, in both cases (local vs. remote server), I see this error when I exit in Unity:

Cheers,
Danrae

It looks like AllUsers ends up populated with a null entry. Could you add a check in MumbleClient.cs ln 252 for if newUserState is null? If so, maybe send a screenshot of a log so that we can see the stack trace

I set a breakpoint in the debugger and could see that newUserState is never null (it actually contains the info for each user on the server as expected too) and line 252 in MumbleClient.cs executes as expected.
Something else interesting is, maybe less than a minute after the client gets disconnected from the server, I see this new warning about a UDP error + switching to TCP show up:

I enabled the debug logs in Unity console for you and I believe the stack trace is showing for all the errors in the previous comments.  The stack trace in this image is for the new 'switching to TCP' warning I noticed.

Oh wait, it might be that you don't have EventProcessor in the scene. Can you add that script to the same object as MumbleClient?

Oh wait, it might be that you don't have EventProcessor in the scene. Can you add that script to the same object as MumbleClient?

OMG that was it haha!  I'm able to connect and chat on the server now!
The latter error related that was happening when I exited the app was fixed when I rolled back to the following commit: 200cf22784b908a9cea808b5a201330021a40797
Thanks so much for all your help!  And for this repo - it's really an incredible contribution you've made to the open-source community.  I added a 'star' in case that helps you somehow haha.
Best regards,
Danrae

Thank you for the kind words! Means a lot to me.
I'm going to leave this open, there should be a better error log for when the event processor is not in. If you wanted to do a PR for that, would be helpful!

For sure!  B.c. it's a work project, I need to get an approval, but I'll drop a patch here either way (maybe from my personal account, worst case).  Thanks again!


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.13.6",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f5ef2fe05d386995b951476ffc8d6a6023888d99"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "f5ef2fe05d386995b951476ffc8d6a6023888d99",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "btrfs: fix lock inversion problem when doing qgroup extent tracing\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.13.6 by commit f5ef2fe05d386995b951476ffc8d6a6023888d99. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001175


When using Vue and/or vuetify with astro style is not being read from content

Describe the bug
Result is missing a lot of CSS
To Reproduce
Use package with @astro/vuejs
Expected behavior
Do not purge styles that are declared in .vue files
Additional context
I have fixed this locally with this code:
import { PurgeCSS } from 'purgecss';
import { writeFile } from 'node:fs/promises';
import { fileURLToPath } from 'node:url';
function handleWindowsPath(outputPath) {
if (process.platform !== 'win32') return outputPath;
if (outputPath.endsWith('\')) {
outputPath = outputPath.substring(0, outputPath.length - 1);
}
outputPath = outputPath.replaceAll('\', '/');
return outputPath;
}
function src_default(options = {}) {
return {
name: 'astro-purgecss',
hooks: {
'astro:build:done': async ({ dir }) => {
const outDir = handleWindowsPath(fileURLToPath(dir));
const purged = await new PurgeCSS().purge({
...options,
content: [
${outDir}/**/*.html,
${outDir}/**/*.astro,
${outDir}/**/*.js
],
css: [${outDir}/**/*.css],
defaultExtractor(content) {
const contentWithoutStyleBlocks = content.replace(
/<style[^]+?</style>/gi,
''
);
        return (
          contentWithoutStyleBlocks.match(
            /[A-Za-z0-9-_/:]*[A-Za-z0-9-_/]+/g
          ) || []
        );
      }
    });
    await Promise.all(
      purged
        .filter(({ file }) =>
          file == null ? void 0 : file.endsWith('.css')
        )
        .map(async ({ css, file }) => await writeFile(file, css))
    );
  }
}

};
}
export { src_default as default };

Should I make a pull request to fix this issue or do you want to handle this yourself?

The fix is in my repository from my website https://github.com/thebetar/VonkProgramming

I have created a pull request with the solution https://github.com/codiume/orbit/pull/175

sorry for the late reply, I have merged your PR. Thanks :1st_place_medal:


eliminate openly accessible endpoints

the goal of the wallet extension is to provide wallet services to third-party pages. however, it is not necessary for the wallet to provide analyzable surfaces to all third-party pages.
currently, the extension attempts no authentication of origins, and all attempted connections receive service. the extension should not acknowledge unpermissioned origins in any way, not even an explicit refusal.
currently, the extension provides conveniences for detection and status indication to the webapp. the extension should not manifest any web-accessible resources, or any detection or status endpoints.
inferring presence, readiness, and status is the responsibility of the webapp. presence and readiness are easily evidenced by acknowledgement of a specced RPC request. any status that matters will likewise be present in the result of an appropriate RPC request.

https://github.com/penumbra-zone/web/blame/48985141b30da200c4c96a6a67139e9da9029839/apps/extension/public/manifest.json#L22-L27
https://github.com/penumbra-zone/web/blob/48985141b30da200c4c96a6a67139e9da9029839/apps/webapp/src/fetchers/is-connected.ts

#73 "connected sites" list provides origin authentication

Web apps may assume the extension is not connected, until an attempted request is acknowledged by the extension with a response.
Web apps should not be concerned with their own authorization, the extension manages authorization.
A web app should by default display instructions directing the user to install the extension and provide it permission. When it receives responses from the extension, it may reliably infer it is connected, and operate accordingly. A web app with specific knowledge of the particular user (session cookie, login, etc) may choose to simplify somewhat or make different assumptions.
I am of the opinion that all permission should be user-initiated, by a manual click on the extension icon. But it is certainly possible for the extension to activate the popup upon any connection attempt or request from a page, which would make permission effectively app-initiated - very much like webcam or mic permission currently operates. This wouldn't require any dedicated rpc message type, as the extension is easily able to identify attempted connections from an unknown origin.

The majority of crypto wallets accomplish this by using content-scripts to inject something onto the window object. If say window.metamask is present, it knows the user has installed it. If not, it prompts the user to go the the chrome web store.

I believe this is a bad choice, because such a technique provides affirmative confirmation to every page that a wallet extension is present.
Consider the page adversarial until the user manually approves permission.

I think there may be a differing vision on what the userflow for authentication is. The industry-wide way it works typically looks like this:

The extension is not installed

The top right hand corner of the screen has a Connect button that when pressed, prompts users to install the extension

The extension is installed, but the user has not authorized the connection

The top right hand corner has a Connect button that when pressed, triggers an approval popup
If approved, the Connect button is replaced with the user's account address (or some connected indicator)

The extension is installed and the user has already authorized

Displays user's account address (or some connected indicator)

⬆ These are the user flows we need to support.

Web apps may assume the extension is not connected, until an attempted request is acknowledged by the extension

In the normal http world, a fetch would return a 403 Forbidden response and the UI could display the right thing. However, what is that for our case? At the moment, if we issue a message without an existing recipient, it will "await" forever. Without any support, the best case scenario is for us to put a kind of timeout on the message. This would be kinda unfortunate that the UI would have loading screens everywhere for X seconds. The injected code or exposed txt object allows the web app to know immediately whether it's installed or not.

Web apps should not be concerned with their own authorization

To support the user flow above, it does need to be concerned about this.

This 'negative' presence can by default trigger display of instructions

What specifically is a "negative" presence? A timeout?

When a web app receives responses from the extension

In this case, do you suggest the connect button issue a random grpc query to see if it's connected? Why not just expose a ping grpc method or, even better, isConnected()?

I am of the opinion that all permission should be user-initiated, by a manual click on the extension icon

In your vision, do you see the user going to the web app, seeing there is no data, and proactively clicking the extension icon to authenticate?

the extension to activate the popup upon a connection attempt

In the industry, it's a bit 50/50 on this behavior. Some web apps do this, but some users (like me) find this annoying. That you land on a page and it throws a popup immediately. Having a Connect button tends to be more common and less invasive. Given we are a privacy chain, I think it's best if users themselves trigger authentication events. Otherwise, a bad web app may trigger a popup, get an approval, and doxx that user's addresses because the user just clicked approve on a random popup without context.


Fail if running outside of netty be default

Gateway only supports netty at the moment, see #145.
Gateway should fail if running in tomcat, jetty or undertow until the above issue is resolved.

This should not preclude tests using wiremock.


-reverse input channel flag needed

Hello
When converting to xml wondering whether reverse input channel is needed?
In my experience, tf models do require this.
Thanks

Hi, @GotG
Darknet:https://github.com/pjreddie/darknet/issues/427
Tensorflow(my project is based on mystics123 Tensorflow YOLOV3):https://github.com/mystic123/tensorflow-yolo-v3/issues/2
OpenVINOYOLOV3:https://docs.openvinotoolkit.org/latest/openvino_docs_MO_DG_prepare_model_convert_model_tf_specific_Convert_YOLO_From_Tensorflow.html
`python3 mo_tf.py
--input_model /path/to/yolo_v3.pb
--tensorflow_use_custom_operations_config $MO_ROOT/extensions/front/tf/yolo_v3.json
--batch
Since YOLOV3 ,OpenVINO didn't use --reverse_input_channels. I checked object_detection_demo_yolov3_async.py and i didn't found this demo converts BGR(OpenCV) to RGB(darknet and tf)
So i did some tests:
YOLOV4 original:

YOLOV4 channels reversed:

YOLOV4 tiny original:

YOLOV4 tiny  channels reversed:

I also do some video tests,the results are the same. Using --reverse_input_channels will be better
So i agree with you. My conclusion is that this may be a mistake made by OpenVINO since YOLOv3
Thanks a lot!!

Thanks for checking. My results are also very close when tested on yolov3. I did mention this at some point on their forums.

Great job!!
Thanks a lot!

Well done with your repo! Very useful!
Do you happen to know for tiny yolo v4 which function prevents it from working in OpenVINO 20.01 or .02? Thanks

yolov4 tiny need this :
[route]
layers=-1
groups=2
group_id=1
In Tensorflow,we could use https://github.com/TNTWEN/OpenVINO-YOLOV4/blob/534cca38d1e3bf95dce98daa216a57f62a2f83ce/yolo_v4_tiny.py#L21
or https://github.com/TNTWEN/OpenVINO-YOLOV4/blob/534cca38d1e3bf95dce98daa216a57f62a2f83ce/yolo_v4_tiny.py#L22
But they are not supported by OpenVINO before 2020R4(In fact, I  used the 2019 version before ,so the exact version which began to support v4 tiny may not  be accurate)
Now OpenVINO 2020R4 supports the second operation but it still doesn't support the first operation.But anyway, that's enough for us to implement  OpenVINO v4tiny


chore: Create LICENSE

Generated from https://github.com/nartc/ngxtension-platform/community/license/new?branch=main&filename=LICENSE&template=mit
I didn't notice this was missing until I needed to share the license link with our Legal team 😅

@all-contributors please add @ajitzero for doc


Questions about the 8 bit display

Hello, I am confused about a few things.
What exactly is EN? It says to solder a "blob" between EN and VCC, on the silkscreen it also says "short power on". I don't know what that means.
What is the driver IC? I think it might be the PT6302 but I'm not sure.
I have tried looking for the original author to contact but found nothing about him.
Thanks in advance.

EN enables the display, taking EN high, I.e shorting it to VCC enables the display however it could also be driven from a microcontrollers gpio for example. If you want the display always on you can just solder j1 closed which will take EN high.
Not sure at this stage what the driver ic is, I have ordered a few variations of this display to play with and will let you know once they arrive.

Thank you for your answer. I actually have ordered the display and received it but I haven't had the time to test it yet.
From what I found the controller IC is the PT6302.
Here is everything I found about the display:
https://github.com/3KUdelta/Futaba-VFD-16bit_ESP32/tree/main
https://github.com/hexesdesu/ESP32VFDClock
https://github.com/sfxfs/ESP32-VFD-8DM-Arduino
https://github.com/Reboot93/VFD-desktop-clock-micropython
https://community.dfrobot.com/makelog-310356.html
https://timewitharduino.blogspot.com/2021/04/
https://blog.csdn.net/sxhexin/article/details/107284089
https://github.com/3KUdelta/Futaba-VFD-16bit_ESP32/blob/main/documents/VFD屏手册.pdf
https://pdf1.alldatasheet.com/datasheet-pdf/view/391603/PTC/PT6302.html
I'll keep this open for when your units arrive.


All entries in the CMS disappeared

Describe the bug
All entries and pages have disappeared from the CMS. Not sure when this happened, but can confirm the last time everything was working was in January.
To Reproduce
All the entries have disappeared. No content shown in the CMS.
Screenshots

Netlify CMS version: 2.10.192
Git provider: GitLab
Backend Config
backend:
  name: git-gateway
  branch: master
media_folder: "src/img/uploads"
public_folder: "img/uploads"
collections:
  - label: "Pages"
    name: "pages"
    files:
      - label: "Home"
        name: "home"
        file: "src/pages/homepage.md"
        extension: "md"
        fields:
          - { label: "Title", name: "title", widget: "string" }
          - { label: "Intro Text", name: "intro", widget: "markdown" }
          - label: "Featured Images"
            label_singular: "Featured Image"
            name: "featuredImages"
            widget: "list"
            field:
              {
                label: "Image",
                name: "image",
                widget: image,
                hint: "2000 x 1459px",
              }
            max: 3
            min: 3
          - {
              label: "About Section Title",
              name: "aboutTitle",
              widget: "string",
            }
          - label: "Portfolio Items"
            name: "portfolioItems"
            widget: list
            allow_add: false
            fields:
              - { label: "Title", name: "title", widget: string }
              - label: "Images"
                name: "images"
                widget: list
                allow_add: false
                min: 2
                max: 2
                field:
                  {
                    label: "Image",
                    name: "image",
                    widget: image,
                    hint: "900 x 600px",
                  }
              - { label: "URL", name: "url", widget: string }
            max: 3
            min: 3
      - label: "About"
        name: "about"
        file: "src/pages/about.md"
        extension: "md"
        fields:
          - { label: "Title", name: "title", widget: "string" }
          - { label: "Intro Text", name: "intro", widget: "markdown" }
          - { label: "Header Image", name: "headerImage", widget: "image" }
          - { label: "Content", name: "content", widget: "markdown" }
          - { label: "Profile Image", name: "profileImage", widget: "image" }
          - { label: "Inline Image", name: "inlineImage", widget: "image" }
      - label: "Portfolio"
        name: "portfolio"
        file: "src/pages/portfolio.md"
        extension: "md"
        fields:
          - { label: "Title", name: "title", widget: "string" }
          - { label: "Intro Text", name: "intro", widget: "markdown" }
          - { label: "Header Image", name: "headerImage", widget: "image" }
          - label: "Categories"
            name: "categories"
            widget: "list"
            max: 3
            min: 3
            allow_add: false
            fields:
              - {
                  label: "Category Title",
                  name: "catTitle",
                  widget: string,
                  required: true,
                }
              - {
                  label: "Category Description",
                  name: "catDescription",
                  widget: string,
                  required: true,
                }
              - { label: "Image", name: "image", widget: image }
      - label: "Wedding"
        name: "wedding"
        file: "src/pages/wedding.md"
        extension: "md"
        fields:
          - { label: "Title", name: "title", widget: "string" }
          - { label: "Intro Text", name: "intro", widget: "markdown" }
          - label: "Images"
            label_singular: "Image"
            name: "images"
            widget: "list"
            fields:
              - {
                  label: "Title",
                  name: "title",
                  widget: string,
                  required: false,
                }
              - { label: "Image", name: "image", widget: image }
      - label: "Music"
        name: "music"
        file: "src/pages/music.md"
        extension: "md"
        fields:
          - { label: "Title", name: "title", widget: "string" }
          - { label: "Intro Text", name: "intro", widget: "markdown" }
          - label: "Images"
            label_singular: "Image"
            name: "images"
            widget: "list"
            fields:
              - {
                  label: "Title",
                  name: "title",
                  widget: string,
                  required: false,
                }
              - { label: "Image", name: "image", widget: image }
      - label: "Testimonials"
        name: "testimonials"
        file: "src/pages/testimonials.md"
        extension: "md"
        fields:
          - { label: "Title", name: "title", widget: "string" }
          - { label: "Intro Text", name: "intro", widget: "markdown" }
          - { label: "Header Image", name: "headerImage", widget: "image" }
      - label: "Contact"
        name: "contact"
        file: "src/pages/contact.md"
        extension: "md"
        fields:
          - { label: "Title", name: "title", widget: "string" }
          - { label: "Intro Text", name: "intro", widget: "markdown" }
          - { label: "Header Image", name: "headerImage", widget: "image" }

Found this issue in search of a fix, not sure if it's relevant: https://github.com/netlify/netlify-cms/issues/2896

Hi @thchristensen, please fill out all the fields in the issue template. The information you provided is not enough to debug the problem.
I'm closing the issue for now. Once you add the missing information, I can open it again.


AssertThat always ignored

Hello,
I'm having an issue making AssertThat work for me.  I want to force the user to select a test result outcome from  when PregnancyTestRequired = true - however it seems to ignore it and continue to post the data to my controller.
Here is a snippet of my view model...
`[DisplayName("Pregnancy Test required")]
public bool PregnancyTestRequired { get; set; }
    [AssertThat("PregnancyTestRequired == true && PregnancyTestResult > 0", ErrorMessage = "Required")]
    [DisplayName("Pregnancy Test Result")]
    public int PregnancyTestResult { get; set; }`

I'm using version 2.9.6 Any idea what I am doing wrong?

Have you registered adapter in Global.asax => Application_Start()?
https://github.com/jwaliszko/ExpressiveAnnotations#what-about-the-support-of-aspnet-mvc-client-side-validation

Have you registered adapter in Global.asax?
https://github.com/jwaliszko/ExpressiveAnnotations#what-about-the-support-of-aspnet-mvc-client-side-validation


fix: refactor the Download method to use client instead of http.Get

The title is quite self-explanatory.

LGTM. Thanks!


is it possible to make 'switchbuf' stick on specific winid?

Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
current default value of option switchbuf or its new added value 'uselast' -their behavior actually looks a bit magic,
// since perhaps it was not a 'quickfix' commands issued..
for now i think it's not very certain sure which window it would jump to..
Describe the solution you'd like
how about adding a new value e.g 'tgtwinid:123'

if winid '123' not existed, then raise err.
if found winid '123', then stick on it.

Describe alternatives you've considered
n/a
Additional context
n/a

'switchbuf' is (at the moment) a global option; it is a comma-separted string, and its default value is the empty string, meaning that every window-splitting command wil indeed open a new split window.
When coming from a non-quickfix window, only the first two possible entries are taken into account: usetab, useopen without usetab, or neither.
The other values come into play when a quickfix command is issued. IIUC, split, vsplit and newtab will open a new window for the source files opened by a quickfix command and (still IIUC) go back to the previous editfile when that source file is closed. I suppose that using :set swb=useopen,split,uselast can be used to reuse an existing window when using :new etc. for an existing edit file, to open source files opened by :helpgrep, :vimgrep, :make etc. in a new window, and load sucessive source files in a single window. CAUTION: This is how I read the help for switchbuf, the quickfix command I use most is :helpgrep and help files replace each other in a single window even with the default settings, so I may be in error.
In any case, splitting commands (:new, :split, vsplit etc.) take as argument (when one is used) a filename, not a window ID. Window IDs are not portable from one session to another, a small experiment I just did seems to indicate that they start at 1000, but in any case (a) it cannot be guaranteed that the same buffer name will correspond to the same window ID after quitting and restarting Vim; (b) after closing a window I suppose that its ID becomes forever unavailable in that Vim session; and (c) IMHO it would be hugely impractical, even dangerous, to force all split commands to go to the same target window regardless of the filename given as argument.

No I don't have another workaround — or on second thought, maybe I do, see below. For :helpgrep reusing the already present help window is OK for me. For :vimgrep I neither want my existing windows to be obliterated nor the grepping operation to open 50 new windows if it looks into that many files, usually I open an empty window just before I start that command but I'll have to ponder possible better ways to do it.
Maybe opening an empty window just before running a quickfix command other than :helpgrep is the workaround you need: AFAIK it will open all files where there is a match into that formerly empty window. I don't open the quickfix window itself — I go directly to the place being matched.
I also define the following mappings in my vimrc:
  if has('quickfix')
    map  <F2>    :cnext<CR>
    map  <S-F2>  :cprev<CR>
  endif

and if I had had additional F keys not yet in use I would also have mapped :cnfile, :cpfile, :cfirst and clast.
Best regards,
Tony.

ahaha... i see.. yea, i agree about 70~80% it is working as expected as long as you knew the trick of these..
but the problem is you may move the cursor to another window (then 'uselast' is broken'), and/or you just issued a 'enter' which not a quickfix command, then it maybe broken.. or 'netrw' was the last/neared window or somehow, then it maybe broken..
// so if wanted to be 100% sure, then that 'switchbuf' option value can be set to/with a specific winid looks was a choice.
// but well, if it had some cost/outage or something i didnot image, then let it be, so far most situation it can be working....

this can stick on pvw actually, so let it be. closing..


Add "check for updates" functionality

One drawback to desktop applications is that they can become out of date. It would be good for OVE electron to add functionality that enables the user to check for updates (and automate the updating process), alert the user that there are updates available (and point them to where they can get them), automatically update the software etc. Some implementation thereof would be good. If this functionality already exists, made it more apparent to the user that it is doing this on their behalf, e.g. under Help menu indicate that the version installed is up to date or not. Not trying to be prescriptive here of the solution, but just to make sure that this issue is considered and responded to in some form when possible.

Plan:

[ ] add a simple component to the ove-electron editor to check the current version against the latest released ove-electron version and display a warning if not fully up to date.


Improved list results - Take 2

Almost the same as #33. Just changed the version and detailed scores sizes. Also changed the detailed scores color and added an hover effect.

@atduarte squashed! Merge it!


stop_http_server()

Hi :)
Is there a possibility to stop the http_server?
The port can be changed in my application. I want to close the old endpoint and start a new one.
A workaround would be appreciated if there is no possibility to stop the http_server within the prometheus/client_python.
I haven't found a solution here or on stackoverflow that would work.
Thank you!

Hello, this is not possible with start_http_server today, but would be possible if/when https://github.com/prometheus/client_python/issues/883 is implemented.
Typically if you need more advanced control of the http_server we recommend that you manage the server yourself, see the examples of WSGI/ASGI or Flask in the readme: https://github.com/prometheus/client_python#exporting
I am going to close this as a duplicate of #883, feel free to follow along there if you don't want to manage the server yourself.


Error in ./startFabric.sh

the startFabric.sh script has the following errors:
Create the channel
docker exec peer0.org1.example.com peer channel create -o orderer.example.com:70
50 -c composerchannel -f /etc/hyperledger/configtx/composer-channel.tx
Error response from daemon: Container 8a2603a405ed625b689f960bc81afa3269b54664ff
f15a587dc12cac6007c21c is not running

@mna2016 appears to be issue with docker container.  Have you tried removing docker containers and then running the script?

I have the same issue. I run it as user from my own user folder.
command
docker exec peer0.org1.example.com peer channel create -o orderer.example.com:7050 -c composerchannel -f /etc/hyperledger/configtx/composer-channel.tx
error
Error response from daemon: Container 2f57fa8ac686886b42a746e606028e11e4c89eb64d50ff9193fe1bff8215a494 is not running
Setup
Ubuntu 16.04 lts. Softlayer VM

I have the same issue.
Following the steps from the blockchain developer-tutorial at https://hyperledger.github.io/composer/latest/tutorials/developer-tutorial.html
My startFabric.sh fails with
Error response from daemon: Container d2a4df08857333ddc46026fe26376af58116af8d39af2823e222aeebedddb648 is not running
ibm@pradi0514075029:~/fabric-dev-servers$ docker ps -a
CONTAINER ID        IMAGE                                     COMMAND                  CREATED             STATUS                         PORTS                                        NAMES
d2a4df088573        hyperledger/fabric-peer:x86_64-1.1.0      "peer node start"        About an hour ago Exited (2) About an hour ago                                                peer0.org1.example.com
0f690b2a6629        hyperledger/fabric-couchdb:x86_64-0.4.6   "tini -- /docker-ent…"   About an hour ago   Up About an hour               4369/tcp, 9100/tcp, <IP_ADDRESS>:5984->5984/tcp   couchdb
8cde7086fd80        hyperledger/fabric-ca:x86_64-1.1.0        "sh -c 'fabric-ca-se…"   About an hour ago   Up About an hour               <IP_ADDRESS>:7054->7054/tcp                       ca.org1.example.com
4e9dd5b6d33f        hyperledger/fabric-orderer:x86_64-1.1.0   "orderer"                About an hour ago   Up About an hour               <IP_ADDRESS>:7050->7050/tcp                       orderer.example.com
It seems to day that my peer container has exited.
I am on Ubuntu 16.04.3 LTS (xenial).

Hi,
Has anyone found a solution to this problem when running ./startFabric.sh, getting the error:
Error response from daemon: Container 43f2bcdc71066896bec4189728375977ec5e1cfe77472096a6fab22be8527cfb is not running

Can you mention the exact steps you follow to re-create the error.
On Mon, 25 Feb 2019 19:26 vanishtachangea<EMAIL_ADDRESS>wrote:

Hi,
Has anyone found a solution to this problem when running ./startFabric.sh,
getting the error:
Error response from daemon: Container
43f2bcdc71066896bec4189728375977ec5e1cfe77472096a6fab22be8527cfb is not
running
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/IBM/Decentralized-Energy-Composer/issues/7#issuecomment-467019877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALuN-0d_ugXQqt-QlBejO0RMebMff-B1ks5vQ-uYgaJpZM4PVGXs
.

I have reinstalled the CLI tool, the hyperledger fabric as per :+1:
https://hyperledger.github.io/composer/latest/installing/installing-prereqs
https://hyperledger.github.io/composer/latest/installing/development-tools
I deleted the containers and try to run ./startFabric.sh, I'm getting this error. But I started getting the error before itself, that's why I did the uninstall and reinstall when nothing was fixing it.  Now, I'm checking the docker side..
If anyone has been able to fix this, please let me know.

Hi! When running startFabric.sh, I had the same problem with a container that was not running. For example :
Error response from daemon: Container 43f2bcdc71066896bec4189728375977ec5e1cfe77472096a6fab22be8527cfb is not running
To SOLVE this : in the file fabric-tools/hlfv12/ (because images was already installed, otherwise I think hlfv1 will run startFabric.sh) I comment the following line in the startFabric.sh script :
docker-compose -f "${DOCKER_FILE}" down
so that we keep the dockers already installed when running again startFabric.sh (and so the following command won't be useless) , then I start the not-running container :
docker start 43f2bcdc71066896bec4189728375977ec5e1cfe77472096a6fab22be8527cfb
and finally, run ./startFabric.sh and all goes right since we have all dockers we need.
Hope it will do the trick for you

Thanks @thib00  God Bless you! It worked!

Hi! When running startFabric.sh, I had the same problem with a container that was not running. For example :
Error response from daemon: Container 43f2bcdc71066896bec4189728375977ec5e1cfe77472096a6fab22be8527cfb is not running
To SOLVE this : in the file fabric-tools/hlfv12/ (because images was already installed, otherwise I think hlfv1 will run startFabric.sh) I comment the following line in the startFabric.sh script :
docker-compose -f "${DOCKER_FILE}" down
so that we keep the dockers already installed when running again startFabric.sh (and so the following command won't be useless) , then I start the not-running container :
docker start 43f2bcdc71066896bec4189728375977ec5e1cfe77472096a6fab22be8527cfb
and finally, run ./startFabric.sh and all goes right since we have all dockers we need.
Hope it will do the trick for you

I had the same issue and I tried that. When I run docker start <contianerID> it works and the container goes up, but a few seconds later, the container goes down again, I don't know how nor why. Does someone have any idea why this happens and how to solve it?


Partial of a vmap function

Description
For the following example code:
# Example usage
import jax
import jax.numpy as jnp
from jax import vmap

@partial(vmap, in_axes=(None, 0))
def f(y, x):
    return x + y
x_var = jnp.arange(10)

func_ = partial(f, x=x_var)
func_(1)

The following error is raised:
ValueError: vmap in_axes must be an int, None, or a tuple of entries corresponding to the positional arguments passed to the function, but got len(in_axes)=2, len(args)=1

System info (python version, jaxlib version, accelerator, etc.)
python 3 (ipykernel)
jax 0.4.30

Agreed with @vfdev-5: this is working as documented, though I understand the behavior around vmap and keywords can be confusing. For what it's worth, this has nothing to do with partial: you can get the same error when calling the function directly with a keyword argument:
f(1, x=x_var)  # ValueError

We've talked about changing the way that vmap handles explicit keyword arguments, but this would be a large breakage in backward compatibility, so it's probably not something we'll change.


Homogenise timestamp metadata in L1 files

One more update may need for the "time_coverage_end" global attribute, it should have the same format as "time_coverage_start".
:time_coverage_start = "2023-10-24 19:34:59";
:time_coverage_end = "24-10-2023 19:57:11";

Also check others for consistency

707860a


Add support for native mouse cursors in pyglet

To test this, open the demo dialog,
Expand 'Inputs, Navigation & Focus' (last item)
Expand the 'Mouse cursors' (last item)
Hover over the lines describing the cursors.
Only tested on Windows 10.

Coverage decreased (-0.3%) to 55.613% when pulling f0115f77739c2b68139ea5a35ac18cf33828611b on learn-more:add_cursor_hand into 480b4de8ab82adaa2cd310100330b41f40274bcc on swistakm:master.

@swistakm Would you have some time to take a look at this?

I was just trying to change the mouse cursor and can confirm it does not work with the latest PIP build. This integration seems to work fine! I also noticed that the MOUSE_CURSOR_HAND is missing as a constant, was this added in another commit because this "fix" does not include it.

I was just trying to change the mouse cursor and can confirm it does not work with the latest PIP build. This integration seems to work fine! I also noticed that the MOUSE_CURSOR_HAND is missing as a constant, was this added in another commit because this "fix" does not include it.

This fix is based on the current pyimgui version, which includes an old imgui.
This hand cursor was added in a later imgui version.


Add some basic usage examples for the README

Need to add some basic examples for highly used methods like

GetInfo
GetBlock
GetTableRows

Added more examples to readme
https://github.com/GetScatter/eos-sharp/commit/91bde31325b0cdeedef54d41575cba60bdba37bd
Check it out if there is some info wrong or missing.


fix: mark txs as committed

While debugging #360 we found a way to have transactions getting committed but not appearing so in the client. This is probably the issue that was reported on #314.
How to reproduce
The issue happens when we execute more than 1 transaction against the same account (which get included in different blocks). Then when we perform a sync we end up with the last of those in a committed state while the others do not. An easy way of reproducing it is by:

creating a wallet and a fungible faucet
mint 2 or more times
wait for a bit and then sync
then run miden tx and you'll see only the last one being committed

The cause
The cause of this is somewhat rooted in the sync_state protocol. Whenever we do a sync we get account hash updates corresponding to the account ids from the SyncStateRequest we made. However, updates on account hashes only get included if they're the current account hash of that account. That means that if account A was changed on blocks 2, 4 and 6, our local chain tip points to 0, and we do a sync (while trakcing A in our client). The whole process would span 3 requests (first we get a response for block 2, then we do a new request and get 4 and lastly block 6), and the account hash update for A would only come in the last response.
Changing the protocol isn't as easy though since the node only tracks a single row per account and discards the history, so unless we change that (there might be some storage limitations there) it won't be possible to send all account hash updates.
What this PR does
In this PR I extend the commitment check on transactions to do the following:

If the current check said it's committed => it's committed
If an uncommitted TX A with init_account_hash = X gets committed and there is a second uncommitted TX B with final_account_hash = X, then that gets committed as well
This last property describes a transitive relation so what we end up doing is computing the transitive closure (that is: get the txs we commit, and go to previous txs via prev.final_account_hash == current.init_account_hash and mark them as committed)

Current solution's limitations
This solution works fine and get's the transactions that previously ended up pending to be committed. However, with this check we lose track of the block height at which some TXs get committed. We might end with something like this:

Which does not reflect what actually happened (each one of those in the image happened in a different block). One way of "hiding" this is not showing the block height or showing (Block <= 446) but still we'd be storing false info.
Some alternatives

As @igamigo suggested in #360, we could replace the commitment check from all nullifiers came in the update && all output notes came in the update && the change in account hash came in the update to all nullifiers came in the update && (all output notes came in the update || the change in account hash came in the update)

This comes at a cost where TXs that change the account hash but do not produce/consume notes would be committed instantly. Also, once the node gets decentralized it might be a bit unsafe since someone could consume the same note as you and you'd see your tx getting committed while it could happen that the other user got it first
At first I thought of combining the solution from this PR and this change in the commitment check, but tbh changing the commitment check will "eat" all cases this PR change handles and I don't see too much sense in having code that won't be executed (despite it being valuable in the future)

We could change the protocol and send all account hash updates instead of the last one, but that would require bigger changes to the node

BTW #360 can be tested in the integration tests with executing a couple of transactions and syncing immediately (instead of waiting for the transaction to be marked as committed as we usually do). It would be nice if we could test this behavior and make sure the error does not occur or is more comprehensive than what the error message suggests , but maybe not for this PR.

Yeah - I think we need a more comprehensive solution here which will involve refactoring in miden-base and miden-node. Specifically, I'm thinking that the state sync endpoint should also return a list of transactions added to the chain involving any of the account IDs sent with the request. This should remove all the ambiguity and I think I have come up with a relatively clean way to do this.
I'll create issues for this early next week, and I think we should be able to implement this in the next 1 or 2 weeks.

Yeah - I think we need a more comprehensive solution here which will involve refactoring in miden-base and miden-node. Specifically, I'm thinking that the state sync endpoint should also return a list of transactions added to the chain involving any of the account IDs sent with the request. This should remove all the ambiguity and I think I have come up with a relatively clean way to do this.
I'll create issues for this early next week, and I think we should be able to implement this in the next 1 or 2 weeks.

should we close this one then?

should we close this one then?

Maybe keep it open until the other solution is implemented? But I'm fine either way.

closing this PR, following this up in https://github.com/0xPolygonMiden/miden-client/issues/370


Add helm push github action

Task description:
https://github.com/kmesh-net/kmesh/pull/813 added helm package and helm push support, then we can add a github action now to do helm push automatically.
Solution:
Who can join or take the task:
The good first issue is intended for first-time contributors to get started on his/her contributor journey.
After a contributor has successfully completed 1-2 good first issue's,
they should be ready to move on to help wanted items, saving the remaining good first issue for other new contributors.
How to join or take the task:
Just reply on the issue with the message /assign in a separate line.
Then, the issue will be assigned to you.
How to ask for help:
If you need help or have questions, please feel free to ask on this issue.
The issue author or other members of the community will guide you through the contribution process.

/assign

Thanks @byhlel We have ${{ secrets.GH_PAT }} used to login ghcr.io https://github.com/kmesh-net/kmesh/blob/main/.github/workflows/release-master.yaml#L103

@byhlel  Any progress


pull

pull

Hi @yangyachao, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

Not sure what this is - it doesn't seem to contain any changes, so I'm guessing it was submitted by mistake. Hence closing.


Deployment Frequency should group by pod

We want to measure deployments per-pod, not per-container. The sdp:lead_time:by_app metric does this by taking the minimum value grouped by app and commit. However, the deployment queries do no such grouping.
We should group by the {pod} label in prometheus.

This seems to be a problem for pods that have more than one container in their definition. In our case, we add a sidecar to the application container, and the Deployment Frequency graph counts it as two deployments (one for each container image) instead of one.

@PabloHiro this is something we will look into. The {pod} label isn't an option as it presents the pod name of an exporter that was used to scrape the data by prometheus. We may need to modify the deploytime exporter to combine those sidecar containers or think of other way that problem.


dbgpt cli not work

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating system information
Linux
Python version information

=3.11

DB-GPT version
main
Related scenes

[ ] Chat Data
[ ] Chat Excel
[ ] Chat DB
[ ] Chat Knowledge
[ ] Model Management
[ ] Dashboard
[ ] Plugins

Installation Information

[ ] Installation From Source

[ ] Docker Installation

[ ] Docker Compose Installation

[ ] Cluster Installation

[ ] AutoDL Image

[ ] Other

Device information
cpu
Models information

What happened

What you expected to happen

How to reproduce

Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

try pip install -e .


Delete old CCLA

Signed-off-by: John Mertic<EMAIL_ADDRESS>

This binary file is linked to from the website - https://www.openvdb.org/license/.
(https://github.com/AcademySoftwareFoundation/openvdb-website/blob/master/license/index.html#L67)
We should remove the link and adjust the text in this license section as well.
(@swinslow)

Good call, @danrbailey. Let me submit a PR to address that.

Hi @danrbailey, I've added #22 to update the language in the license and CLA sections, and also to clarify the description of the DCO as a separate section. Happy to discuss if you have any questions / comments about the proposed changes in #22.


STITCH-1317 Handle transport timeouts

This was basically the same change as for Swift. I added a transport timeout setting to client configuration, and I modified doRequest in the StitchRequestClient to perform the Transport round trip on a background thread, and wrote a test.
I'm somewhat concerned with the performance implications of the ExecutorService I'm using to wait for the round trip to finish, so I would like some feedback on that, mainly since I'm not too familiar with concurrency in Java.

Trying to rebase on eric's recent work on v4-alpha is a mess of merge conflicts. Since I'm going to be pretty much redoing this anyway, I'm going to close this and open a new PR when it's ready.


Create a command for adding a new cell or replacing the current code triggered from a kernel

This is similar to get_ipython.set_next_input., but enable to create a code cell in any of the current languages.
This allows the kernel to dynamically generate code in any language and add it to the notebook which would be helpful for generated code logics.

This is partially supported today but needs some improvements.

The limitations are:

It can only add a cell, not edit an existing one.
It always adds the cell at the end of the notebook. This probably isn't the right behavior when running a cell somewhere earlier in the notebook, and if the end of the notebook is scrolled out of view, then it's not apparent to the user that anything happened.

Related: #2878.

I'm going to close this issue. It's partially supported today via SendEditableCode as noted above. While this doesn't support replacing the content of an existing cell, the use case for that is less clear. A separate issue should be opened for that to expand on the use cases before we implement it.


Create a ZXing (MLKit-free) build for F-Droid

What

[ ] Create a blob free version of the app that we can deploy to F-Droid

[ ] Remove MLKit
[ ] Ensure whether we need to tweak Sentry or not

Part of

#2515

Initial message by @g123k
Hi everyone,
Smoothie has two dependencies to manage barcode decoding: google_ml_barcode_scanner (MLKit) and qr_code_scanner (ZXing). For both cases, the engine is embedded in our app. For debug APKs (= non-optimized), even with the Flutter engine, the difference with V1 is huge:

V1 (native Android - with a dynamic downloaded MLKit engine): 30 Mo
V1 (native Android - embedded MLKit engine): ~ 40 Mo
V2 (Flutter): 95 Mo (without x86 binaries)

The reason behind this choice seems to be related that we want some builds for Google Play (let's say with MLKit) and for other app stores (FDroid…). Instead of building a single "fat" application, shouldn't we split the app into two versions?
Or maybe is qr_code_scanner still relevant? Is embedding MLKit an "OK" solution for non-Google Play Android stores?
Part of

#2515

When switching back to ML Kit we left in ZXing for two reasons: 1. Comparing them, I'd say that's done and 2. To allow publishing in stores like fDroid
But first most stores like these from Amazon or Samsung don't really care if we include ML Kit or not. The only one I know of is FDroid.
V1 is on there so the initial plan was to also release it there but that's not a priority.
If there is a way to build with only one of them included without splitting the codebase that's a idea if that's not possible we can just remove qr_code_scanner. It's currently not in use and with the current level of abstraction it's easy to add back in if we need it again

What’s our déploiement goal for B1 and upcoming releases?
Only Google Play? Fdroid?

@teolemon What’s our déploiement goal for B1 and upcoming releases?
Only Google Play? Fdroid?

Only Google Play, but it'd be cool to figure out fdroid after that

Ok, so here is the plan:

For 1.0.0:

Embedded MLKit for Android

Embedded MLKit for iOS

For the upcoming release (let's say 1.1.x):

Embedded MLKit for Android - Google Play

Zxing for Android - Non GMS compliant stores (eg: FDroid)

Embedded MLKit for iOS

Is-it OK for everyone?

Is-it OK for everyone?

Understood, though I'm not convinced the energy spent there will be worth the trouble. For the Android app, how many downloads from Google Play and from FDroid?

We want a fully free version to be available for F-Droid and FOSS (Open Food Facts is about Open Source).
In V1, we actually allow users to opt-in into ML Kit, since there are terms and conditions.
https://github.com/openfoodfacts/openfoodfacts-androidapp/pull/3836
<string name="preference_choose_scanner_dialog_title">New: Enhanced “MLKit” scanner</string>
<string name="preference_choose_scanner_dialog_body">We have included a new option to more reliably scan barcodes. While this scanner works on your device, using machine learning,
        please be aware that it is a proprietary component provided by Google, governed by this privacy policy, and that some limited telemetry might be sent back to Google’s servers
        to improve their software. As noted in the MLKit terms, this won’t include any information about the products you scan and the telemetry is anonymized. Choosing MLKit scanner
        implies that you accept those terms\nNote: You can switch back at any time between the 2 scanners in the Settings.

Regarding app size in general as in OP, maybe we could get rid of external packages that we don't use often.
For the record, those are all the external packages we use:
% grep -rh ".dart';" * | grep -v "package:smooth_app" | grep -v "package:flutter" | grep -v "package:openfoodfacts" | sort | uniq -c | sort
   1 import 'package:camera_web/camera_web.dart';
   1 import 'package:carousel_slider/carousel_slider.dart';
   1 import 'package:collection/collection.dart';
   1 import 'package:device_preview/device_preview.dart';
   1 import 'package:fwfh_selectable_text/fwfh_selectable_text.dart';
   1 import 'package:hive/hive.dart';
   1 import 'package:http/http.dart';
   1 import 'package:image_cropper/image_cropper.dart';
   1 import 'package:image_cropper_for_web/image_cropper_for_web.dart';
   1 import 'package:image_picker/image_picker.dart';
   1 import 'package:image_picker_for_web/image_picker_for_web.dart';
   1 import 'package:intl/intl.dart';
   1 import 'package:iso_countries/iso_countries.dart';
   1 import 'package:latlong2/latlong.dart';
   1 import 'package:matomo_forever/matomo_forever.dart';
   1 import 'package:modal_bottom_sheet/modal_bottom_sheet.dart';
   1 import 'package:package_info_plus_web/package_info_plus_web.dart';
   1 import 'package:path/path.dart';
   1 import 'package:path_provider/path_provider.dart';
   1 import 'package:percent_indicator/percent_indicator.dart';
   1 import 'package:photo_view/photo_view.dart';
   1 import 'package:photo_view/photo_view_gallery.dart';
   1 import 'package:qr_code_scanner/qr_code_scanner.dart';
   1 import 'package:rxdart/rxdart.dart';
   1 import 'package:sentry_flutter/sentry_flutter_web.dart';
   1 import 'package:shared_preferences/shared_preferences.dart';
   1 import 'package:shared_preferences_web/shared_preferences_web.dart';
   1 import 'package:typed_data/typed_buffers.dart';
   1 import 'package:url_launcher_web/url_launcher_web.dart';
   1 import 'package:uuid/uuid.dart';
   2 import 'package:mailto/mailto.dart';
   2 import 'package:permission_handler/permission_handler.dart';
   2 import 'package:sentry_flutter/sentry_flutter.dart';
   2 import 'package:visibility_detector/visibility_detector.dart';
   4 import 'package:google_ml_barcode_scanner/google_ml_barcode_scanner.dart';
   4 import 'package:package_info_plus/package_info_plus.dart';
   4 import 'package:url_launcher/url_launcher.dart';
   6 import 'package:camera/camera.dart';
   6 import 'package:hive_flutter/hive_flutter.dart';
   8 import 'package:auto_size_text/auto_size_text.dart';
  44 import 'package:provider/provider.dart';

Excellent idea @monsieurtanuki.
I have created a dedicated issue.
Should also be followed by #1824

Good news: the app is working well on Huawei devices (without GMS).
The only use case where we will have to use ZXing is for FDroid.

Heyy @g123k the new modular pipline is up and running so if we create a different flavour / store listing it's just a matter of passing different values to the workflow to create a differnt app.

ℹ This issue will be implemented as part of #3084 (step 3)

A few after the release, we should think about removing the data import feature #3150

@g123k @M123-dev @monsieurtanuki is that something we can now do ?
Unsure why we closed it in the first place

I opened a new ticket, because this was is on a related subject, not the core.


Code block doesn't parse after 10000bytes characters.

Report bugs here only for the Node JavaScript library.
If you're having problems using Notion's API, or have any other feedback about the API including feature requests for the JavaScript library, please email support at<EMAIL_ADDRESS>Describe the bug
Code block doesn't parse after 10000bytes characters.
Screenshots
Until 9999bytes input, 'Code block' parse the syntax well. but If write more than 9999 letters, doesn't parse it.

Additional context
I'd like to patch the source code, but It seems not a part of notion-sdk-js, so I just report it. Thanks.

@nightohl, currently this is a limitation in the Notion product and unrelated to the API. I have noted your feedback internally so it can be tracked. Closing this issue for now.


Template render failing

While learning how to use OteraEngine with Oxygen.jl I got an error when trying to render a template.
The error: UndefVarError: thtow not defined
The fix: I was able to resolve this issue by changing thtow to throw line 139 in src/template.jl
The template used:

                First	Last	Phone	Email

            {% for i in contacts %}

                {{ i["first"] }}
                {{ i["last"] }}
                {{ i["phone"] }}
                {{ i["email"] }}

                        Edit
                        View

            {% end %}

Data sent:
test_dict = Dict(
    "contacts" => [
        Dict(
            "id" => 1,
            "first" => "John",
            "last" => "Doe",
            "phone" => "555-1234",
            "email" =><EMAIL_ADDRESS>        ),
        Dict(
            "id" => 2,
            "first" => "Jane",
            "last" => "Doe",
            "phone" => "555-1234",
            "email" =><EMAIL_ADDRESS>        ),
        Dict(
            "id" => 3,
            "first" => "Josh",
            "last" => "Doe",
            "phone" => "555-1234",
            "email" =><EMAIL_ADDRESS>        )
    ]
)

p.s. Great work on the package. I have greatly enjoyed using it.

Hi @Justyn-Nissly .
Thanks for your report. I fixed it and released new version v0.4.2.


Add a 'worklet ready' handshake when starting up. (Fixes 'placeholderchunk' race condition error.)

When we ask the worklet to start up, because requests to the worklet are
asynchronous, we can't be sure of whether the worklet has even received a
previous client's request to shut down yet. This means we may get messages
that were intended for a previous client.
We serialize this by adding a 'handshake': when we ask the worklet to start,
we wait to get a 'ready' message back, indicating that it has started, before
accepting messages from it.
This should eliminate the stop-start race, wherein we get messages intended
for a previous client that already stopped the worklet (but the worklet has
not yet processed the command to stop.)
We also add a "cookie" to identify a specific start request; this should
eliminate an even more obscure race (stop-start-stop-start, where the second
start races the worklet's processing of the first start.)

This is effectively a two-parter -- without the cookie, just sending and awaiting a 'ready' message should be enough to fix the stop-start race that we're seeing in practice. I believe the cookie is only necessary to fix a more obscure stop-start-stop-start race that I don't think we're likely to run into unless something else is going wrong (but I figured if I was going to do it, I should do it right.)


grpc code generator in v1.4.0 (and master) is outdated

What version of protobuf and what language are you using?
v1.3.5, v1.4.0 and master

Latest commit on tag v1.4.0 is from Nov 2018
https://github.com/golang/protobuf/tree/v1.4.0/protoc-gen-go/grpc

Latest commit from v1.3.5 is from Jan 2020
https://github.com/golang/protobuf/tree/v1.3.5/protoc-gen-go/grpc

Master is missing commits, too
https://github.com/golang/protobuf/tree/master/protoc-gen-go/grpc

The protoc-gen-go/grpc package is dead code. The underlying implementation for grpc is in github.com/golang/protobuf/internal/gengogrpc, which at the time created was a direct copy of the code in google.golang.org/protobuf/cmd/protoc-gen-go-grpc/internal_gengogrpc.
The commit you think is missing was simultaneously committed to the new implementation here.

This will break users using grpc as a library (instead of using the binary generator). I'm verifying with the user now, in https://github.com/grpc/grpc-go/issues/3591.
But even though using the library isn't expected, was there any particular reason to have outdated code there?
It's an exported package (probably should have been, but..), and I don't see any reason to break it.

This will break users using grpc as a library (instead of using the binary generator).

If that's the case, then that use case is unfortunately unsupported. Any uses of generator as a library has explicitly been stated to be outside our compatibility policy. That said, we may consider making the grpc package identical to what it was in v1.3.5 even though it's on the chopping block for being removed in the future.


Job failing with very little error output

Following on from the discussion here, I'm attempting to use your version of the library, tag v1.3.2, but all my jobs are failing with the following error stored in Redis:
"exception": "Resque_Job_DirtyExitException",
"error": "Job exited with exit code 255",
"backtrace": [
    "#0 \/var\/www\/html\/vendor\/danhunsaker\/php-resque\/bin\/resque(185): Resque_Worker->work(5, false)",
    "#1 {main}"
  ],

The above doesn't really tell me what the problem is. I was wondering if this is an issue you've come across before and have some ideas as to what could be wrong. I'm using the latest version of redis available here
I haven't come across this issue using the master  branch of chrisboulton's version of the library.

Sorry I didn't respond sooner.  Exit code 255 is a PHP Fatal Error, which means we get exactly as much detail as PHP provides for any of its fatal errors, but not necessarily anywhere useful.  You'll pretty much need to collect the worker's STDOUT to get more detail on why it was dying with the prior Redis version.


Fix for occasional server when adding or removing a feature

I tested this fix several times and I was not anymore able to re-produce any error even I fired automatically X times AddFeatureChange -change from AddFeature.tsx

I wanted to make sure I understood what was going on and what made it so the app-level exception handler missed these exceptions and crashed the app. The main important change ended up being this one:
diff --git a/packages/apollo-shared/src/Changes/AddFeatureChange.ts b/packages/apollo-shared/src/Changes/AddFeatureChange.ts
--- a/packages/apollo-shared/src/Changes/AddFeatureChange.ts
+++ b/packages/apollo-shared/src/Changes/AddFeatureChange.ts
@@ -155,7 +155,7 @@ export class AddFeatureChange extends FeatureChange {
           })
           const childIds = this.getChildFeatureIds(addedFeature)
           topLevelFeature.allIds.push(addedFeature._id, ...childIds)
-          topLevelFeature.save()
+          await topLevelFeature.save()
         } else {
           const childIds = this.getChildFeatureIds(addedFeature)
           const allIdsV2 = [addedFeature._id, ...childIds]

This put the mongoose saving back into the regular flow of the app so the error gets caught and doesn't crash. I also tested with requests not using the UI, and it works well now.
To make sure we don't get any other unexpected crashes, I enabled the @typescript-eslint/no-floating-promises lint rule (thanks for the tip @cmdcolin) and fixed the errors that it revealed.


Remove the ASCII Story from python script

Hi!
I a have suggestion to make the structure of the project more sustainable and readable.
At the moment you have all the stories (parts, answers, etc) inside of the code (so called hardcoded in the script) and it makes it difficult to identify where is actually the logic of the game.
My suggestion:
Separate every story in a different txt file (e. g. part1.txt, part2.txt) and use a function to convert a txt into a string.
The function story_to_str takes the path of a file as an argument and converts it into a str that can be printed.
def story_to_str(file_path: str) -> str:
    with open(file_path) as file:
        return "".join(file.readlines())

And you can call the function every time as follows:
print(story_to_str("part1.txt"))

That would make the code of the game cleaner and easier to follow.
Hope it helps!

Hey!
Of course it helps!
Sorry to see the issue too late...
I will improve the code this weekend.
A valdesiano binary hug to Deutschland!


Matching menu entries must match with or without acents in builderPromptschoice

When creating a bot that displays a list of options (builder.prompts.choise)
containing accented words, writing any of them without accents is not recognized as part of the list, and the user gets the message: ". I did not Understand Please Choose an option from the list.".
In Spanish at least, a meny entry should be able to match with and without accents, because people usually do not write accents over vowels during an informal chat (like with a  bot).

Are you talking about the node or C# SDK?

Hi,in node

Closing this issue due to age. @rouscast - please open a new issue if this issue is not fixed and needs further discussion. Thanks!

Good bug... We can look into improving this. @chrimc62 what does C# do in this case?

Added to our bug backlog, closing the issue.


Mac: Command-s

Have you considered expanding this to include CMD-s for mac users? Command-s is default for save for Mac, and I installed this package hoping it would save-all for me with that binding, but it doesn't.

I found it's not necessary to use this package. Just modify your keymap to include the following:
"body":
  "cmd-s": "window:save-all"


Request: Expand further on Portus TLS implementation

I've been working on trying to get the Portus TLS portion working for secure communication between the resources. And, I'm hoping that someone can clarify the docs a little bit.

To run Portus securely you'll need an SSL key and certificate that cover the domain names that the Portus, Docker registry and Nginx services use.

Check. I have a cert that covers the fqdn ex foo.bar.com

To use TLS you must set portus.tls.enabled to true.

Check. Option is configured to true in the values.yaml

You will need to generate an appropriate key and certificate if you would like to install the chart securely.

Check. see the first quote above

If you would like to enable TLS for the Portus installation you will need to store your key in the value portus.tls.key and the certificate in the value portus.tls.cert

This is where I'm a bit confused. Perhaps this is because I'm new to helm, but, is this expecting a file or a C&P of the crt & key. I've tried both with no avail. I've renamed my cert to portus.crt and portus.key and I've tried it a number of different ways and I end up in the same spot.
2017/12/26 22:16:31 [emerg] 1#1: PEM_read_bio_X509_AUX("/certificates/portus.crt") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE) nginx: [emerg] PEM_read_bio_X509_AUX("/certificates/portus.crt") failed (SSL: error:0906D06C:PEM routines:PEM_read_bio:no start line:Expecting: TRUSTED CERTIFICATE)
checking my certs with "openssl x509 -in certs/portus.crt -text -noout" returns expected output.
So, I guess my question/request is, what is the proper way to setup TLS in portus.
Also, side note. How would one do this leveraging kube-lego? I have my own cert that I bought from cert authority, however it would be cool to get this working with kube-lego moving forward.

Hey @Nick-Harvey , thanks for reaching out.
Sorry, I'm not sure what part of you first question "or a C&P of the crt & key", means?
For TLS support the Portus key and cert values need to use the full contents of both the key and cert files that you want to use. For example if you update the values.yaml file it should look something like:
portus:
  ...

  tls:
    key: |
      -----BEGIN RSA PRIVATE KEY-----
      ...
      -----BEGIN RSA PRIVATE KEY-----

    cert: |
      -----BEGIN CERTIFICATE-----
      ...
      -----END CERTIFICATE-----

I hope this clarifies things a bit. Your comment makes me realize that the documentation is not very clear for the TLS values, so I think that will need to be updated to avoid confusion in the future.
If TLS still does not work for you after using the format above please let me know. If there are any bugs in the TLS support for this chart I will definitely look into it.
And as for kube-lego, I agree that leveraging that would be nice going forward. This chart still needs some work, we have not quite gotten to the point where we are ready to propose it into the official charts repo, so that might have to be something added at a later point. But I have seen some charts in the official repo offer kube-lego support, so I think that could potentially be something that could be offered in the Portus chart as well.

Found out that I need to add a "|" to keep the cert formatting in place, but upon deployment, the portus container is stuck in a waiting failed state. My guess is that it has something to do with the cert having to cover all the hostnames, but since helm generates names upon deployment it's going to be difficult to generate a cert that covers it.

@bonhamjp
I have went through all the discussion above, and now understand better on tls setup for portus.
i am now able to deploy insecure portus, ingress tls enalbed portus. Now i am trying to deploy portus with tls enabled all the way,  but i met problem to create cert and key for the internal pods, like below:
test-portus
test-portus-registry
test-portus-nginx
test-portus-mariadb
Could you help to share some points on how to create crt and key for all these pods?
Thanks,
yzha


Add control-plane taint and label for Kubernetes v1.24+

Similar to NMO's PR we add the new taint and label for control-plane node, and in the future we will remove the master taint and label.

After updating CI - https://github.com/openshift/release/pull/32186
/retest

/retest

/lgtm
/retest

/test all

/cherry-pick release-0.3


Issue when chaining BFTasks created from Swift

The test [result isKindOfClass:[BFTask class]] is failing sometimes when using tasks created from Swift.
The result of the test is undefined (know bug by apple)

isKindOfClass: should continue to work, since when converted to Swift - BFTask might become a subclass of BFTask aka SwiftBFTask. Which is valid for isKindOfClass:
Any chance you can create a repro PR that showcases the bug?

What’s odd now is that with a clean test framework I can’t reproduce the bug… But it repro 100% of times with the current project I’m working on.
I’ll get you screenshots of the current behaviour
On Fri, Jul 31, 2015 at 1:35 PM, Nikita Lutsenko<EMAIL_ADDRESS>wrote:

isKindOfClass: should continue to work, since when converted to Swift - BFTask might become a subclass of BFTask aka SwiftBFTask. Which is valid for isKindOfClass:
Any chance you can create a repro PR that showcases the bug?
Reply to this email directly or view it on GitHub:
https://github.com/BoltsFramework/Bolts-iOS/issues/111#issuecomment-126763544

As you can see the current stack: BOOL isKindOfClass = NO, however, with the NSStringFromClass.. introspection it yields "BFTask"

@nlutsenko what do you think? strange, odd and hardly reproductible with another project...

BTW, it's with the Bolts framework from the lastest FacebookSDK release

#116 includes a repository with a task that doesn't chain properly. I know it's supposed to be an issue with swift, but this has the exact same symptoms, but without swift...maybe it's closer to the actual root issue?

Great. Many thanks guys for the repro. I'll take a look shortly and will update here.

Actually, I just tried @flovilmart 's fix and it doesn't fix my particular case. What I'd done is just compared the two NSStringFromClass, which fixes his issue, but adds problems with subclasses, but for some reason that branch doesn't fix my example.

That's getting even more interesting. Two related issues which don't fix the same way :popcorn:
On Sat, Aug 8, 2015 at 9:22 PM, Korben Rusek<EMAIL_ADDRESS>wrote:

Actually, I just tried @flovilmart 's fix and it doesn't fix my particular case. What I'd done is just compared the two NSStringFromClass, which fixes his issue, but adds problems with subclasses, but for some reason that branch doesn't fix my example.
Reply to this email directly or view it on GitHub:
https://github.com/BoltsFramework/Bolts-iOS/issues/111#issuecomment-129081059

@krusek I've just ran the test on Xcode 6.4 with the project from https://github.com/krusek/Bolts-error
It actually succeeds...
Was there anything specific about your configuration?

I take it back, I can see the issue right now...

Oh, crazy! I am yet once again amazed by how this is implicit, though extremely fragile and
I figured why this happens for you @krusek, which could also be the reason behind the problem with @flovilmart case (haven't seen the source there, so can't confirm).
It's extremely non-obvious, but since you have a dynamic framework that links Bolts.framework via static code, the code from it will be included there. Then you link Bolts.framework to your unit testing target.
Since code for BFTask now is both statically linked to KRTaskUnzipper.framework (loaded dynamically) and to Unit Testing Bundle (also loaded dynamically), and the code is the same - there is no compiler error or warning, though these classes are actually different and referenced differently in runtime.
So one is created inside KRTaskUnzipper.framework, but actually used by code from Unit Testing Bundle - which tries to lookup that class in it's runtime (doesn't lookup in dynamic libraries, since it finds it locally), but can't find the same class.
Does it make sense guys? It's tough to explain, but I can try some other way...
Fix: Remove linking with Bolts.framework from your unit testing bundle.
Just tested it locally and it works as expected - it continues on a proper task and the result is NSString instead of BFTask with NSString.
Step-by-step to fix the project by @krusek :

Remove KRTaskUnzipperTests from link_with in Podfile
Remove libPods.a from Link phase on KRTaskUnzipperTests
Remove $(inherited) and -l"Bolts" from Other Linker Flags on KRTaskUnzipperTests
Run the tests
???
Profit

I would recommend setting up the Framework via Cocoapods actually, so if you want to use it in a project or write tests against it - you link Bolts.framework only with a single target automatically and don't need to do the fix mentioned above. (we have this done in https://github.com/ParsePlatform/ParseUI-iOS)
Let me know if this helps, guys...

Awesome! Thanks for the fix!
I guess that will happen a lot with dynamic libs now that use libs.
If using Carthage and building/testing a framework (that will be distributed via Carthage), should I put my frameworks in framework search path in every case and let the automatic linking do it's magic?
On Sun, Aug 9, 2015 at 3:21 AM, Nikita Lutsenko<EMAIL_ADDRESS>wrote:

I take it back, I can see the issue right now...
Reply to this email directly or view it on GitHub:
https://github.com/BoltsFramework/Bolts-iOS/issues/111#issuecomment-129129814

it worked, thanks! my actual project has lots of BFTasks created and working properly (and some more pods), odd that only this snippet was borked (and could be pulled out into a separate/standalone project still being borked).

@flovilmart - that works, yup. Another solution would be 'use_frameworks!' flag via Covoapods.
Thanks for raising this guys, and glad I could help.

Thanks @nlutsenko!

@nlutsenko
For me  the resolution si not quite the same.
My project is a Swift framework.
I had Linking  + Copy in bundle resources (/framework) for my dependencies (Bolts, Stripe and Realm)
When I removed Bolts from the linking and put it to auto linking the compiler could not build the framework as Bolts is no a dylib.
My solution was:

Remove the Deps. from Copy Bundle Resources
Remove dynamic libs from linking
Keep bolts linking in the framework AND the tests target
Profit

So for my case, the resolution is also related to the build configuration, linking and embedding but solves differently!
Cheers!
F.


voucher validity minutes minimum field input does not match saving requirements

When creating new vouchers for a voucher splash you are asked to set timelimit "
Validity Minutes" to at least 5 minutes, but doing this wont let you save and generate vouchers, the pages saving minimum is 60 minutes for this field.

@ChristianWinkler I cannot replicate this. Can you please provide screenshots of the issue.

you might as well change just the text for the validity minute field < 60

It wasn't that field causing the problem. The fix in beta should resolve.

@ChristianWinkler can you confirm it's fixed in beta?


Regression: ES6 & TypeScript "go to definition" jumps to import

VSCode Version: 1.2.1
OS Version: OS X 10.11.5

I the past week (or two?) the "go to definition" feature for ES6 and TypeScript has changed from jumping to the original definition to jumping to the import at the top of the current file. That's the old broken behaviour which was reported in #263 (and despite that issue being open still, was actually fixed and has worked nicely for several months).
"Peek definition" also suffers from the same problem.
I've opened this as a new issue to report it as regression and not as a feature request 😄

This is actually a problem in the tsserver. Moving to the TS team.

This issue was moved to Microsoft/TypeScript#9274