Latest version of PySCIPOpt goes wrong while v1.4.9 works fine

Hi all,
After installing the latest version of PySCIPOpt in Python3.6 on Windows64, I try to call it by from pyscipopt import Model, and a common error occurs as follows:
from pyscipopt.scip import Model
ImportError: DLL load failed: The specified module could not be found.

I have included C:\Program Files\SCIPOptSuite 5.0.1\bin to my system path. So I guess this should not be the problem.
Then I removed my PySCIPOpt of the latest version, and installed PySCIPOpt of version v1.4.9. Now everything works fine.
I don't know if anybody else has encountered this, and what might have caused this?

PySCIPOpt is not backwards compatible to older versions of the SCIP Optimization Suite. You should always use the latest PySCIPOpt together with the latest SCIP version. You should not just update one part.


Unable to create issue due to additional required fields

What it should do
Find required fields, and allow inputting required ones
What it does
Fails to create a new issue because some fields are required for new issues on our Jira projects.
Other Info
After looking into the Jira API a bit, the expand query string can be set to get all fields on an issue type. However, with many projects this can be massive. I would suggest waiting to fetch a more detailed set of metadata until after the user has selected the project at the very least, maybe even better to wait until they have selected the type. The request can then be filtered down by project name and issue type to limit the returned data (see https://docs.atlassian.com/software/jira/docs/api/REST/8.1.2/#api/2/issue-getCreateIssueMeta)

This could be fairly easy to implement as you said, however, I'm thinking how we can implement this when creating issues without the interactive mode, any ideas?

One temporal solution, if the project and issue type are provided and it has additional fields, enter into the interactive mode to ask for those required fields: jira create -p PK -t bug -m "My issue name" (ask for the required fields interactively) what do you think?

Maybe provide a "generic" flag where you could pass some kind of set of key value pairs for the additional fields, maybe just a plain old JSON object (which would be cleaner to parse, but might be harder to type). I don't know about the flag parsing library you are using, but if you are allowed to repeat flags, you could do like -c "key: value" -c "key2: value2" to allow for multiple fields to be input.
The "go-to-interactive" thing seems like a decent stopgap, but looses some of the power you get to automate things when you have everything as a flag.

@allout58 that sounds good, and it's supported by commander, now I'm thinking about the data type, is it always text?

Here is an example of the types for the project I found this issue on originally.
["issuetype","array","string","project","option","timetracking","any","date","user","priority","issuelink"]
It looks like just strings should be okay, as my guess is all of these would have to be typed as strings for the JSON request anyways.


Can't upload file to Discord

Error

{'content': 'v2.0 - Fix build again', 'username': 'bCore', 'avatar_url': 'https://github.com/D-x-Z.png'}
Traceback (most recent call last):
File "/webhook.py", line 187, in
execute_webhook(payload, args['filename'])
File "/webhook.py", line 132, in execute_webhook
response = requests.post(args['webhook'], data=payload, files={'upload_file': open(filename, 'rb')})
File "/usr/lib/python3/dist-packages/requests/api.py", line 116, in post
return request('post', url, data=data, json=json, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 60, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 519, in request
prep = self.prepare_request(req)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 452, in prepare_request
p.prepare(
File "/usr/lib/python3/dist-packages/requests/models.py", line 313, in prepare
self.prepare_url(url, params)
File "/usr/lib/python3/dist-packages/requests/models.py", line 387, in prepare_url
raise MissingSchema(error)
requests.exceptions.MissingSchema: Invalid URL '': No schema supplied. Perhaps you meant http://?

You can see the repository here https://github.com/D-x-Z/bCore


Add glossary components

Adds three components for building pages with an alphabetized list of terms (currently used to build the Glossary page):
GlossaryCard for a single term.

GlossarySection for defining the layout for each letter including the letter and GlossaryCards for relevant cards.

GlossaryPage for defining the layout for all GlossarySections.

Thanks @katydecorah! This code worked well with my test case (I also checked in IE11). Are there other test cases we should include (entries that start with numbers comes to mind, but there could be others).


Fix build VM comparison

Stage 3: https://builds.gradle.org/viewLog.html?buildId=3029534&tab=queuedBuildOverviewTab
Stage 5: https://builds.gradle.org/viewQueued.html?itemId=3030171&tab=queuedBuildOverviewTab

The code could potentially be improved more. First adding and later removing the daemon default args seems like it adds unnecessary complexity. But there are other places where DaemonParameters is used and the order in which arguments are added can be important.
Its probably best to focus this PR on fixing this issue without doing any structural changes.


fixsupport check priv when tvf use resource

current, follow sql not check priv, we need check usage priv of test_resource
SELECT * FROM S3 (
    "uri" = "xxx",
    "format" = "orc",
    "resource" = "test_resource",
    "use_path_style" = "true"
);

run buildall

run buildall

run buildall

run buildall

run buildall


Handle plugins

How would you like to handle plugins? (which process commands, inline queries, etc)
matchPlugin currently finds first plugin whose RegExp pattern matches query from user input

https://github.com/goodmind/cycle-telegram/blob/master/src/plugins.js

Rewritten version supports multiple matches

https://github.com/goodmind/cycle-telegram/blob/match-multiple-plugins/src/plugins.js

Possibly remove from driver core for reasons:

Not stream-agnostic
Hard to maintain

Merged in eb6ad77b25f8a39541ccf6c0601695e0a712d933


[WIP] Adding common support for GraphQL.

Adding common support for GraphQL.
This includes:

GraphQL Schema generator that is based on OpenAPI
The necessary schema templates used
The additional schema types used
Helper methods for the GraphQL controller

Moving this GraphQL Common logic from https://github.com/ManageIQ/topological_inventory-api/pull/194

With this PR.  GraphQL can be quickly enabled in OpenAPI based micro-services.

Testing in progress with:

Topological Inventory API
Sources API

/cc @Fryguy as we chatted yesterday, before I forget them, these are the main enhancements:

Expose the versioned GraphQL paths /api//v#.#/graphql
Move from rake triggered GraphQL schema generation to JIT GraphQL Schema generation based on accessed path above.

Remove the [graphql] option from the service's openapi:generate tasks
GraphQL Schema generation can be done on the fly from the graphql controller via a call like ::Api::Docs[version].init_graphql

Ditch the Relay Node interface for the more simpler GraphQL core signature for paging.

Implement the offset and limit parameters in the primary collections
Example:

Relay Specification:
{
  sources(after: "MQ", first: 5) {
    edges {
      node {
        id
        name
        endpoints {
          edges {
            node {
              id
              schema
              host
              port
              authentications {
                edges {
                  node {
                    id
                    username
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

GraphQL Proper:
{
  sources(offset: 6, limit: 5) {
    id
    name
    endpoints {
      id
      schema
      host
      port
      authentications {
        id
        username
      }
    }
  }
}

Which is tons better, we'd just need to add a queryable pagination element that's more appropriate for GraphQL  (vs. REST's first, last, prev, next), i.e. page_size, has_next_page, number_of_pages.

Updated the GraphQL Prototype in manageiq-api-common and related PRs for sources and topological-inventory to take care of the first 2 items discussed with @Fryguy above.
so ....

GraphQL endpoints exposed is now the versioned path

/api/topological-inventory/v1.0/graphql
/api/sources/v1.0/graphql

The openapi JSON has been updated to reflect that the graphql endpoints exist and this can be seen in the swagger editor too.

This now implements a JIT GraphQL Schema generator.

No need to run openapi generate task with the graphql option.
The lib/api/graphql.rb schema file is no longer needed.
GraphQL Schema is dynamically generated for the exposed graphql endpoint's version
so /api/sources/v1.0/graphql will create a v1.0 GraphQL schema based on the openapi v1.0 spec.

/cc @gtanzillo

cc @Hyperkid123


Changine header background colour

Hello,
sorry to be a pain again, is there a way of changing the siteHeader background?

There's no way to do this. You would need to upload an image.


added turkish language

Hi @enginkartal Thanks for the PR, however there are several problems. You need to follow the instructions in the README.  I just noticed there was an error in those instructions, which I have now corrected.  Sorry about that.  I'll try to clarify it further, too as soon as I have a chance.
Here are some things you need to correct:

Your PR changes the main (English) index.md to Turkish, but instead you need to put the Turkish index.md in the tr directory.  That will keep the default home page http://expressjs.com/ in English, and make the Turkish home page be http://expressjs.com/tr/.
Don't duplicate the _includes/api dir or its content. Don't put a tr folder in there.  We don't translate the API docs.  All you need are the tr/4x/api.md and tr/3x/api.md files to ensure that the menu remains in Turkish even if the API doc is not.
I noticed you put redirect_from: "/4x/api.html" in tr/4x/api.md but that will make the default (English) menu while in API docs be the Turkish menu.  So please remove that and the 3x one as well.
Make sure ALL your files have lang: tr in the front-matter.  It looks like you missed some (e.g. guide, starter, resources, etc.  Even if the file is not translated, this ensures that the Turkish menu bar is shown.

I suggest looking at one of the other translations (e.g. fr or de) to see how they did it.  Your PR should create a tr structure that matches it.

I was not available :( I'm looking at the problems 👍

I have updated the PR

Thanks @enginkartal
When I checked out your fork/branch, I got some runtime errors.  Since they were quite easy for me to fix, I went ahead and checked them in.  I guess the README instructions didn't cover some of this....
Anyway, it runs now, so I'll land this.  Thanks for the contribution!

Thank you too @crandmck


[ISSUE #473]fix configuration property get error

fix the configuration check error

Codecov Report

Merging #479 (5c893f8) into develop (0e4def2) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Current head 5c893f8 differs from pull request most recent head aaa65c3. Consider uploading reports for the commit aaa65c3 to get more accurate results

@@            Coverage Diff             @@
##             develop     #479   +/-   ##
==========================================
  Coverage      11.25%   11.25%
  Complexity       326      326
==========================================
  Files            228      228
  Lines          10796    10796
  Branches         907      907
==========================================
  Hits            1215     1215
  Misses          9484     9484
  Partials          97       97

Impacted Files
Coverage Δ

.../eventmesh/common/config/ConfigurationWrapper.java
48.38% <0.00%> (ø)

Continue to review full report at Codecov.

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


Bump WasmEdge version 0.13.1 -> 0.13.2

Bump wasmedge version following the new release today.

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

@apepkuss PTAL


add-category que-faire-en-presence-de-radon-dans-son-logement.md

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


Polish v1 items

Some reference issue with TrackCtaButton on community page though it works its still throwing an error.

yaml might need love from @callicles


Dpdk merge

Backports:
netdev-dpdk: update vhost user client port status.: Can be back-ported to 2.6
dpif-netdev: Fix per packet cycles statistics.: Can be back-ported to 2.6

Thanks Darrell, I merged this and backportd the two patches you highlighted.
I noticed that on some of these you forgot to add your own sign-off.  Please be more careful about that in the future.

Thanks Ben; I double checked the sign-offs, but I was not able to find missing ones ?
Is it possible you saw intervening patches listed in the merge, but not part of the code delta ?
Darrell
From: Ben Pfaff<EMAIL_ADDRESS>Reply-To: openvswitch/ovs<EMAIL_ADDRESS>Date: Tuesday, September 12, 2017 at 7:46 AM
To: openvswitch/ovs<EMAIL_ADDRESS>Cc: Darrel Ball<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [openvswitch/ovs] Dpdk merge (#201)
Thanks Darrell, I merged this and backportd the two patches you highlighted.
I noticed that on some of these you forgot to add your own sign-off. Please be more careful about that in the future.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs_pull_201-23issuecomment-2D328867145&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=nCNJN63adwNqs-L-ji9Fsl2nS0fPqubjDZL3fQvGMOM&s=RMteQj6uDQl350nsvBgS8cnrD_CJdCgEeDxdugvykKE&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_APMgtf8OYebqDYuSv6EWWOmvcvkdwGWOks5shpK2gaJpZM4PPWhv&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=nCNJN63adwNqs-L-ji9Fsl2nS0fPqubjDZL3fQvGMOM&s=utUbqUrOT6jzd6zq9K1I2CgwxclXCYKLohnbCRFhmuA&e=.

Commit 6e491fbc80262 is one example of a commit that lacks your sign-off. Commit 9089475bea3ec7 is another.


Pyrra ListObjectives route returns 500 if SLO is created with invalid metrics

We tried creating an SLO with the following spec:
spec:
  target: "99.9"
  description: "Success ratio of workspace backups"
  window: 4w
  indicator:
    ratio:
      errors:
        metric: gitpod_ws_manager_workspace_backups_failure_total
      total:
        metric: (gitpod_ws_manager_workspace_backups_failure_total + gitpod_ws_manager_workspace_backups_success_total)

We made a mistake here when we assumed that a query could work instead of a single metric.
The problem is that the admission controller accepted the SLO, and after that all other SLOs we had stopped showing up in the ListObjectives route. We got confused at first, but after sometime we noticed the 500s showing up in the logs. We deleted this problematic SLO and 500s disappeared.

Accepting queries instead of a specific metric might be reasonable in some use cases, but that is not the point of this issue 😅. I believe it would be a better experience if the admission controller rejected the SLO during creation time, or if Pyrra UI could handle invalid SLOs without returning 500s.

Thanks for reporting!
Pyrra crashing is far from ideal. Thankfully, once the recording rules are loaded the alerting should continue, even if Pyrra crashes. So it's not as bad as it might sound first.
Pyrra should handle both scenarios gracefully.


Missing update to android v2

Getting: "This app is using a deprecated version of the Android embedding." error

Hello @spendres,
Did you got that error while using examples

@spendres it should be fixed with #26


"File context created without an input path"

On master, and doing sass.render({contents: input}, callback).
When input is an empty string, I get the error File context created without an input path.

Hi @callumlocke<EMAIL_ADDRESS>(master) doesn't support contents as an option. You will need to use either file or data for file paths for file data respectively.
We should provide a more informative error message.

But contents works fine for me. (Just not with an empty string.)

Interesting... can you please supply an example of how you're using node-sass with contents?

No wait, maybe I am using data not contents. Not at a computer right now. I probably just entered the issue wrong. Sorry for confusion.
The point is, whatever property name I'm using, it works fine - except for when the value is an empty string, in which case I get the obscure error message.

Thanks for the clarification, I do think we need a better error message in this case.

Empty braces cause this as well:
var sass = require('node-sass');

sass.render({
}, function(err, result) {
   if (err) {
        console.error(err);
   } else {
        console.log('successfully rendered');
   }
});

https://github.com/sass/node-sass/pull/915#issuecomment-99056525

So there's two separate problems:

Cryptic error message if you fail to provide either file or data (i.e. if both are undefined).

If data is an empty string, node-sass behaves as if it's undefined, and errors out. An empty string is valid Sass so it should not error. Should I open this as a separate issue?

No, no need to, thanks.

Should be fixed by #956. Now I think that the behaviour with render({}) is acceptable - we can complain either about data or file context; we don't know which one was really meant.

It still errors out for me if I try to render/import a file that happens to be empty.

I have the same problem when running my gulp-sass task. When one ore more files of my template are empty, the error undefined:undefined  File context created without an input path occurs.

@callumlocke the patch has not yet been merged. It'll be in the next release of node-sass.

Would No input specified: provide options.data or options.file be a better error message?
I also wonder what we should return in case of async functions: show we call a callback and emulate a libsass error JSON object?

#956 should be ready for testing.

Would No input specified: provide options.data or options.file be a better error message?

Yes. It's exponentially better.

I also wonder what we should do in case of async functions

You suggestion sounds legit.


feat: #870 - new UI for attribute buttons and user preference titles

Deleted files:

attribute_dialog.dart
important.svg
mandatory.svg

Impacted files:

abstract_user_preferences.dart: aligns the title of the header with the expand/collapse icon, and with a compact mode
attribute_button.dart: removed the attribute dialog and put a button instead
attribute_helper.dart: removed was not relevant anymore, and there's not much left!
user_preferences_attribute_group.dart: different text style and compact title, no more reordering

The goldens have changed:
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following assertion was thrown while running async test code:
Golden "goldens/user_preferences_page-blue-dark.png": Pixel test failed, 43.86% diff detected.
Failure feedback can be found at
/home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/failures
When the exception was thrown, this was the stack:
#0      SmoothieFileComparator.compare (file:///home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/utils/goldens.dart:44:7)

(elided one frame from package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:22 +0 -1: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected blue / dark [E]
Test failed. See exception logs above.
The test description was: blue / dark
00:22 +0 -1: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected blue / light
00:22 +0 -1: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected blue / dark
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test (but after the test had completed):
Expected: Text contrast should follow WCAG guidelines
Actual: <Instance of 'WidgetTester'>
Which: Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
When the exception was thrown, this was the stack:
#0      fail (package:test_api/src/expect/expect.dart:137:31)
#1      _expect. (package:test_api/src/expect/expect.dart:112:9)

(elided 5 frames from dart:async and package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:23 +0 -1: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected blue / light
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following assertion was thrown while running async test code:
Golden "goldens/user_preferences_page-blue-light.png": Pixel test failed, 43.87% diff detected.
Failure feedback can be found at
/home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/failures
When the exception was thrown, this was the stack:
#0      SmoothieFileComparator.compare (file:///home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/utils/goldens.dart:44:7)

(elided one frame from package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:23 +0 -2: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected blue / light [E]
Test failed. See exception logs above.
The test description was: blue / light
00:23 +0 -2: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / dark
00:23 +0 -2: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected blue / light
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test (but after the test had completed):
Expected: Text contrast should follow WCAG guidelines
Actual: <Instance of 'WidgetTester'>
Which: Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
When the exception was thrown, this was the stack:
#0      fail (package:test_api/src/expect/expect.dart:137:31)
#1      _expect. (package:test_api/src/expect/expect.dart:112:9)

(elided 5 frames from dart:async and package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:23 +0 -2: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / dark
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following assertion was thrown while running async test code:
Golden "goldens/user_preferences_page-brown-dark.png": Pixel test failed, 43.86% diff detected.
Failure feedback can be found at
/home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/failures
When the exception was thrown, this was the stack:
#0      SmoothieFileComparator.compare (file:///home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/utils/goldens.dart:44:7)

(elided one frame from package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:23 +0 -3: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / dark [E]
Test failed. See exception logs above.
The test description was: brown / dark
00:23 +0 -3: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / light
00:23 +0 -3: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / dark
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test (but after the test had completed):
Expected: Text contrast should follow WCAG guidelines
Actual: <Instance of 'WidgetTester'>
Which: Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
When the exception was thrown, this was the stack:
#0      fail (package:test_api/src/expect/expect.dart:137:31)
#1      _expect. (package:test_api/src/expect/expect.dart:112:9)

(elided 5 frames from dart:async and package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:23 +0 -3: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / light
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following assertion was thrown while running async test code:
Golden "goldens/user_preferences_page-brown-light.png": Pixel test failed, 43.87% diff detected.
Failure feedback can be found at
/home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/failures
When the exception was thrown, this was the stack:
#0      SmoothieFileComparator.compare (file:///home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/utils/goldens.dart:44:7)

(elided one frame from package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:23 +0 -4: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / light [E]
Test failed. See exception logs above.
The test description was: brown / light
00:23 +0 -4: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected green / dark
00:23 +0 -4: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected brown / light
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test (but after the test had completed):
Expected: Text contrast should follow WCAG guidelines
Actual: <Instance of 'WidgetTester'>
Which: Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
When the exception was thrown, this was the stack:
#0      fail (package:test_api/src/expect/expect.dart:137:31)
#1      _expect. (package:test_api/src/expect/expect.dart:112:9)

(elided 5 frames from dart:async and package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:24 +0 -4: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected green / dark
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following assertion was thrown while running async test code:
Golden "goldens/user_preferences_page-green-dark.png": Pixel test failed, 43.86% diff detected.
Failure feedback can be found at
/home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/failures
When the exception was thrown, this was the stack:
#0      SmoothieFileComparator.compare (file:///home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/utils/goldens.dart:44:7)

(elided one frame from package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:24 +0 -5: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected green / dark [E]
Test failed. See exception logs above.
The test description was: green / dark
00:24 +0 -5: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected green / light
00:24 +0 -5: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected green / dark
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test (but after the test had completed):
Expected: Text contrast should follow WCAG guidelines
Actual: <Instance of 'WidgetTester'>
Which: Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
Multiple nodes with the same label: Not important
When the exception was thrown, this was the stack:
#0      fail (package:test_api/src/expect/expect.dart:137:31)
#1      _expect. (package:test_api/src/expect/expect.dart:112:9)

(elided 5 frames from dart:async and package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:24 +0 -5: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected green / light
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following assertion was thrown while running async test code:
Golden "goldens/user_preferences_page-green-light.png": Pixel test failed, 43.87% diff detected.
Failure feedback can be found at
/home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/failures
When the exception was thrown, this was the stack:
#0      SmoothieFileComparator.compare (file:///home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/utils/goldens.dart:44:7)

(elided one frame from package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
00:24 +0 -6: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/pages/user_preferences_page_test.dart: UserPreferencesPage looks as expected green / light [E]
Test failed. See exception logs above.
The test description was: green / light
00:24 +0 -6: loading /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/plural_translation_test.dart
00:25 +0 -6: loading /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/plural_translation_test.dart
00:25 +0 -6: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/plural_translation_test.dart: Plural test aa plural test
00:25 +0 -6: /home/runner/work/smooth-app/smooth-app/packages/smooth_app/test/plural_translation_test.dart: Plural test aa plural test
════════

Makes sense @monsieurtanuki the goldens have to be re-generated

Thank you @teolemon @M123-dev @jasmeet0817  for your code review!
I'm going to implement what I suggested to @M123-dev about similar buttons for the preference page.
I'll send you a screenshot.

What do you think of that?

I like that

Thank you @M123-dev!
Beyond that, we should probably do the same for the "Settings" item lower in the page.

To keep it consistent, yes, but that many buttons in one column probably doesn't look so good again.

Fair enough. I don't know if there are mock-ups.

I'll forward this to the UX Team

Looks fairly good to me. Lets see what the UXers say


add suport to extra volumes and also bump to the latest mm version

Adding support to user can add extra volumes
bump the mm version

it is good to have tests :)

@jwilander done

@cpanato this is good to merge right?


Could this package be used together with laravel/cashier-paddle?

This isn't an issue, but more a question/discussion (discussions tab is disabled):
I've stumbled upon this great package while looking for a "usage-engine" to replace my home-grown one in a side project. I love how flexible soulbscription is.

quote features
tickets
different periodicity_type

My problem: The project already uses laravel/cashier-paddle to handle billing and subscriptions.
cashier-paddle already exposes a subscription-method on the Model, that would use HasSubscriptions. So I run into a FatalError when adding the trait to the User-model for example.
The table name clash with my existing app, but that can be solved by overrding the $table-property and using my own version of the Subscription-model.
So long story short:

Do you have any guidance on how the package could be used together with laravel/cashier-paddle/laravel/cashier?
Is there a way to "just" use the feature consumption part of the package?

Haven't invested much time yet, so maybe this can all be solved in "userland". But maybe someone here already has the perfect solution for this.
Thanks again for publishing this package and sharing how a usage-engine can be built. ❤

Quick update: I got the package to work with laravel/cashier-paddle by overriding some methods, renaming a table and bringing my own model.
A quick dump of all the changes made.
Change the name of the to be migrated table.
- Schema::create('subscriptions', function (Blueprint $table) {
+ Schema::create('soulbscription_subscriptions', function (Blueprint $table) {

Create a SoulbscriptionSubscription-model that extends the default Soulbscription Subscription-model and update the used table name.
namespace App\Models;

use Illuminate\Datbase\Eloquent\Model;
use LucasDotVin\Soulbscription\Models\Subscription;

class SoulbscriptionSubscription extends Subscription
{
    protected $table = 'soulbscription_subscriptions';
}

Use the new model in config/soulbscription.php.
use App\Models\SoulbscriptionSubscription;

return [
    'models' => [
        'subscription' => SoulbscriptionSubscription::class,
    ],
];

The tricky part was adding HasSubscriptions to my User/Billable model.
Through Trait Conflict Resolution I've renamed the subscription-method from the HasSubscriptions-trait to something different.
I've then overriden the subscribeTo, consumeNotQuotaFeature and loadSubscriptionFeatures-method to use soulbscriptionSubscription instead of just subscription.
 class User extends Authenticatable implements MustVerifyEmail
 {
     use Billable;
+    use HasSubscriptions {
+        Billable::subscription insteadof HasSubscriptions;
+        HasSubscriptions::subscription as soulbscriptionSubscription;
+    }

     protected function consumeNotQuotaFeature(Feature $feature, ?float  $consumption = null)
     {
         $consumptionExpiration = $feature->consumable
+            ? $feature->calculateNextRecurrenceEnd($this->soulbscriptionSubscription->started_at)
             : null;

         $featureConsumption = $this->featureConsumptions()
             ->make([
                 'consumption' => $consumption,
                 'expired_at' => $consumptionExpiration,
             ])
             ->feature()
             ->associate($feature);

         $featureConsumption->save();

         return $featureConsumption;
     }

     public function subscribeTo(Plan $plan, $expiration = null, $startDate = null)
     {
         $expiration = $expiration ?? $plan->calculateNextRecurrenceEnd($startDate);

         $graceDaysEnd = $plan->hasGraceDays
             ? $plan->calculateGraceDaysEnd($expiration)
             : null;

+        return $this->soulbscriptionSubscription()
             ->make([
                 'expired_at' => $expiration,
                 'grace_days_ended_at' => $graceDaysEnd,
             ])
             ->plan()
             ->associate($plan)
             ->start($startDate);
     }

     protected function loadSubscriptionFeatures(): Collection
     {
         if (! is_null($this->loadedSubscriptionFeatures)) {
             return $this->loadedSubscriptionFeatures;
         }

+        $this->loadMissing('soulbscriptionSubscription.plan.features');

+        return $this->loadedSubscriptionFeatures = $this->soulbscriptionSubscription->plan->features ?? Collection::empty();
     }

Overriding package methods is obviously not the best solution.
Maybe the package could expose a getSubscriptionsRelationshipName-method to allow package consumers to change the used relationship name without overriding core methods.
I might give this a try in a fork and propose a PR if this is something you would be interested in. Will also do some research how other package authors solve this problem.

Hey! Hello, @stefanzweifel! Thanks for the comments! I'm flattered you're enjoying using this package. 😅 You've made very good points here, perhaps Soulbscription needs some updates to be more modularized (so you could use only the feature consumption handling, for instance) and to be compatible with already existing solutions from the Laravel ecosystem. I'm gonna start looking for a viable way to do it, but every contribution is totally welcome! Once more, thanks, man! 🚀

Hey @lucasdotvin,
Thanks so much for this fantastic package! 🫶
I'm using Laravel Spark and encountering the same issues that @stefanzweifel mentioned. Is there any workaround for this? Overriding package methods isn't an option for me, unfortunately. 😅
Best,
Alex


Replace ThreadLocalRandom with a L64X128MixRandom RandomGenerator

This improves performance by 4x.
Also fixed stuck object rendering, such as arrows, displaying inconsistently.
Closes #23.

For some reason, I encountered some very unusual spawn behaviour where I was spawned at around y=0 in a mineshaft, but I couldn't get this to occur again.

Dropped itemstacks with more than 2 of the same item have some jitter. This does not occur with singular dropped items, and seems to happen at random intervals.

Seems like thunder is also broken, because the random int used for it never is 0.

Just pushed a fix for item rendering.

The items work fine now, but I just discovered that mineshaft generation is very... chaotic, and seemingly infinite? What's happening is that tonnes of mineshafts are generating next to each other, completely ignoring the structure rules (and greatly reducing chunk generation performance for me). This also affects Badlands Mineshaft generation as well. No other structures are affected.

Alright, I'll take a look!

I think I'll add a new implementation of Minecraft's Random interface for cases where it breaks. That way we can just inject that class into the start of broken methods, replacing the faster random class.

Hi @AnOpenSauceDev, could you check if the latest commit works without issues for you as well?
Mineshafts shouldn't generate everywhere anymore, visual issues should be fixed, and enchantments should be predictable again.
I haven't done any benchmarking yet, could you check how this performs, compared to vanilla, on your system?
I'll do some testing as well when I have time.

Just tried your new commit out, and for some reason the block rotation and item shuffling has returned, and enchantments still seem to be inaccurate. Structures do generate properly again. Not sure if something has gone wrong on my end though.

Ah, you're right. Also happens on my end now. Weird that it didn't happen for me yesterday.

I believe I've found a fix that actually works now. It's not as clean as I'd like it to be, since it involves effectively replacing classes, but at least it might work as it should.
My benchmark results seem to be slower than vanilla though?
// Benchmark
		var nanoTimeRandomGeneratorRandomStart = System.nanoTime();
		var randomGeneratorRandom = new RandomGeneratorRandom(RandomSeed.getSeed());
		for (int i = 0; i < 100000; i++) {
			randomGeneratorRandom.nextInt();
			randomGeneratorRandom.nextLong();
			randomGeneratorRandom.nextDouble();
			randomGeneratorRandom.nextFloat();
			randomGeneratorRandom.nextBoolean();
			randomGeneratorRandom.nextGaussian();
		}
		var nanoTimeRandomGeneratorRandomEstimated = System.nanoTime() - nanoTimeRandomGeneratorRandomStart;

		var nanoTimeVanillaStart = System.nanoTime();
		var vanillaRandom = new CheckedRandom(RandomSeed.getSeed());
		for (int i = 0; i < 100000; i++) {
			vanillaRandom.nextInt();
			vanillaRandom.nextLong();
			vanillaRandom.nextDouble();
			vanillaRandom.nextFloat();
			vanillaRandom.nextBoolean();
			vanillaRandom.nextGaussian();
		}
		var nanoTimeVanillaEstimated = System.nanoTime() - nanoTimeVanillaStart;

		LOGGER.info("RandomGeneratorRandom: {}s, vanilla: {}s", nanoTimeRandomGeneratorRandomEstimated / 1e9,
				nanoTimeVanillaEstimated / 1e9
		);

With L128X128MixRandom, this returns RandomGeneratorRandom: 0.0229267s, vanilla: 0.0173085s.
It's supposed to be 4x faster than vanilla though.

With L128X128MixRandom, this returns RandomGeneratorRandom: 0.0229267s, vanilla: 0.0173085s. It's supposed to be 4x faster than vanilla (CheckedRandom). Is my benchmarking code bad?

It could be that one or more random functions are much slower compared to vanilla, so it would be better to benchmark every method separately, instead of doing it all at once.

Odd, the new generator is consistently slower vs. vanilla.
# int
RandomGeneratorRandom: 0.019367281s, vanilla: 0.007450953s

# long
RandomGeneratorRandom: 0.025516993s, vanilla: 0.012274628s

# double
RandomGeneratorRandom: 0.023700025s, vanilla: 0.010885982s

# float
RandomGeneratorRandom: 0.022416038s, vanilla: 0.00581613s

# bool
RandomGeneratorRandom: 0.019014472s, vanilla: 0.006581874s

# guassian
RandomGeneratorRandom: 0.023590226s, vanilla: 0.023925273s

huh. This keeps getting weirder.
I'll ask around in the Fabric Discord server.

@Steveplays28 Actually, I found a fix, you were accidentally using L128x128MixRandom, which was significantly slower than L64X128MixRandom. After doing that, I got roughly 2x the performance compared to vanilla.

Oh, nice! Great that you found the issue.
Is everything working correctly on your end as well, in terms of all the issues that were present before?

Yep! Everything works correctly.

Nice! One last thing I could do then, is test if replacing some new CheckedRandom(seed) calls would work.
In the world generator, there's quite a few of these instantiations. Might help with gaussian-related functions.
If it does break stuff though, we can always choose not to include it.
Is terrain generation currently consistent?

I'll test it out now, but at a glance worldgen looks like vanilla.

Can confirm that worldgen is 1:1 when using the same seed.

Awesome! That's great progress.
Do you want to try replacing calls in the world generator? Could do that in a followup PR, alongside another followup PR for a docs update.
I'll mark the PR as ready for review, if you don't haven't found any other issues.

This improves performance by 2x

Just wrote up a benchmark, it's actually anywhere from 4x -> 8x faster, depending on the generator used.
The new benchmark also a bit more detailed, and only executes on dev.


Camel case declared properties with single letter in the middle are being ignored

Camel case declared properties with single letter in the middle are being ignored. This behaviour has been introduced somewhere around 1.2.3, because in 1.0.0, 1.1.0 and 1.1.3 it works as expected. If this is not considered a bug then information about the new behaviour should be included in the documentation.
For example: a boolean variable named alignYAxis will be ignored when added to the element code:
<chart alignYAxis>a very informative chart goes here</chart>

Polymer({
  is : 'fusion-chart'
  properties: {
    alignYAxis: Boolean
  }
});

but alignAxis works as expected:
<chart align-axis>an even more informative chart goes here</chart>

Polymer({
  is : 'fusion-chart'
  properties: {
    alignAxis: Boolean
  }
});

Looks like this change was introduced in 1.2.2 as a result of the mirco-optimizations, I think specifically of this change here: https://github.com/Polymer/polymer/commit/acdd242616f77616f1f3f90e0389c4c98161bcb4
We used to do dash-case to camel-case when processing the attributes, but now we build up a _propertyInfo object using the camelCaseToDashCase function, which doesn't handle consecutive capital letters.
I'd definitely argue it's a bug, since it's a) a change in behavior, and b) the camelCaseToDashCase function doesn't correctly reverse the dashCaseToCamelCase function in case-map.html.

@arthurevans Looking at the git history, it appears that the camelCaseToDashCase function never worked with 2 uppercase characters in sequence. Is that correct?
Renaming of file
Caching of conversions
Moving the function again
First version of the function

This doesn't seem like a bug per the docs:

When mapping attribute names to property names:
Attribute names are converted to lowercase property names. For example, the attribute firstName maps to firstname.
Attribute names with dashes are converted to camelCase property names by capitalizing the character following each dash, then removing the dashes. For example, the attribute first-name maps to firstName.

In this case an attribute name of alignYAxis would have a corresponding property name of alignyaxis due to the first rule:
<chart alignYAxis>a very informative chart goes here</chart>

Polymer({
  is : 'chart'
  properties: {
    alignyaxis: Boolean
  }
});

If you truly want a camel cased property name, you'd need to take advantage of the second rule by changing your attribute name to align-y-axis:
<chart align-y-axis>a very informative chart goes here</chart>

Polymer({
  is : 'chart'
  properties: {
    alignYAxis: Boolean
  }
});

@jimsimon you are right. my example was flawed, I've edited my first post to make it precise. I also made this plnkr for illustration purposes: http://plnkr.co/TmCQ8WS9d19jULFohSaE

Fixed in #3279


show average mmr

the match overview sums the player mmrs; it should average them instead, like the client does. the sum is fairly useless when not everyone displays their mmr

Could do.  I'm storing MMR in a separate table now keyed by match ID.

Checked the code and this requires a bit of a structure change.  Probably going to hold off (and just do this for new UI).


stf.pl fails with path name too long on Windows

Running test SharedClassesWorkloadTest_Softmx_Increase_JitAot_0 ...
===============================================
SharedClassesWorkloadTest_Softmx_Increase_JitAot_0 Start Time: Wed Jan  2 04:03:25 2019 Epoch Time (ms):<PHONE_NUMBER>962
variation: NoOptions
JVM_OPTIONS:  -Xcompressedrefs
Uncaught exception from user code:
	mkdir C:/Users/jenkins/workspace/Test-extended.system-JDK8-win_x86-64_cmprssptrs/openjdk-tests/\TestConfig\test_output_15464227613621\SharedClassesWorkloadTest_Softmx_Increase_JitAot_0/20190102-040326-SharedClassesWorkloadTest_Softmx_Increase_JitAot/debug: No such file or directory; The filename or extension is too long at C:/Users/jenkins/workspace/Test-extended.system-JDK8-win_x86-64_cmprssptrs/openjdk-tests///..//jvmtest\systemtest\stf\stf.core\scripts\stf.pl line 324.
	File::Path::_mkpath(HASH(0x9b82c0), ARRAY(0x9b83f8)) called at C:/Strawberry/perl/lib/File/Path.pm line 154
	File::Path::mkpath("C:/Users/jenkins/workspace/Test-extended.system-JDK8-win_x86-"...) called at C:/Users/jenkins/workspace/Test-extended.system-JDK8-win_x86-64_cmprssptrs/openjdk-tests///..//jvmtest\systemtest\stf\stf.core\scripts\stf.pl line 324
STF 04:03:26.681 - =========================   S T F   =========================
systemtest-prereqs has been processed, and set to: C:/Users/jenkins/workspace/Test-extended.system-JDK8-win_x86-64_cmprssptrs/jvmtest/systemtest/systemtest_prereqs
SharedClassesWorkloadTest_Softmx_Increase_JitAot_0_FAILED

https://ci.eclipse.org/openj9/view/Test/job/Test-extended.system-JDK8-win_x86-64_cmprssptrs/123/tapResults/

The name of the failing tests are indeed unnecessarily long in the playlist. The simple solution of this error would be to update the test names into reasonable and shortened alternatives.

Note: the problem was not reproducible at Adopt:  https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/713/console

In openj9, the path is longer with job name Test-extended.system-JDK8-win_x86-64_cmprssptrs, whereas a shorter job name Grinder is used above at Adopt. We are comparing a different path length here. A further investigation may be needed.

The new names should work in the regular builds as well, since the new names have been made shorter than SharedClassesWorkloadTest_Softmx_Increase - which worked successfully on the same machine where the others failed: https://ci.eclipse.org/openj9/view/Test/job/Test-extended.system-JDK11-win_x86-64_cmprssptrs/120/tapResults/


Is it possible to replace the % symbol ? It is too tiny for me

I don't currently have a way to replace existing glyphs, but I will take a look at adding that feature.
I agree, the % symbol is odd with its closed circles.

Thank you very much @kiliman ! Please reply here when you will replace, I can't see another way of being updated with the news from you.

Have you done any changes to the % gliph ? Let me know please !

How does this look?

The first one looks awesome !! Very balanced with the digits, the second one is difficult to distinguish right away. The first is the good choice.

Ha. The 2nd one is the current Operator Mono one. I was just showing it in comparison.
Not a big fan of the closed circles, so I see why you would like a replacement.

Thank you, @kiliman :))

Here's what the alternate % sign looks like in VS Code.

I have added support in latest build on branch features/contextsubst. This allows replacing existing glyphs with alternates.
Since the alternate percent glyph is optional, you will need to add a custom profiles.ini file in the ./original folder. This is how you can define custom fonts.
[default]
percent=percent.alt

The format of the profiles.ini file is:
# optional comments
[profile]
# map glyph to an alternate
glyph=altglyph
# don't add this glyph to the font
!glyph

You can have more than one profile. The profile name is appended to the name of the font (except for default). This way you can create different fonts with different ligatures, etc. for specific languages. So if you have a [Go] profile, the font would be Operator Mono SSm Lig Go.
You can also disable certain ligatures if you want. For example, if you don't like the == glyph, just add: !equal_equal.liga
If you want to try the alternate ligatures, you can do: less_equal.liga=less_equal.2.liga
Look in the glyphs folder to see what alternates are available.
Let me know if you have any questions.

Closed by 2de4cec227ea2971ebefd8665ad2d9792eb7d5d0 and 094662aef66d0a2072127b9865c30f557b928435

Thank you @kiliman

Please use the develop branch. I've merged the feature branch and deleted it.

I will
mie., 24 iul. 2019, 17:07 Kiliman<EMAIL_ADDRESS>a scris:

Please use the develop branch. I've merged the feature branch and deleted
it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kiliman/operator-mono-lig/issues/85?email_source=notifications&email_token=AIPZH4JSD62IKB2KJJVVZWDQBBOYHA5CNFSM4HXP3WKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2WOIBI#issuecomment-514647045,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIPZH4MOV6AHPWXLDAZJYXTQBBOYHANCNFSM4HXP3WKA
.


[Feature request] Move FOV slider to the video settings.

Should be placed next to the FOV Effects slider because it would fit there nicely and there is also an empty space for a button so it would be symmetrical now.

Would play nicely when the realms button in options is hidden so only these buttons would be visible.

Like this


Fixed singular and plural for category names

Fixed singular and plural for category names of the management commands.

Here is an example of this small issue.

Singular category name is now shown for the help text of a command. @zootalures


Will not build for me

I cannot get this code to build for me. The ReadMe says to modify the Proxy.java file, but there's no indication how it's supposed to be modified. Proxy.java is where all the errors are.

I got it to run by adding these to the Proxy (Thread) class:
public InputStream clientIn;
public OutputStream clientOut;
public InputStream serverIn;
public OutputStream serverOut;
And by importing this:
import java.io.InterruptedIOException;
Now it runs but it seems to stop all web browsing. It is not clear to me if the proxy is actually configured, or if I must make it myself, how to let some traffic through, how to prevent other traffic, etc? Can I view more than just URLs? Can I view, for example, the content of a webpage?

This just converts all traffic into a socket in which you can handle everything from their. If you want to route it traffic through a SOCKS proxy I recommend using my other project.
https://github.com/DrBrad/JTun2Socks

This just converts all traffic into a socket in which you can handle everything from their. If you want to route it traffic through a SOCKS proxy I recommend using my other project.
https://github.com/DrBrad/JTun2Socks


Floating label support

Is your feature request related to a problem? Please describe.
It would be very useful to get floating labels like this: https://getbootstrap.com/docs/5.1/forms/floating-labels/#selects
Describe the solution you'd like
Floating labels support.

Yes, it will look great.

We created one by some css.
But it's not really floating label as Boostrap 5.2 is not also supported floating labe on form-select. They support only input, textarea.
I hope you have this feature. Then great!


Added documentation on publication buttons

I did not find the custom bibtex keywords documented anywhere, so I've added them to the main readme under a details tag.

thanks a lot for contributing to the documentation!


🐞 - TuiFilter - not updated component state when use the same control more than once

Reproduction url
https://stackblitz.com/edit/angular-stgx3sqd
Description
When I'm using the same control more the once and try to select control value - another component with the same control does't change the state.
And another case:
If on component 1 select value and on the component 2 - select another value - value will rewrited.
More clarified:
Step: 1
Comp1 - select value "Text 1"
formValue result: [{ "text": "Text" }]
active badge only on Comp1
Step 2
Comp2 - select value "Text 2"
AS IS
formValue result: [{ "text": "Text2" }]
active badge on Comp1 - "Text", on Comp2 - "Text2"
TO BE
formValue result: [{ "text": "Text" }, { "text": "Text2" }]
active badge on Comp1 - "Text" and "Text2", on Comp2 - "Text" and "Text2"
Taiga UI version
4.17.0
Browser Used
Chrome
OS Used
macOS

Apparently this is Angular bug, updating form control does not trigger any event for another component using the same formControl (should call its writeValue):
https://stackblitz.com/edit/stackblitz-starters-435ebnom
https://github.com/angular/angular/issues/43484


Set config.json search path lazily after changing into workDir

Fixes #1150. After this PR, the behavior if --workDir is not specified will be the same, but if --workDir is specified, then config.json will be searched for in the specified working directory rather than whatever directory PufferPanel happens to start in. (This is especially useful when running as a Windows service, since those start up in the System32 directory with no apparent way to override that behavior.)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I tested this manually on Linux and it seems to work fine. Still need to test on Windows (though there shouldn't be anything OS-specific about this change).


Play travis

Added files as requested on page 12 of Методические рекомендации (add template)

Workflows are added. I don't know why workflow is failed.

Resolved. 1+1=2

Errors are resolved in test.py


Terminal tab is blank on Windows 10

Issue Type: Bug
The terminal of my VSCode suddenly stopped working. Now is blank and I can't do anything on it. I'm using Windows 10 and this hasn't happened to me before.
I use the Git Bash as a default bash profile. I event tried uninstalling, deleting all the setting/extensions files and installing it again, but still doesn't work.
VS Code version: Code 1.62.3 (ccbaa2d27e38e5afa3e5c21c1c7bef4657064247, 2021-11-17T08:11:14.551Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
AMD Athlon 3000G with Radeon Vega Graphics      (4 x 3493)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.93GB (2.55GB free)

Process Argv
--crash-reporter-id 11b925f1-12ac-4c5e-8be8-ef55afb4f735

Screen Reader
no

VM
0%

Extensions: none
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
pythonrunftest32:30373476
pythonf5test824:30373475
javagetstartedt:30391933
pythonvspyt187:30373474
vsqsis200:30402083
vsaa593:30376534
vssld246cf:30401891
vscexrecpromptt2:30404948
vscop804:30404766
vs360:30404995

I looked into the developer tools and I saw these errors.

I went to that directory and exactly there isn't a node_modules directory. (I already have enabled the Explorer feature to see hidden files/directories)

This looks suspicious and conflicts with the extension list you posted:

Does it happen when you close all windows and run code --disable-extensions?

Yes, I just reloaded it in that way and I got the same problem.

I've got the same issue!
Version: 1.62.3 (user setup)
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T08:11:14.551Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043
First noticed yesterday. At some point it suddenly worked again, no idea why. This morning, gone again.
Terminal section is blank, trying to open a fresh terminal via the plus, the keyboard shortcut or the menu does nothing (also no further error messages in the dev tool console).
I made no changes to the configuration for weeks, if not months, and I noticed this problem first yesterday, and only on one of my machines.

Update: It seems an erratic thing, did not work at all yesterday, today I started VScode, no terminal. Had it running in the background for a while and looked at it again - terminal is there.

Some times it works and some times it doesn't.

I have same issue after update vscode, so I tried reinstall older version.
July 2021 (v1.59) was OK and problem reproduced on August 2021 (v 1.60).
until someone fix this issue, just using v1.59 is one of option i think...

Can anyone confirm whether this happens after closing all windows and running code --disable-extensions? I can't reproduce.

I'm on 1.63.2 now and it has not happened for some time.


Update dependencies

Please be noted that:

This package will require Node >=5 to run Buffer.from(). cson requires "node": ">=10", tho. So I think it doesn't matter.
It is going to merge from my branch "dev" to your "master".
"Allow edits" is enable. Feel free to add commits.

Thanks, merged and published as 1.1.0


Add #[track_caller] in all assertion functions

is this still relevant?

#[track_caller] does not support async fn yet (https://github.com/rust-lang/rust/issues/110011) so some assertion functions in tests can not use it. Since what is left it is only related to test cases, we can close it.


[question] Can you post your DXC.EXE command for Raytracing.hlsl to Raytracing.hlsl.h

Can you post your DXC.EXE command for Raytracing.hlsl?
DXC is brand new to me and there isn't a lot of information for it on the internet.  I don't get the same compiled shader using the following;
dxc -T lib_6_3 -Zpr test/Raytracing.hlsl -Fc test/Raytracing.hlsl.h

You'll find most of the relevant information on it's GitHub site.
The version of DXC.EXE you are using is likely the one from the Windows 10 SDK. Which one do you have installed?

I am using the latest version from GitHub.  I don't get the #if 0 and #endif or the g_pRaytracing[] = { ... in my file compared to yours.  I am sure I am just leaving an option off or using the wrong option, but honestly, the -help file is not very helpful in figuring this out.

Your original command-line works with this file:
//--------------------------------------------------------------------------------------
// RaytracingLibrary.hlsl
//
// Single HLSL file containing a Ray Generation, Miss, Any-Hit and Closest Hit Shader
// Compiled as a single /Tlib_6_3 DXIL shader library.
//
// Advanced Technology Group (ATG)
// Copyright (C) Microsoft Corporation. All rights reserved.
//--------------------------------------------------------------------------------------

RaytracingAccelerationStructure Scene : register(t0);
RWTexture2D<float4> renderOutput : register(u0);

cbuffer Params : register(b0)
{
	uint dispatchWidth;
	uint dispatchHeight;
    uint rayFlags;
    float holeSize;
};

struct RayPayload
{
	float dummy;    // Minimum of 4 bytes required for payloads.
};

[shader("raygeneration")]
void RayGenerationShader()
{
	// Orthographic projection, just as if we were already in NDC.
	float2 vpos = DispatchRaysIndex().xy;
	float3 rayOrigin = float3(-1, 1, -5);

	rayOrigin.xy += float2(2, -2) * (vpos / float2(dispatchWidth, dispatchHeight));

	float3 rayDir = float3(0, 0, 1);

	RayDesc myRay = { rayOrigin, 0.0f, rayDir, 100.0f };
	RayPayload payload = { 0.0f };

	uint missShaderIndex = 1;
	TraceRay(Scene, rayFlags, ~0, 0, 0, missShaderIndex, myRay, payload);
}

[shader("anyhit")]
void AnyHitShader(inout RayPayload payload, in BuiltInTriangleIntersectionAttributes attr)
{
    float3 barycentrics = float3(attr.barycentrics.xy, 1 - attr.barycentrics.x - attr.barycentrics.y);
    float3 triangleCentre = 1.0f / 3.0f;

    float distanceToCentre = length(triangleCentre - barycentrics);

    if (distanceToCentre < holeSize)
        IgnoreHit();
}

[shader("closesthit")]
void ClosestHitShader(inout RayPayload payload, in BuiltInTriangleIntersectionAttributes attr)
{
    float3 barycentrics = float3(attr.barycentrics.xy, 1 - attr.barycentrics.x - attr.barycentrics.y);
	renderOutput[DispatchRaysIndex().xy] = float4(barycentrics, 1);
}

[shader("miss")]
void MissShader(inout RayPayload payload)
{
	renderOutput[DispatchRaysIndex().xy] = float4(0, 0, 0, 1);
}


react-native-permission: NativeModule.RNPermission is null

What's happening?

How can it be reproduced?

Build details?

I just installed the library, Issue I had with permissions was that it was locking the version to 2. when the latest docs are on v3.
Try out the following steps and let me know if it works for you.
firstly uninstall the libraries
npm uninstall react-native-qrcode-scanner
npm uninstall react-native-permissions
Then in this order
npm install react-native-permissions (check your package.json you have version 3.0.0, the repo was locking me 2.3)
npm install github:moaazsidat/react-native-qrcode-scanner (The owner of the repo has not updated the npm link so you are getting the old version)
Update you podfile
permissions_path = '../node_modules/react-native-permissions/ios'
pod 'Permission-Camera', :path => "#{permissions_path}/Camera" (Or whatever permission you want here)
Pod install
And run :) Goodluck

For me the problem was appearing because I couldn't install pods, in readme it says to paste this in podfile:
permissions_path = '../node_modules/react-native-permissions/ios'
pod 'Permission-Camera', :path => "#{permissions_path}/Camera .podspec "
but actually permissions should be without .podspec

Just merged a PR with the update to the readme, thanks for the catch!

Just merged a PR with the update to the readme, thanks for the catch!


Optimization: cache results between TypeScript projects

Towards https://github.com/sourcegraph/scip-typescript/issues/175
Previously, scip-typescript didn't cache anything at all between TypeScript projects. This commit implements an optimization so that we now cache the results of loading source files and parsing options. Benchmarks against the sourcegraph/sourcegraph repo indicate this optimization consistently speeds up the index command in all three multi-project repositories that I tested it with.

sourcegraph/sourcegraph: ~30% from ~100s to ~70s
nextautjs/next-auth: ~40% from 6.5s to 3.9
xtermjs/xterm.js: ~45% from 7.3s to 4.1s

For every repo, I additionally validated that the resulting index.scip has identical checksum before and after applying this optimization. Given these promising results, this new optimization is enabled by default, but can be disabled with the option --no-global-cache.
Test plan
Manually tested by running scip-typescript index tsconfig.all.json in the sourcegraph/sourcegraph repository. To benchmark the difference for this PR:

Checkout the code
Run yarn tsc -b
Go to the directory of your project
Run node PATH_TO_SCIP_TYPESCRIPT/dist/src/main.js
Copy the "optimized" index.scip with cp index.scip index-withcache.scip
Run node PATH_TO_SCIP_TYPESCRIPT/dist/src/main.js --no-global-caches
Validate the checksum is identical from the optimized output shasum -a 256 *.scip

Very nice! How did you recognize that this approach of caching the SourceFile values would help speed up type-checking?


refactor: gas distribution in transfer call

Legacy gas distribution is not good because gas use of ft_transfer_call or nft_tranasfer_call itself is a  static value. This may cause panic when developers wrap this method and add their own logic which increase the gas use.
So I think we should remove static gas for ft_transfer_call or nft_transfer_call itself. Instead, we use gas weight to distribute the gas, that is more flexible and can solve previous problem.
Currently, I set xx_on_transfer : xx_resolve_transfer = 9 : 1 and attach a static gas 10 T for resolver because resolver is more important and decrease its panic risk.
I am not sure 9 : 1 is good or not, we can disscuss.

This change will cause log print when nft_transfer_call failed due to exceed gas.


Featured Item Component

Component demo:
https://eea.github.io/volto-kitkat-frontend/?path=/story/components-item--default-item

@g-stamatis why is this component added in the spreadsheet?
It seems to be that the featured item is already tracked by this ticket
https://github.com/eea/volto-eea-design-system/issues/14


UNC paths not resolved even with host on whitelist or setting fully disabled

Does this issue occur when all extensions are disabled?: No, issue occurs in extension. I reported the issue to the extension and was told it is an issue with VS Code. Note that my repro steps are slightly different as I simplified them, but they have the same effect.

VS Code Version: 1.79.2 and Insider's
OS Version: Windows 10 21H2 Build 19044.2788

Steps to Reproduce:
unc_package_dir.zip

Install Python extension and Pylance extension
Extract attached ZIP file to a local and UNC location.
Open the unc_package_dir folder from the UNC path in VS Code. Confirm that you want to add the UNC host to the whitelist permanently.
Open file test.py in editor, once the analysis completed after a few seconds, note that import some_package is indicated as an error. Under Problems note the message  [unc_package_dir.zip](https://github.com/microsoft/vscode/files/11824504/unc_package_dir.zip) Import "some_package" could not be resolved

Now repeat 3-5 but for the unc_package_dir in the local folder location. Note that the Import "some_package" could not be resolved does not appear here.

@philnagel what is your exact entry for the UNC setting? And does it reproduce even after a restart?

Thank you, I think that particular extension is closed source so it is hard to know what's going on for end users.
I do most of my day to day work using the Remote - SSH extension connecting from macOS to Windows. For this test, I am just running locally to rule out anything related to the remote extension. I see the same issue in both.

Any difference when you define an environment variable NODE_UNC_HOST_ALLOWLIST with the value of arcdev?
How does a UNC path look like typically that fails for you?

I still see the "unresolved" message from Pylance with that environment variable set.

Well but in that case you need to allow arcserver1, no?

Correct. The above example was for my testing setup which I was keeping separate from my production settings to rule out any interactions. For testing, I had the folder at \\arcdev\dev\unc_package_dir with the settings shown in my previous reply.

This does indeed work as you describe, showing the additional folders.

Oh nice, this is a step forward! Now we need to learn what the PyLance extension is doing differently.

I am able to reproduce this issue.

@philnagel curious if you can reproduce the issue using our exploration builds which contain a newer runtime:
https://az764295.vo.msecnd.net/exploration/28a8c1f1d373c22f8e69c66cbbae246a1179279e/VSCode-win32-x64-1.82.0-exploration.zip

@bpasero Trying this out but it seems like Pylance is not operating at all in the build you linked. I am not getting any Intellisense or anything. Even with logging set to Trace, this is the only output shown for the Python Language Server:
2023-08-02 10:06:19.287 [info] (Client) You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. You may not: work around any technical limitations in the software that only allow you to use it in certain ways; reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; use the software in any way that is against the law or to create or propagate malware; or share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.
The build suggested the pre-release version of the Python extension so I tried that first, then switched to release. Both have the same result.

@philnagel the runtime update has landed in VS Code insiders, so please try with https://code.visualstudio.com/insiders/ now.

This bug has been fixed in the latest release of VS Code Insiders!
@philnagel, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version 54821ee1f14beca4866abd7de86175b4794b030d of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Happy Coding!

I'm testing on this version of Insider's:
Version: 1.85.0-insider (user setup)
Commit: b3a649fe52c0fb8692c9b28dfe25227c97521884
Date: 2023-11-15T09:43:13.091Z
Electron: 25.9.4
ElectronBuildId: 25127168
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

and I am still seeing this issue (logs: 2023-11-15 09:29:25.log)
[{
	"resource": "/dev/unc_package_dir/test.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": {
		"value": "reportMissingImports",
		"target": {
			"$mid": 1,
			"path": "/microsoft/pyright/blob/main/docs/configuration.md",
			"scheme": "https",
			"authority": "github.com",
			"fragment": "reportMissingImports"
		}
	},
	"severity": 4,
[2023-11-15 09:29:25.log](https://github.com/microsoft/vscode/files/13366623/2023-11-<IP_ADDRESS>.log)

	"message": "Import \"some_package\" could not be resolved",
	"source": "Pylance",
	"startLineNumber": 1,
	"startColumn": 8,
	"endLineNumber": 1,
	"endColumn": 20
}]

@philnagel I attempted to repro the issue today, I can repro it in latest stable whereas it works fine in latest insiders attaching recording below, let me know if I missed some steps
https://github.com/microsoft/vscode/assets/964386/238b7328-6e37-4c2c-924f-c526017451a8

@deepak1556 I think I found the difference - in my case I initially had the security.restrictUNCAccess property set to false and in that case, I am still seeing the issue in the latest Insider's build.
https://github.com/microsoft/vscode/assets/17130646/aa665bb2-8f3a-4046-b516-72e7f1466cb5
However, when I set security.restrictUNCAccess to true and instead accept the unc host in the prompt as allowed, the issue goes away.
https://github.com/microsoft/vscode/assets/17130646/8e69589c-7cac-4f66-a749-3adb68eb6a25

Thanks for clarifying, I can confirm the bug with that setting disabled.

@philnagel can you give the latest insiders another try, it should now respect the setting Security: Restrict UNCAccess with the python extension.


Enable webpack watch

Fixes #28
Let webpack watch and rebuild when new changes happen in files in app directory. Also trigger electron to reload once a new build is ready.
Changes proposed in this pull request:

Enable the webpack watch option with npm run watch.
Add electron-reload package.
Let electron reload itself once a new change is built by webpack.
Keep package.json list of packages sorted.

@Venkat5694 nice catch!
I added electron-is-dev package to check for that.

@mohamed-moanis The issue will still occur but this time the package electron-is-dev will be missing in the production build. This package needs to be moved to dependencies from dev-dependencies. And an environment variable needs to be added in the Dev start script.

@Venkat5694 envvar only needed when you want production act as development according to the docs:

Can be overridden by setting the ELECTRON_IS_DEV environment variable to 1.


fix: proper Partial typing

Using TypeVar("T", bound=Type[BaseModel]) as the type variable in Partial does not type-check.
For example:
class Person(BaseModel):
    name: str

PartialPerson = Partial[Person]  # does NOT type-check
PartialPerson = Partial[Type[Person]]  # type-checks

This PR changes the type variable used in Partial from TypeVar("T", bound=Type[BaseModel]) to TypeVar("T", bound=BaseModel) and subsequent types in Partial as needed to allow PartialPerson = Partial[Person] to type-check 🤡
For context, I enjoy using Pyright in its strictest configuration. If somehow this was ok by MyPy, then please ignore this PR.
BTW, Partial is brilliant! Typescript has a similar idea:
type Partial<T> = {
    [P in keyof T]?: T[P];
};

It's unfortunate Python can't express it in this way, but we make do!

Thanks 😃,
Yes I am a TypeScript developer as well. So thats the source of inspiration here.

Released as v1.0.5


Invalid swing_mode

Hello,
I have been working on a script (HA script) to set the swing mode of my LG ThinQ HVAC. For this I use the climate.set_swing_mode service. The YAML file looks as follows:
alias: Example
sequence:
  - service: climate.set_swing_mode
    data:
      swing_mode: "Horizontal Center"
    target:
      entity_id: climate.air_conditioning_air_care
mode: single
icon: mdi:bed-empty

In order to get to this point, I looked through the code to determine what the value should be of the swing_mode data parameter. This is what I could make out of the code. However the problem is that once I try to run this script, I receive the following error message: Invalid swing_mode [Horizontal Center].
 But is this a mistake on my part (and if so, what would be the solution) or is there something else going on?

Available swing modes are exposed in the entity attribute swing_modes. You can use the develoment tools to consult entities attributes values.
I think that in your case the right value is HorizontalCenter (without space).
I close this because not an integration issue.


[Fine] Fixauth handles serialized objects

Allow fix_auth to work on databases that have objects serialized in them

@jrafanie so if --exit-on-error defaults to true then you have to pass --no-exit-on-error ?

@jrafanie so if --exit-on-error defaults to true then you have to pass --no-exit-on-error ?

Good point. I don't like how trollop does no-....   I see why you did --resilient.  How about --allow-failures or something like that

--allow-failures or something like that
@jrafanie

done

Ah, I didn't see the comments here before I merged the PR to master ... were there issues you wanted addressed there @Fryguy @jrafanie ?

closing - this is too late to be backported to Fine


Add Benjamin-Ono equation

If the Hilbert transform of the second partial derivative is diagonal in some basis, then time-evolution could be taken care of using a fourth-order time-stepper for stiff PDEs, like this.

Would have to be the rational basis since soliton solutions have 1/x decay, probably LaurentDirichlet:
S=LaurentDirichlet([-Inf,Inf])
isdaig(Hilbert(S))    # returns true

On 18 Dec 2015, at 3:57 AM, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
If the Hilbert transform of the second partial derivative is diagonal in some basis, then time-evolution could be taken care of using a fourth-order time-stepper for stiff PDEs, like this https://peoplemathsoxacuk/trefethen/publication/PDF/2005_111pdf
—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/SingularIntegralEquations.jl/issues/64.

We could start with a large periodic domain to compare with this:
http://www.diva-portal.org/smash/get/diva2:617038/FULLTEXT01.pdf
I think the solitons decay as 1/x^2 on the real line right?
Cheers,
Mikael

On Dec 18, 2015, at 1:12 AM, Sheehan Olver<EMAIL_ADDRESS>wrote:
Would have to be the rational basis since soliton solutions have 1/x decay, probably LaurentDirichlet:
S=LaurentDirichlet([-Inf,Inf])
isdaig(Hilbert(S)) # returns true

On 18 Dec 2015, at 3:57 AM, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
If the Hilbert transform of the second partial derivative is diagonal in some basis, then time-evolution could be taken care of using a fourth-order time-stepper for stiff PDEs, like this https://peoplemathsoxacuk/trefethen/publication/PDF/2005_111pdf
—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/SingularIntegralEquations.jl/issues/64.

—
Reply to this email directly or view it on GitHub.

Why do we need diagonal operators?  Can't we just do a rational approximation of the exponential and use ?
Sent from my iPhone

On 18 Dec 2015, at 12:47, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
We could start with a large periodic domain to compare with this:
http://www.diva-portal.org/smash/get/diva2:617038/FULLTEXT01.pdf
I think the solitons decay as 1/x^2 on the real line right?
Cheers,
Mikael

On Dec 18, 2015, at 1:12 AM, Sheehan Olver<EMAIL_ADDRESS>wrote:
Would have to be the rational basis since soliton solutions have 1/x decay, probably LaurentDirichlet:
S=LaurentDirichlet([-Inf,Inf])
isdaig(Hilbert(S)) # returns true

On 18 Dec 2015, at 3:57 AM, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
If the Hilbert transform of the second partial derivative is diagonal in some basis, then time-evolution could be taken care of using a fourth-order time-stepper for stiff PDEs, like this https://peoplemathsoxacuk/trefethen/publication/PDF/2005_111pdf
—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/SingularIntegralEquations.jl/issues/64.

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.


🎨 remove Fullscreen button from editor toolbar

closes https://github.com/TryGhost/Ghost/issues/8480

removes fullscreen button from toolbar but keeps the "fullscreen" routines so that styling and other behaviour doesn't need to be updated
side-by-side toggle now toggles fullscreen on/off (previously only toggled fullscreen on)

Coverage increased (+0.07%) to 72.752% when pulling 702dec8b1235b4f9a5802dba51996a3c78b0ff62 on kevinansfield:remove-fullscreen-button into ddc8aed370e14f9dfa9d5e1544474d56afb7288c on TryGhost:master.


Authentication with Apple Developer Portal failed!

Build/Submit details page URL
No response
Summary
When I try to run git:(dev-alt) ✗ npx eas build --platform ios --profile development it fails because of Authentication with Apple Developer Portal failed!
The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined
Managed or bare?
managed
Environment
System:
  OS: macOS 15.2
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 20.13.1 - ~/.nvm/versions/node/v20.13.1/bin/node
  Yarn: 1.22.17 - /usr/local/bin/yarn
  npm: 10.8.3 - ~/.nvm/versions/node/v20.13.1/bin/npm
  Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
  CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
IDEs:
  Android Studio: 2020.3 AI-203.7717.56.2031.7583922
  Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
  @expo/metro-config: ^0.18.8 => 0.18.11
  expo: ^51.0.38 => 51.0.38
  expo-router: ~3.5.23 => 3.5.24
  react: 18.2.0 => 18.2.0
  react-dom: 18.2.0 => 18.2.0
  react-native: 0.74.5 => 0.74.5
npmGlobalPackages:
  eas-cli: 13.1.1
Expo Workflow: managed

Error output
Learn more: https://docs.expo.dev/distribution/security#keychain
✖ Logging in...
Authentication with Apple Developer Portal failed!
The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined
Reproducible demo or steps to reproduce from a blank project
I don't know how reproduce this.

Getting the same error
Was working this morning and then stopped working in the evening time

@SeanNFT I tried like 10 times, and a minute ago it started working again - maybe a global issue? Nevertheless it started the build so I hope it gets through.

related to https://github.com/expo/eas-cli/issues/2651 but this is happening on 13.3.0

@ilyadynin been trying for quite a few hours lmao and it's just after working thankfully.
Major pain when it does happen

There were some items I needed to fill out in the app store connect portal, but even after agreeing to new terms I was still not able to proceed.
After 30 minutes of trying, I reverted to version v13.2.3 and I was able to submit a build successfully.

@TimelyToga it started working for everyone 10 mins ago, prob just expo server  / apple server issue, those are all private repos

Same.

I've been attempting to build all day but haven't been able to due to this issue. Any updates on this?

I've been attempting to build all day but haven't been able to due to this issue. Any updates on this?

Keep trying. It eventually starts working again.

Oh, this seems like a bug on our end. At least providing a better error message would be helpful. Can you run the command with EXPO_DEBUG=1 so I can see a full stack trace?

@szdziedzic I am also getting this error when running eas device:create
EAS is an awesome set of tools! Let me know if I can provider more info.

I'm still getting this a week later. Any updates?

@szdziedzic Here are the relevant pieces of the error code for me:

Internal Server Error: 'h', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later. Service errors:
- Verification codes can’t be sent to this phone number at this time. Please try again later.'. Retrying after 3 seconds (remaining: 3)

✖ Logging in...
Authentication with Apple Developer Portal failed!
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later. Service errors:
- Verification codes can’t be sent to this phone number at this time. Please try again later.
Error: Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later. Service errors:
- Verification codes can’t be sent to this phone number at this time. Please try again later.
    at t.getAppleResponseError (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:856522)
    at block (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:864570)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async O (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:865082)
    at async I (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:863935)
    at async t.requestAsync (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:862471)
    at async t.idmsaRequestAsync (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:736419)
    at async t.requestAuthAsync (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:751126)
    at async t.handleTwoFactorAuthentication (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:745676)
    at async Object.w [as loginWithUserCredentialsAsync] (/Users/timbo/Library/Application Support/fnm/node-versions/v18.16.0/installation/lib/node_modules/eas-cli/node_modules/@expo/apple-utils/build/index.js:1:728315)```

    Whenever I get this error it's usually because there is some stupid agreement update / terms that I need to sign. It would be nice if we got a more descriptive error message in that case and this case. I wouldn't keep trying if I could have just seen this error the whole time.

Any updates on this issue ? I am still getting constantly that error and can't make the build
Ok, I tried downgrading the eas-cli to the node js and nothing fixes it
eas-cli/14.0.2 linux-x64 node-v22.11.0
`Internal Server Error: 'h', 'Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later. Service errors:

Verification codes can’t be sent to this phone number at this time. Please try again later.'. Retrying after 3 seconds (remaining: 3)

✖ Logging in...
Authentication with Apple Developer Portal failed!
Received an internal server error from Apple's App Store Connect / Developer Portal servers, please try again later. Service errors:

Verification codes can’t be sent to this phone number at this time. Please try again later.
Error: build command failed`

hi there, this should be resolved - please refer to: https://github.com/expo/eas-cli/issues/2698#issuecomment-2532459498
if this doesn't resolve your issue, please create a new issue with detailed information.

I also have a Developer Portal error
✔ Logged in New session
✔ Select a Team › IdentaFly LLC - Company/Organization (xxxx)
✔ Select a Provider › IdentaFly LLC (xxxx)
✖ Couldn't switch to provider IdentaFly LLC (xxxx)
Authentication with Apple Developer Portal failed!
Apple 401 detected - You are either not logged in, your account doesn't have access to the requested data, or the page doesn't exist
    Error: build command failed.


Use fixed-length paths in memifproxy

In memifproxy we create unix sockets with path containing connection id.
https://github.com/networkservicemesh/sdk-vpp/blob/7780191e4f39fc2b3ccfb1968d534da85c59460e/pkg/networkservice/mechanisms/memif/memifproxy/client.go#L82-L84
This is an easy way to ensure that every connection has its own unique socket, but it has drawbacks.
Unix sockets are limited in length. On linux the limit is 108.
Connection IDs are not limited in length, and paths that contain them can easily exceed this limit. Related issue: https://github.com/networkservicemesh/deployments-k8s/issues/1826
To ensure reliable behavior we must not use any variable length strings when defining paths.
We have several possible solutions for this:
Solution 1
Use relative paths.
I don't think is an appropriate solution because in order to use relative path to a file in a certain directory we would need to change current working directory, and this is basically incompatible with multithreading.
Solution 2
Keep [connection id -> uuid] map in memifproxy, and use these uuids for socket paths.
Solution 3
Use short symlinks to sockets with potentially long paths.
This is basically identical to second solution, because we would still need to keep mapping from connection id to its symlink, so I believe it's overly complicated without any real benefits.
Conclusion
I think that the only suitable solution here is the second: use mapped uuids for socket paths.
It would also be pretty easy to implement.
There is still another unknown-length part of the path: os.TempDir(). Temp directory is usually just /tmp by default, but it is not guaranteed. For example, it seems like on MacOS default temp dir is relatively long (48 symbols). And, of course, users can set temp dir to be whatever they want.
We can probably say that very long temp dir path is just an invalid configuration for a program that uses memifproxy.

Solution2 looks good to me.
@edwarnicke Can you also have a look at the issue and share your thoughts?

Keep [connection id -> uuid] map in memifproxy, and use these uuids for socket paths.

Which is state we will lose when we heal :(

Use short symlinks to sockets with potentially long paths.
symlinks will break grpcfd in terms of passing them between Pods

Use relative paths.

You are correct about the issues for this within NSM.  However, VPP's api runs in a single worker thread.  It may very well be doable to upstream code to VPP that does the relative path trick.

In the immediate term: why are we ever setting the connection id manually in any of our things like cmd-nsc ?

Which is the state we will lose when we heal :(

Basically, memif chain element is using in next places

client
forwarder
endpoint

Let's consider death cases:

client died -- nothing to heal
forwarder/endpoint died -- we need to re-create memif folder with the socket on the forwarder/endpoint side.

it seems solution 2 can be used.
Did I miss something?

In the immediate term: why are we ever setting the connection id manually in any of our things like cmd-nsc ?

In the immediate term: why are we ever setting the connection id manually in any of our things like cmd-nsc ?

Note: we are setting id manually because we want to not see issues on NSC restarting.

@denis-tingaikin What issues would we see on NSC restarting if we didn't manually set its connection ID?

@edwarnicke

resources leaking on forwarder, manager, and etc. Resouces will be not disposed of until token expiration. This problem may be critical of client restarting to a short frequency. (Imagine a ton of interfaces on the forwarder side)
In the case of external clients we need also to identify the sidecar client as init container client.

Can't reproduce the problem. MemifProxy client has been deleted in this PR. MemifProxy server doesn't have this problem.


How to disable console messages?

Whenever I load from persistent storage, I'm getting a handful of console messages:

Is there any way to turn this off?

@themeteorchef Thanks! Sorry about that. Leftover debugging messages that I accidentally committed. They've been removed in v0.4.3 which i've just released.

No worries, thanks for the quick patch :)


Fix set initialization, set.OnlyCapsuleModeIsInvalid could be garbage

Your great patch is much appreciated. We are considering to apply your patch into the SoftEther VPN main tree.
SoftEther VPN Patch Acceptance Policy:
http://www.softether.org/5-download/src/9.patch
You have two options which are described on the above policy.
Could you please choose either option 1 or 2, and specify it clearly on the reply?

Option 1, I allow you to apply this patch into Packetix VPN.

Thank you so much for your contribution to enrich the SoftEther VPN source code.
Your patch has been merged on the main source-tree of SoftEther VPN.
As a token of our gratitude, your GitHub username has been added on the AUTHORS.TXT file and on the header of the related source file.
Please see: https://github.com/SoftEtherVPN/SoftEtherVPN/blob/master/AUTHORS.TXT
Thanks again for your contribution.


Reorganize coordinator <=> worker communication

In broad strokes, this...

Moves the lifting / lowering logic out of a centralized location and puts it nearer to each specific command.
Removes the concept of the "job" message and its vector of subcommands in favor of single messages.
Flattens the enums sent between the two components.
Introduces the Multiplexed type and demultiplexer.

As before, these are my ideas. I've liberally used unwrap / expect / panic! to get things into the shape I want. Happy to discuss details.

This design looks much more flexible and elegant.

It seems that we just need to return operation error from worker, add error handling in coordinator and finish all TODOs.
Plus some cleanup. Then it's good to go.

Oh, I see that Some TODOs are from previous code.

I'm working on adding error handling.
And found that there are plenty of places in worker where we should report errors back to coordinator.
E.g. Unable to write file at specific path and read nonexistent file.
One thing puzzling me is that should we just use a String to represent errors of all operations?
If we do so, they will all share the same error context selector in coordinator.
Or we create an Error type for each kind of operation?
In this approach, how can we properly wrap inner Error like std::io::Error and also make it (de)serializable?
By the way, is there a convenient method of wrapping non-Error value in my custom Error using SNAFU?
As an example, oneshot::Sender<T>.send() returns Result<(), T>.
Since T doesn't implement Error trait, it cannot be a source of another Error as usual.
How can I use ? on this result if the function's return type is my custom Error enum?

I'm working on adding error handling.

I apologize; I didn't know what you were working on so I've already taken steps towards that.

One thing puzzling me is that should we just use a String to represent errors of all operations?
If we do so, they will all share the same error context selector in coordinator.
Or we create an Error type for each kind of operation?
In this approach, how can we properly wrap inner Error like std::io::Error and also make it (de)serializable?

I followed your initial ideas and serialized each error to a String (wrapped in a newtype). That error is sent as a separate message.
When we expect a specific response type, we also check to see if the message was an error and wrap that in an error that then later is wrapped in something domain specific.
When streaming, we can also check for errors and pull them out and report them.

Since T doesn't implement Error trait, it cannot be a source of another Error as usual.

There's not really anything great for this.
For MPSC senders, I added this extension trait to change it to a RecvError<()>, discarding the original message.
For oneshot senders, I'd probably do something like .send(...).ok() to convert it to an Option and then use snafu::OptionExt to convert it back to an error (now with no details).

It's okay.
I should apologize for not devoting enough time on this to make some progress.
And I learnt a lot of practices from your well-written commits.

from your well-written commits.

Haha, that's very kind of you, but these are definitely not what I'd call well-written. The commit messages are thrown in last-minute and the contents of the commits are rather haphazard.


Finalise VPC changes work - merge working branch to main

User Story

During CIDR change migration the below branch has been used to apply changes locally, this has prevented unmigrated environments from being impacted.
BRANCH CIDR-changes-working-branch
Value

Questions / Assumptions

Definition of done

[ ] CIDR-changes-working-branch merged to main and all environments tested
[ ] CICD for all environments has been reactivated

Reference
How to write good user stories

https://github.com/ministryofjustice/modernisation-platform/pull/1345