where to set adapter.config.maxAttempts

Hello,
I saw the ability if the adapter to retry sendCommand-attempts if the device is unreachable. This is done up to MAX_ATTEMPS times. this value may be overwritten by the adapter.config.maxAttempts variable. But where can I set this variable in the adapter-config-pane?
My scenraio is, that I have some unstable connections to some lights. When I use a script to emulate activity for a vacation absence, it is very bad to have some switching commands not to come through. I need the adapter to retry the sendCommand indefinitely until the device is reachable and the commands went through.
So my hope is to set the adapter.config.maxAttempts variable somewhere to a very high number to reach this behaviour. Where can this be found? Or is this feature possible to be implemented (resulting in indefinite retries)?
Cheers
Sebastian

It is simply not implement in the adapter configuration interface. I can provide this though.

Hi @Zefau, this would be really great and much appreciated. I think overall, this improves switching reliability.

Currently no further development isplanned for this adapter. Please use ioBroker.hue.


import funder identifiers and metadata

The dataone graph will hopefully have many references to funders through metadata documents that link to global funder identifers from the CrossRef Funder registry, and from the ROR system. Both are made available as data dumps:

Funder registry (in RDF): https://gitlab.com/crossref/open_funder_registry/-/blob/master/registry.rdf
ROR (in JSON): https://doi.org/10.6084/m9.figshare.c.4596503.v9

I think it would be helpful to:

Load both of these graphs
Where possible, provide sameAs links across the graphs
Use the graph to be able to provide contextual relationships for querying (e.g., summarize all datasets from NSF, or from GEO programs in NSF)

While the ROR graph isn't in RDF, its highly structured and provides very nicely structured cross-references to other identifier types like WikiData IDs, ISNI, etc.
Being able to report based on funders has long been a goal of ours, and getting all of this accessible in a queryable form would be really helpful.

Also, note that those data dumps are updated periodically, so we can both reimport periodically, and they each have a REST API as well.


Post release automated changes for communication releases

Post release automated changes for azure-rest-communication-messages

API change check
API changes are not detected in this pull request.


llvm-kompile crashes with bad error when #Ceil rule is added

I'm not sure if I'm using the #Ceil rule correctly, but I've marked it symbolic and still the LLVM backend is crashing with an uninformative error.
At the very least, the error should be made more informative about the problem. But I also think:

Marking it symbolic should mean the LLVM backend ignores it.

We should be able to send #Ceil rules to the LLVM backend and have it ignore them.

K commit: 4a011c920 - haskell-backend/src/main/native/haskell-backend: b3c17111 - Fix sorting bugs around RulePattern (kframework/kore#1787) (kframework/k#1251)

LLVM backend commit: fa4c44f - fix non-exhaustiveness bug (#324)

K Definition:
module FIXED-INT
    imports INT
    imports BOOL

    syntax FInt ::= FInt ( value: Int , one: Int ) [klabel(FInt), symbol]
 // ---------------------------------------------------------------------
    rule #Ceil(FInt(... value: V, one: O)) => { V >=Int 0 andBool O >Int 0 #Equals true } [anywhere, symbolic]
endmodule

Error output:
/home/dev/src/mkr-mcd-spec-dev/deps/k/k-distribution/target/release/k/lib/../bin/llvm-kompile: line 44: 59186 Segmentation fault      (core dumped) "$(dirname "$0")"/llvm-kompile-codegen "$definition" "$dt_dir"/dt.yaml "$dt_dir" $debug > "$mod"
org.kframework.utils.errorsystem.KEMException: [Error] Critical: llvm-kompile returned nonzero exit code: 139
Examine output to see errors.
        at org.kframework.utils.errorsystem.KEMException.create(KEMException.java:126)
        at org.kframework.utils.errorsystem.KEMException.criticalError(KEMException.java:39)
        at org.kframework.backend.llvm.LLVMBackend.accept(LLVMBackend.java:76)
        at org.kframework.kompile.KompileFrontEnd.run(KompileFrontEnd.java:74)
        at org.kframework.main.FrontEnd.main(FrontEnd.java:62)
        at org.kframework.main.Main.runApplication(Main.java:118)
        at org.kframework.main.Main.runApplication(Main.java:108)
        at org.kframework.main.Main.main(Main.java:56)
Makefile:104: recipe for target '.build/defn/llvm/fixed-int-kompiled/interpreter' failed
make: *** [.build/defn/llvm/fixed-int-kompiled/interpreter] Error 113

Kompile command:
kompile --debug --main-module FIXED-INT --backend llvm              \
                 --syntax-module FIXED-INT .build/defn/llvm/fixed-int.k \
                 --directory .build/defn/llvm -I .build/defn/llvm                           \
                 --emit-json                                                      \
                  -ccopt -O2

This is blocked on #1252. Ceil rules are simplification rules and the llvm backend ought to ignore simplification rules, but we need to resolve the issue with or patterns in the function encoding before it will work correctly.

I confirmed that the uninformative error message still happens for this definition. I added the simplification attribute to the problematic rule, and that let it compile.
Is the solution to drop symbolic rules in the same way as we already drop simplification rules in the LLVM backend, or is it to emit a better error somewhere suggesting that this rule needs to have simplification added?

Closed by https://github.com/runtimeverification/k/pull/3053


PEX Not Putting Players in Default Group 1.8

Hi there,
I'm using PEX 1.23.2, and Spigot 1.8.5.
Ever since PEX updated to 1.8 players have not been automatically put into the default permissions group. Only when I manually add the players myself will the default permissions work.
When a new player joins the server they have no permissions whatsoever.
Any help or advice would be greatly appreciated.
Thanks

I found the issue. I guess the way the default group is registered changed.
I had:
groups:
Default:
default: true
When I should have had this
groups:
Default:
options:
default: true


bug(MatTable): trackBy does not differentiate between multiTemplateDataRows templates

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
When using a MatTable with multiTemplateDataRows and trackBy, the provided TrackByFn will be passed the same arguments (index and the row object) for each of the templates for the same row object. This makes it extremely difficult to write a viable TrackByFn when using conditional multiTemplateDataRows via the when option.
Reproduction
By logging the output inside the TrackByFn, we can see that each row template is passed the same arguments (index and row object), and there is no simple way to differentiate between different row templates within the TrackByFn.
A typical use case which is very close to the multiTemplateDataRows example in the MatTable docs shows the issue clearly
Stackblitz example  of a typical use case where the row object unique identifier is used for the TrackByFn.
Steps to reproduce:

toggle the first row 3 times

Expected Behavior
The TrackByFn should be provided with some differentiator per row template. (ideally some way to identify which template the trackBy was triggered for).
In the provided Stackblitz example, it would be expected that when using a typical TrackByFn, that the rows are rendered in the correct position always, instead of occasionally.
Actual Behavior
The TrackByFn is passed the same arguments for each row template per row.
In a typical use case (the provided Stackblitz) the table will misplace the rows under certain conditions, which can be seen by expanding and collapsing the first row a few times, the multiTemplate for the 2nd row will eventually be shown in the first row (video below).
https://user-images.githubusercontent.com/1449302/197506379-ec6051ea-ebea-47ad-9e20-b59ca7b2aa5e.mov
Environment

Angular: 14.2.7
CDK/Material: 14.2.5
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): macOS

Currently the only workaround for this I have found is to use an auxiliary object to keep track of how many times the TrackByFn is called per id, and then appending this value to the returned unique identifier, resetting this auxiliary object whenever the data changes or the rows are toggled.
This solution seems to work fine, but can be very complex and hard to read given more complex situations (for example, with additional conditional row templates)


Add ability to clone attributes of a feature to other features

Fixes #9191
Added an action that clones tags from the first selected entity to all other entities.
Created one base operation that clones a subset of tags.
Created several operations that call the base operation and pass a subset of related tags to clone.
It allows to save time by copying several related tags with one click.
Also added unit tests for those features.

This a base PR for discussion. All operations have the same icon for now. For the shortcuts, there are not enough keys, I'm not sure what to use.
cc @kaligrafy @tahini @greenscientist


pcm-iio reports wrong IB write/read data on iio pcie stack

pcm-iio fails to dump stack "IIO Stack 2 - PCIe0" to get Intel data center max GPU(device id: 0BDB) pcie r/w,  it always zero.
However, the "IIO Stack 1 - DMI" show the corrected data, about 40G.
my cpu model:
model           : 143
model name      : Intel(R) Xeon(R) Gold 6438Y+
results of pcm-iio:

And, it works on Intel(R) Xeon(R) Platinum 8469 CPU @2.00GHz.
Does pcm-iio support all types of SPR? Is there any other iio stack mapping of SPR CPU?
pcm-iio.cpp line 173

this has been fixed some time ago


Run All/Run Dir buttons freeze (animation only)

The first time you load the editor, the run all or run dir buttons seem to freeze (This is probably due to loading resources). They also seem to intermittently freeze up occasionally.
This is animation only. Their functions don't freeze (thankfully).

Had nothing to do with the buttons. Was poor resource management.


About lodash

remix-form is only importing concat and startCase from lodash, but depends on the whole package, which is not tree-shakeable. What about switching to lodash-es or to individual packages (e.g. lodash.concat)? OR... moving away from lodash?
Can do a PR.

Hey @tavoyne , thanks for pointing this out!
I was going to make a little test and ended up creating a PR. Check #63 out ;)

Hey @tavoyne I just published an RC to test the removal of lodash and I'm super happy about the results.
We really appreciate your time and contributions on this one 🥳
Before 😱

After 😌

That's something 🥹
Happy to help!
Why not making react-hook-form a peer dependency while we're at it?

Agree, now that we have a monorepo it'll be easier to do it.
I'm probably not going to be doing it today.
Feel free to either create another issue or even a PR ;D
Cheers

@tavoyne I couldn't help but try your suggestion just to see the results:

Will be publishing soon


Don't Merge! Regression pull request test

Docs Build status updates of commit 9ba1f55:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 9ba1f55:
:clock10: Full build: the average full build time is 18 min(s) 7 sec(s), this is based on the last 189 build(s) for this repository.

Docs Build status updates of commit 9ba1f55:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

TestingPullRequest.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


PLT-7693 get transaction by id

This PR:

Adds the runtime-rest-client endpoint: getTransactionById
Improves the generated documentation of related runtime-rest-client endpoint
Simplifies rest-client-flow.html to avoid repetition and add error handling

@hrajchert can you resolve the conflicts ? and we can merge it


chore: Migrate ESLint and prettier to Biome

This removes everything ESLint[^webpack] and Prettier related from the project, including the config package for eslint and the docs mention.
Reasons why we should migrate away from eslint:

ESLint to run on the entire project will takes literal minutes (10min+ on my pc)
ESLint to run at all even for one file will use more then 1.5 GB of RAM (2GB if we include Virtual Page on Windows, on Linux i did not test the exact memory usage)
The time it takes for lint-staged to run eslint is quite a bit (around 1min on my pc) which is a pretty big annoyance/road block for contributing

Reason to use Biome:

It is reasonably fast (around 600ms to run on the entire project)
It has pretty much the same rules as ESLint even if some do not are a direct copy and others are "inspired" (as per the term the biome documentation uses) so they have the same concept applied in a different thing
Format and Lint can be a single command*
It is written in rust (To be clear: this is a joke, not an actual reason)

*: Currently the old fmt scripts are now biome format and lint scripts are biome lint. Should we use check on the lint or fmt (or both) scripts instead? (check will run both format and lint)

[!NOTE]
This does not include examples/bigbot as it has its own formatter

[^webpack]: website/yarn.lock still has some eslint packages, because apparently Webpack depends on some eslint packages

Though, I wonder if we should merge other PRs before this one or merge this PR before others first if we decided to merge this?

I think the only pr that will need some work to merge in if this gets merged before that one is the refactor pr since it is for a good part literally an eslint and prettier run, however i think that by doing a rebase i should be able to resolve merge conflicts fairly trivially. Others PRs, yes might have some conflicts especially for the import sorting biome does, but should be a faily easy conflict to resolve

Small issue i have found yesterday i didn't notice before: yarn and biome fight for the format of the package .json
This isn't much of an issue (i hope) however it is worth mentioning, especially if dependabot will format the file the yarn way. We can either disable biome for the package.json(s) or find a way to disable the yarn formatting of the package.json


Switch to BIO_snprintf to avoid missing symbol problems on Windows

It seems the snprintf() call introduced in https://github.com/openssl/openssl/commit/3372039252c4d9c67de784a0fbdad5589991a347 fails to compile for some windows builds. I've replaced with OpenSSL's own BIO_snprintf() which is available on all platforms.

Just need to confirm that appveyor passes now.

@slontis looks good

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Thanks for fixing.. Merged to master

Unsubscribe please
Sent from my iPhone

On Feb 5, 2021, at 02:10, Shane<EMAIL_ADDRESS>wrote:

Closed #14063.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Restructure

is this ongoing work ? looks very interesting with the pywidgets support and more.
i'm curious to enable jbang.dev style support to ijava or possibly different kernel so curious if better to base of this PR rather than the older master/main ?


Stub new methods

Description
https://github.com/PaperMC/Paper/commit/69950d5a6a22908368bf081c5006ec36d176fd14
Checklist
The following items should be checked before the pull request can be merged.

[ ] Unit tests added.
[x] Code follows existing code format.

Info on creating a pull request

Make sure that unit tests are added which test the relevant changes.
Make sure that the changes follow the existing code format.

For maintainer
When a PR is approved, the maintainer should label this PR with release/*.

If the PR fixes a bug in MockBukkit, update the patch version. (if the current version is 0.4.1, the new version should be 0.4.2)
If the PR adds a new feature to MockBukkit, update minor version. (if the current version is 0.4.1, the new version should be 0.5.0)

Note that a PR that fixes an UnimplementedOperationException should be considered a new version and not a bugfix.

The build looks to be failing because it thinks the new methods don't exist, which is weird because they do, and it compiles fine locally.

Making the action run the build task with --refresh-dependencies fixes the build issue, but once it's removed it fails to build again.

Looks like Gradle finally figured out there's a new version of Paper.


Update data.sql

US #1: add horse names in database

/tina - can you have a look at this?

/tina - done


Punch cache_dir through model factory / builder / pretrain helpers

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


List-Formatting/view-samples /project-gantt-chart Issue

I have created all the columns with the appropiate format, and a final one named "Gantt" with the .JSON file, but it doesn´t seem to create the view.
I´ve checked:

All columns names match
Sorting in ascending order by TaskStart

I leave a SS. What could be the issue?

Hi @edqu1001 !

What could be the issue?

project-gantt-chart is a view formatting, not a column formatting. Try applying JSON to the view formatting.

If you want to display a Gantt chart in a column, please try generic-gantt-chart.

HI @edqu1001,
Indeed, you should not create a column "Gantt" but use the code to format the whole view like @tecchan1107 mentioned.
In this article there is a step-by-step guide https://exceltrainer.be/sharepoint/260/ It was written for the previous version of the code, si stick to your own columns and version 2 of the code and you will be fine.
Please let us know if you managed.
Geert

Thank you so much @gdk-max 🙏!!

Solved! Thank you and looking forward to new updates! :) It would be nice if a commented version of the code could be made so we know how to modify small parameters as sizes, lenght, etc.

Hi,
Yes, the comment about commenting is valid. I have tried to add a little bit of comments, but the json-code itself doens't allow commenting.
I have actually commented my original code, by adding the "_comment" tag, but that seems to be removed here since it is not really a comment but a label that is not supported and therefore ignored.
Geert


release

Hi,
Are you planning to release the TwFA anytime soon? Btw the article is very interesting and i would love to test it!

Thanks for attention! The code will be released soon!

Thanks a lot! I have a question about the setup of the experiment. How many test set images do you use to calculate FID for COCO-stuff and VG?

You can refer to this link.


[Build Transaction] Added operations

Added operation description and docs URL
Some refactoring to improve operation field validation and XDR formatting
Added the following operations:

Payment
Manage Sell Offer
Manage Buy Offer
Create Passive Sell Offer

Preview is available here:http://laboratory-pr843.previews.kube001.services.stellar-ops.com/

Question: for 'Payment operation, we save native asset related value in its fields, but we don't do the same thing for Alphanumeric 4 or Alphanumeric 12. Why is that?

Question: for 'Payment operation, we save native asset related value in its fields, but we don't do the same thing for Alphanumeric 4 or Alphanumeric 12. Why is that? This is the behavior in our current lab.

Thanks for the question, @jeesunikim ! :raised_hands: The values for non-native asset inputs are cleared when the type changes because the values can't be used interchangeably. For example, an Alphanumeric 4 asset code is not a valid Alphanumeric 12 asset code, and vice versa.


Strip control codes in Text.append_tokens

Type of changes

[x] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[x] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[x] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
Fixes #3014
Strip control codes in Text.append_tokens similar to Text.__init__ and Text.append

This appears to workaround the issue rather than fix it. It doesn't take in to account cell length.
Appreciate the PR, but I think we will solve this a different way.


BDD for busy people questions blog

@theo-england I believe Google's algorithms look favourably upon us if we link to the original post in our copy. If they see us posting copies of other peoples content without attribution, they may down-grade us as a reliable source.
Just add a paragraph at the bottom saying "This article was originally posted here" with a link to the AWA blog post.

I think that link should be rel=canonical as well...
Maybe we could add a field to the metadata that does this automatically?
https://blog.kissmetrics.com/myths-about-duplicate-content/

@theo-england did you work out how to do this? Shout if you want a hand.

@mattwynne I added the AWA link to the top, but didn't manage the "rel=canonical" bit. Wasn't sure how to do this in markdown. Trial and error by pull request is quite frustrating and time-consuming. Not sure if there is a way around this? -https://cucumber.io/blog/2017/03/07/matt-wynne-courage-and-comittment

@theo-england I fell back to a regular HTML link to do it: 71204ad19dda133d58a8c36f81aefe8c4bc7a2b3


New version of openshift playbooks better s3 support

LGTM - Also reminds me I need to do this and abstract out the registry role completely! Nice work


.Net: Test a model that has function calling (i.e., aws-llama-2-7b-chat-hf-function)

Test another model with function calling support to make sure that it works with existing funtion calling abstractions. Need to use hugging face deployment (ask Matthew for keys)

Summary - Existing abstracts are sufficient with regards to describing functions, but the json structure and model interactions diverge.
JSON schema for function descriptions diverge:

Function description
Prompt construction
Function invocation: model and pattern

Function Description
Not structural differences, ability to express enum, and required parameters.
Open AI
[
  {
    "type": "function",
    "function": {
      "name": "get_current_weather",
      "description": "Get the current weather in a given location",
      "parameters": {
        "type": "object",
        "properties": {
          "location": {
            "type": "string",
            "description": "The city and state, e.g. San Francisco, CA",
          },
          "unit": {"type": "string", "enum": ["celsius", "fahrenheit"]},
        },
        "required": ["location"],
      },
    },
  }
]

llama-2
{
  "function": "get_current_weather",
  "description": "Get the current weather in a given location",
  "arguments": [
    {
      "name": "location"
      "type": "string",
      "description": "The city and state, e.g. San Francisco, CA",
    },
    {
      "name": "unit"
      "type": "string",
      "description": "The temperature unit: cesius or fahrenheit",
    }
  ]
}

Prompt construction
The function calling for Llama2 appears to be more deeply integrated with prompt construction:
<s>[INST] <<SYS>>
You are a helpful research assistant. The following functions are available for you to fetch further data to answer user questions, if relevant:

{
	"function": "get_current_weather",
	"description": "Get the current weather in a given location",
	"arguments": [
		{
			"name": "location"
			"type": "string",
			"description": "The city and state, e.g. San Francisco, CA",
		},
		{
			"name": "unit"
			"type": "string",
			"description": "The temperature unit: cesius or fahrenheit",
		}
	]
}

To call a function, respond - immediately and only - with a JSON object of the following format:
{
    "function": "function_name",
    "arguments": {
        "argument1": "argument_value",
        "argument2": "argument_value"
    }
}
<</SYS>>

What is the current temperature (F) in Seattle, Washington
[/INST]

Prompt Invocation
The model instructions on how to invoke a function differ structurally (json) as well as the capabilities for repeated or parallel function calling.

You keep your answers short. <</SYS>> Is \"192131\" a prime number?[/INST]
"@

$prompt = $prompt -replace "`r|`n",'\n'

curl https://r5llg6t27ciek1y9.us-east-1.aws.endpoints.huggingface.cloud `
	-X POST  `
	-d "{""inputs"": ""$prompt"", ""parameters"": {""max_new_tokens"": 150}}" `
	-H "Authorization: Bearer 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"  `
	-H "Content-Type: application/json"


Remove old Educates versions from package repository.

Is your feature request related to a problem? Please describe.
The package repository has old versions back to 2.0.0.
Describe the solution you'd like
Keep only versions from last two X.Y versions instead of whole history.
Describe alternatives you've considered
No response
Additional information
No response

Dropping package repository in 3.0


Enable actions for images and other file types in active tab

It  is a current limitation of VS Code that you cannot get the file URI of a tab through the Extensions API for filetypes such as images. There is an open issue to change this. If this change happens, I can update the extension to incorporate this behavior.

Updated all "active" commands to work on all supported filetypes in v2.0.0.


NhostNextProvider broken SSG(static site generation) on NextJS application

I'm trying to use NhostNextProvider on NextJS application.
But once I used the provider, SSG is not working at all.
If I remove it, then everything is fine.
How can I solve this?

Is it the NhostNextProvider that is not working with SSG?
What's the error message?
How do you initialize the nhost instance in src/constants/nhost?

@elitan
we use "next build && next export" and after we made some changes to implement nhostnext and nhostapollo our build outputs aren't static
Working: https://c341871b.designed-platform.pages.dev/
Broken: https://6ce777d6.designed-platform.pages.dev/
When we replaced NhostApollo with the generic Apollo client we were able to get it to work again. It appears the NhostApollo only works with SSR mode.

Hi, @simpson That's right.
Seems NhostNextProvider doesn't work with it.

There is no error message.
And next export completed.
But static pages are generated incorrectly.

Hey! 👋 Thanks for your detailed bug reports.
I'll take a look at this issue later this week and maybe reach out to you to get more information if needed. Thank you for your patience. 🙏

@szilarddoro here is how we temporarily solved it
import { NhostNextProvider } from "@nhost/nextjs";
import { ToastContainer } from "react-toastify";
import { NhostApolloProvider } from "@nhost/react-apollo";
import RedirectMiddleware from "../src/middlewares/RedirectMiddleware";
import "../src/assets/sass/framework.sass";
import "react-toastify/dist/ReactToastify.css";
import "../src/assets/css/tailwind.css";
import "../src/assets/css/skeleton.css";
import { nhost } from "../src/constants/nhost";
import UserProfileContext from "../src/hooks/useUserProfile";
import { ApolloClient, ApolloProvider, createHttpLink, InMemoryCache, useApolloClient } from "@apollo/client";

function MyApp({ Component, pageProps }) {
  const client = new ApolloClient({
    ssrMode: true,
    link: createHttpLink({
      uri: 'https://hovfgsbqgycnxrcmhgvq.nhost.run/v1/graphql',
      credentials: 'same-origin',
    }),
    cache: new InMemoryCache(),
  });

  if(typeof window !== 'undefined') return (
     <NhostNextProvider nhost={nhost} initial={pageProps.nhostSession}>
      <NhostApolloProvider nhost={nhost}>
      <UserProfileContext>
      <RedirectMiddleware>
        <Component {...pageProps} />
        <ToastContainer
          position="bottom-center"
          autoClose={3000}
          hideProgressBar={true}
          closeButton={false}
        />
      </RedirectMiddleware>
    </UserProfileContext>
   </NhostApolloProvider>
  </NhostNextProvider>
  )

  return (
    <NhostNextProvider nhost={nhost} initial={pageProps.nhostSession}>
    <ApolloProvider client={client}>
    <UserProfileContext>
          <RedirectMiddleware>
            <Component {...pageProps} />
            <ToastContainer
              position="bottom-center"
              autoClose={3000}
              hideProgressBar={true}
              closeButton={false}
            />
          </RedirectMiddleware>
          </UserProfileContext>
    </ApolloProvider>
    </NhostNextProvider>
  );
}

export default MyApp;

Yeah this is a tough bug, and I don't think this is a trivial workaround from what I can see. It breaks our Open Graph implementation (social link previews) which we rely on pretty heavily.

I don't know the full answer, but here's more context: https://github.com/vercel/next.js/discussions/12350
Basically there's something not being provided soon enough, and useState / useEffect is usually the culprit

@GavanWilhite ya this is causing all kinds of really strange side effects

@pumpkin46  @simpson do you have a repo I can use to reproduce this issue? I used a bare minimum Next.js project with NhostNextProvider and NhostApolloProvider inside _app and only see statically generated pages.

I created a repository as a starting point for this conversation.
There are two routes fetching data from the server during build (check links to see the result):

/users/mockapi uses the Fetch API in getStaticProps to fetch a list of users
/users/nhost uses the Nhost SDK (GraphQL) to fetch a list of users

The actual build output:
info  - Checking validity of types...
--
11:39:21.605 | info  - Creating an optimized production build...
11:39:36.399 | info  - Compiled successfully
11:39:36.399 | info  - Collecting page data...
11:39:41.248 | info  - Generating static pages (0/5)
11:39:41.328 | info  - Generating static pages (1/5)
11:39:41.339 | info  - Generating static pages (2/5)
11:39:41.348 | info  - Generating static pages (3/5)
11:39:42.018 | info  - Generating static pages (5/5)
11:39:42.028 | info  - Finalizing page optimization...
11:39:42.033 |
11:39:42.060 | Page                                       Size     First Load JS
11:39:42.060 | ┌ ○ /                                      289 B           161 kB
11:39:42.060 | ├   /_app                                  0 B             161 kB
11:39:42.060 | ├ ○ /404                                   193 B           161 kB
11:39:42.061 | ├ ● /users/mockapi                         365 B           161 kB
11:39:42.061 | └ ● /users/nhost (766 ms)                  352 B           161 kB
11:39:42.061 | + First Load JS shared by all              161 kB
11:39:42.061 | ├ chunks/framework-1d23e0fb4601e56d.js   45 kB
11:39:42.061 | ├ chunks/main-c8650c219ef2eb46.js        28.7 kB
11:39:42.061 | ├ chunks/pages/_app-dc0f2a46dc819a74.js  86.4 kB
11:39:42.061 | ├ chunks/webpack-9b312e20a4e32339.js     836 B
11:39:42.062 | └ css/27d177a30947857b.css               194 B
11:39:42.062 |
11:39:42.062 | ○  (Static)  automatically rendered as static HTML (uses no initial props)
11:39:42.063 | ●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)

What else should I add to the reproduction repository?

Thanks for taking a look at this.
(Please correct me if I'm wrong on any of this, I have a surface-level understanding of Next.JS)
So I downloaded your repo repository and it seems like a perfect reproduction. Basically when you right-click -> "View Page Source", "Statically Generated Home Page" is not present in the code. I believe this is the core issue, as for Open Graph tags to work, then need to be rendered early enough such that they would show up in "View Page Source".
As mentioned before, they were showing up there before integrating NhostNextProvider

@szilarddoro
I also just double checked, and yeah if you remove the providers from _app.tsx it then shows "Statically Generated Home Page" in "View Page Source"

@szilarddoro @GavanWilhite it looks like you have a repo reproducing the problem, but if you want to check out our project let me know and I can add you to it.

Thank you for elaborating on this @GavanWilhite. The build output has certainly tricked me.
I can't tell you exactly when we can submit a fix for this issue, but this is surely something we want to have a look at in the near future.
cc. @plmercereau

Sounds good @szilarddoro
In the interest of time, I may be able to give you a head-start here based on what I've learned so far (again, please take what I say here with a grain of salt, I'm not a React expert).
https://github.com/nhost/nhost/blob/9c382a3773e2b6af5c3480fadb65d6ead75e27e0/packages/react-apollo/src/provider.tsx#L18
This line I believe is the proximate cause. Given that it's not returning any children, we are going to see an empty render on first call.
It's doing so because it may not have a client ready. I don't know if there's a way to get react to wait for this.
I think order of preference for fixes is:

Find a way to get the ApolloProvider ready on first render. This will likely involve not using useState, as I believe the setClient call in useEffect makes it wait a frame.

Punt and just return the children directly on first frame. This will mean that usage of the provider will fail, and workarounds will probably be needed, but at least we can feasibly get opengraph tags in by grabbing data another way in getServerSideProps and continue to use the NhostApolloProvider elsewhere.

@szilarddoro Can we get an ETA on this?

Hey @GavanWilhite! We have not made any progress on this since the last time we talked about the topic here.
We are currently quite busy with preparations for our Product Hunt launch, but I'll try to submit a fix for this problem very soon. Probably this weekend or early next week.

It's possible this may also be relevant?
https://medium.com/@A__G__B/component-level-data-fetching-in-next-js-with-srr-8d35cdc5849e

Thanks!! @szilarddoro

Please let me know if the issue persist so we can keep digging.


I got PlatformNotSupportedException when using InTheHand.BluetoothLE in Unity

Hi!
I built my project with Unity editor version 2020. I have successfully imported InTheHand.BluetoothLE.dll version 4.0.22 into that same project. However, when I used Bluetooth.ScanForDeviceAsync, I got a PlatformNotSupportedException, which said that this operation is not supported on this platform. InTheHand.BluetoothLE.dll targets .NET 4.x and my Unity runtime also supports .NET 4.x so I'm not sure what went wrong. I'd really appriciate if you can help me. Thank you in advance!

How are you adding the dll to your Unity project? Have you tried extracting the correct dll manually from the nupkg and referencing that?

Hey, I've encountered a similar issue.
When I install the package using some nuget package manager for unity, it copies the netstandard dll.
When I run the unity project and try to do the following:
using InTheHand.Bluetooth;
using UnityEngine;

public class BLEController : MonoBehaviour
{
    // Start is called before the first frame update
    async void Start()
    {
        var devices = await Bluetooth.ScanForDevicesAsync();
        Debug.Log(devices);
    }

    // Update is called once per frame
    void Update()
    {

    }
}

I get the PlatformNotSupportedException: Operation is not supported on this platform. exception.
If I manually replace the netstandard with net461, I get the following errors in the Unity Editor:
Assembly 'Assets/Packages/ble/net461/InTheHand.BluetoothLE.dll' will not be loaded due to errors:
Unable to resolve reference 'Windows.Foundation.UniversalApiContract'. Is the assembly missing or incompatible with the current platform?
Reference validation can be disabled in the Plugin Inspector.
Unable to resolve reference 'System.Runtime.WindowsRuntime'. Is the assembly missing or incompatible with the current platform?
Reference validation can be disabled in the Plugin Inspector.
Unable to resolve reference 'Windows.Foundation.FoundationContract'. Is the assembly missing or incompatible with the current platform?
Reference validation can be disabled in the Plugin Inspector.

I tried changing the player settings to use .NET Framework, which didn't help.
I'm using Unity on Windows 11 Pro.
I'm not sure what else I can do. Would appreciate some help.

I'm not sure if NuGet in Unity pulls in all the dependencies in the same way as Visual Studio but can you manually add the Microsoft.Windows.SDK.Contracts package as this is required for the .NET Framework dll.

Hey, thanks for the suggestion.
It seems that when I change the Api Compatibility Level to .NET Framework, the nuget package manager is installing the correct dependencies.

Thing is, it looks like not the whole dependency is installed. But it seems that it copies what it thinks is relevant.
For example the System.Runtime.WindowsRuntime.4.6.0 the lib\net45 folder is actually empty also in the full package as well.

I copied the whole Microsoft.Windows.SDK.Contracts into unity:

And the error did disappear, but now when I run the above code, it fails with: TypeLoadException: Failure has occurred while loading a type.
I tried adding also dlls for netstandard but still getting the TypeLoadException when running the code.
Were you ever able to use BluetoothLE in Unity?


Remove jsonld APIs and config.

Interested in feedback wrt FIXME in util.js.
Should the code from jsonld.hasValue be copied here as a helper function.
It's unclear how much code that would involve since hasValue calls other jsonld APIs
https://github.com/digitalbazaar/jsonld.js/blob/master/lib/util.js#L212-L240

We should just reimplement that function without using jsonld. It's just a check to see if name is a certain value or contains a certain value if name's value is an array.

Science behind hasValue helper: https://gist.github.com/mattcollier/6f35a181e4a6f333dfdb9d78ff7b0ddc
If we can get this in bedrock.util we can use it in all the places.


Refactor drawer story state and update drawer footer image for dark theme

Fixes #249.

Changes proposed in this Pull Request:

Refactor state for drawer stories
Update footer images for use with theme toggle

*Notes:

The footer image swaps for the with-footer and full-config stories but there is a knob to change the background color so it's "hardcoded" when the theme is toggled. Should we still swap out the image even though we can't change the "hardcoded" color value? Or is there a way to make a knob default dynamic so we can hardcode the color with respect to the theme?
I'm getting a hooks issue when toggling to the rail variant on the within-a-drawer-layout story :( ... still need to figure that out.

The footer image swaps for the with-footer and full-config stories but there is a knob to change the background color so it's "hardcoded" when the theme is toggled. Should we still swap out the image even though we can't change the "hardcoded" color value? Or is there a way to make a knob default dynamic so we can hardcode the color with respect to the theme?

I haven't tried this before, but you could try using a useEffect hook to respond to a change to the useDarkMode value and then redeclare the knob with a new default value:
const darkMode = useDarkMode();
let bgKnob = color('backgroundColor', Theme.colors.surface) // or whatever colors we want

useEffect(() => {
    bgKnob = color('backgroundColor', Theme.colors.surface) // or whatever color this should be
}, [darkMode]);

The footer image swaps for the with-footer and full-config stories but there is a knob to change the background color so it's "hardcoded" when the theme is toggled. Should we still swap out the image even though we can't change the "hardcoded" color value? Or is there a way to make a knob default dynamic so we can hardcode the color with respect to the theme?

I haven't tried this before, but you could try using a useEffect hook to respond to a change to the useDarkMode value and then redeclare the knob with a new default value:
const darkMode = useDarkMode();
let bgKnob = color('backgroundColor', Theme.colors.surface) // or whatever colors we want

useEffect(() => {
    bgKnob = color('backgroundColor', Theme.colors.surface) // or whatever color this should be
}, [darkMode]);

This ended up not working out the way I expected. There's a similar issue with the itemFontColor and itemIconColor when toggling the dark theme for the drawer full config story so I'm thinking we should just leave it as is for this story and open another issue to handle finding a solution for dynamic hard-coded values if we want to fix that.

I'm still getting a hooks issue when toggling to the rail variant on the within-a-drawer-layout story. Could someone else take a look at this?

I'm still getting a hooks issue when toggling to the rail variant on the within-a-drawer-layout story. Could someone else take a look at this?

It's because you are calling a hook inside of a conditionally rendered element:

Move that hook call outside of the rendering (make a const var for it) and you should be good.

Let's log a new issue (or JIRA story) for looking into resetting the default knobs when swapping theme.


fix: Match C source highlighting to VSCode

The theme was missing quite a few things to make it match VSCode.
VSCode:

Neovim:

I can't do anything about the LOG line just yet. The tree-sitter grammar isn't detailed enough and clangd doesn't seems to provide good tokens here.

Looking at these screenshots, it seems like the background in Neovim needs to become darker. Also, what you see is the vivid variant.

Looking at these screenshots, it seems like the background in Neovim needs to become darker. Also, what you see is the vivid variant.

I think it's how they're rendered in the terminal and VS code itself; VSCode background verses Neovim background.


Using FCM in multiple instances of an Electron app

I would like to run multiple instances of my app on the same computer. I notice that the sender ID from FCM is the only parameter used to register a client with FCM. This raises the question as to how multiple apps on a computer (even different apps) are able to register separately from other apps. Does your library create some kind of unique ID for the app that it is running on? If not, when a Push message is sent from FCM and multiple apps are running, how does the message get routed to the correct client?

push-receiver does generate an id for each registration here.
In electron-push-receiver, a new registration is created only if we didn't register before or if the credentials have been cleared. See this line.
We could add a way in electron-push-receiver to handle registration & credentials storage in user land.
As electron-push-receiver is just a wrapper around push-receiver, you can also use push-receiver directly and handle registration & credentials storage yourself.

Without looking at your code to figure it out, does this mean that if I run two instances of my app and both are using the same cache folder, both will end up having the same id? I assume that you're storing the id to some file, so when the first app registers, the second app would end up using the same registration id. If that's true, the one solution is to change the user data path for each app instance when the apps start up.

In electron-push-receiver we use electron-config or now electron-store

@MatthieuLemoine
@JohannBlake
Sorry for resurfacing an old post.
I was using the library created by Matthieu, but ran into the problem that: after we built the app, the standalone app on a Mac cannot receive any FCM events, WHILE it can if it's fired up from a terminal or VSCode.
I've been on this problem for a week now - may I ask if you might know what's gone wrong here?
(We have already checked that the token registration worked, and AWS delivered the events to FCM, but we don't know if FCM is somehow misconfigured so the standalone app cannot receive the notification, or maybe the standalone app has some privilege issue.)
Any pointer would be highly appreciated, thank you! 🙏

Not a pointer but, just to let you known that recently I used the lib on Monterey, Catalina and BigSur and it worked fine.. I used AZURE (notification hub) and the App is based on Electron 19.0.0.


Some setups are not suited in game

A lot of setups is just for high sim score, it can't use in game. For example, Veronica and GAlex. I think no one will use S!Patia's cex for GAlex. And no Veronica will use Durant's ss. I hope sim can show best or recommended setup for me to equip my character.

Simulator in it's current state is not suitable for recommending setups due to the assumption of a sandbag situation. I don't have a good solution for reconciling reality and felt that it's better to go with sim DPS first. In the future we may ban certain setups, like Durant.


artefacts in RHEL7-based images prevent easily building the images

I'm interested in being able to locally build this project myself (for #51) but still failing miserably.
Originally #48, but currently not even get that far anymore.
I'll open more specific issues, and link them here; I'l close this issue when I can actually locally build this project easily.

https://github.com/jboss-container-images/openjdk/issues/48
https://github.com/cekit/cekit/issues/380
https://github.com/cekit/cekit/issues/381

#58
#59
#60

#63

Hi @vorburger , I don't think you are still interested in using cekit/building these images (correct me if I'm wrong), but I didn't want to close off this issue until the problems had been resolved. All the linked issues and PRs are closed or merged now except for one — #58 — and there's still a problem there to fix (although the PR isn't sufficient). Therefore, I am going to re-title this issue to describe the problem that #58 tries to address. Please let me know if you have any objections.

To expand on the (new) issue title: The RHEL7-based images require Prometheus and Jolokia artefacts to be sourced somehow as part of the image build process. This happens mostly automatically when building in a Red Hat internal environment but requires the user to independently source the artefacts and install them in their local cekit cache for other cases, which is awkward.
This was resolved for the RHEL8-based images by moving the artefacts into RPMs.

Hi @vorburger , I don't think you are still interested in using cekit/building these images (correct me if I'm wrong)

If it helps for your prioritization and planning, I'm happy to confirm that I have indeed sailed on (very far actually), and therefore no longer have any interest in this space. Feel free close issues or do what you deem best. I'm unsubscribing from Notifications of such issues when I get emails about updates.
All the best.

Thanks — good luck in your new adventure (1Y late :))


[App Service] Add new App Service Environment SKU

Related command
az appservice plan create
az appservice plan update

Description
Adding new SKU for App Service Environment.

Testing Guide
az appservice plan create -g ASEResourceGroupName -n ASEPlanName --app-service-environment ASEName --sku I4v2

History Notes
This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

App Service


Fail to build

While I was attempting to build this project from source, it failed. Here are steps:
git clone --recursive https://github.com/mathis-s/SoomRV
cd SoomRV
make

It stopped with the following error message:
ccache clang++-15   -I.  -MMD -I/home/jserv/share/verilator/include -I/home/jserv/share/verilator/include/vltstd -DVM_COVERAGE=0 -DVM_SC=0 -DVM_TRACE=0 -DVM_TRACE_FST=0 -DVM_TRACE_VCD=0 -faligned-new -fbracket-depth=4096 -fcf-protection=none -Qunused-arguments -Wno-bool-operation -Wno-tautological-bitwise-compare -Wno-parentheses-equality -Wno-sign-compare -Wno-uninitialized -Wno-unused-but-set-variable -Wno-unused-parameter -Wno-unused-variable -Wno-shadow     -march=native -g -I../riscv-isa-sim   -c -o VTop__Syms.o VTop__Syms.cpp
echo "" > VTop__ALL.verilator_deplist.tmp
../Top_tb.cpp:16:10: fatal error: 'VTop_RenameTable__N4_NB2.h' file not found
#include "VTop_RenameTable__N4_NB2.h"
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

Verilator version:
$ verilator --version
Verilator 5.010 2023-04-30 rev v5.010

Clang/LLVM version:
$ clang++-15 -v
Ubuntu clang version 15.0.7
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

Thanks for the issue! The name of Verilator headers depends on module parameters, leading to these kind of stray includes. Should be fixed now, let me know if there are any other issues with building.


Compat Layer String Pollution [Quest For Smaller File Sizes!]

sol version: 6a77d5cf42da2bd1d5fac4e435c6272ce561f623
Compiler: Visual Studio 2019 16.8.2
The Issue:
While investigating file sizes produced by sol, I noticed that the compat headers are defining two static strings in the headers.
See here:

https://github.com/ThePhD/sol2/blob/develop/include/sol/compatibility/compat-5.3.c.h#L108
https://github.com/ThePhD/sol2/blob/develop/include/sol/compatibility/compat-5.3.c.h#L131

Using VS2019, with string pooling enabled, these strings are ignored and not pooled. These also don't seem to listen to/adhere to the inclusion guards either and land up being duplicated and compiled into the resulting binary for every file that includes/touches sol.
For example, my current project using sol has 55 different files that refer to sol, and thus, I have 55 copies of these strings in the compiled binary.
Here's an example pic showing some of those 55 instances:

Another interesting point to this is that as far as I can tell, my project is not setup to use these files at all, but information such as these strings are making into the resulting binary even with options setup to remove unused things.
Tested Solution:
I don't have a project setup that makes use of these compat layers to fully test, but as a potential solution, there is no need for these two strings to sit outside of the functions that refer to them. Only 1 function uses each string, so there is not much reason to leave them in the global space otherwise.
Doing this completely removes all references to them in my binaries, helping reduce the file size upwards of 1MB in size, depending on the amount of times sol.hpp is referenced.

This seems like an easy win so I might as well fold it down.

In addition to this, we could probably list all the definitions as inline rather than just static for the .c compatibility shim file. It seems like the linker folds the definitions anyways but we shouldn't be taking that risk....

Thanks! 👍 I'm working through a project while also trying to debug some other means of slimming things down. A couple of the various locations/things I've noticed that can help with reduced sizes and reduced compile times would be:

Full new_usertype usage is bad for compile times and file size.

Here's three examples of using new_usertype that can have very different impacts on the file size and compile times:
// Method 1
this->m_LuaState.new_usertype<ISomeInterface>(u8"ISomeInterface",
  sol::no_constructor,
  u8"DoSomething", &ISomeInterface::DoSomething);

// Method 2
auto chatManager = this->m_LuaState.new_usertype<ISomeInterface>(u8"ISomeInterface", sol::no_constructor);
chatManager.set_function(u8"DoSomething", &ISomeInterface::DoSomething);

// Method 3
auto chatManager = this->m_LuaState.new_usertype<ISomeInterface>(u8"ISomeInterface", sol::no_constructor);
chatManager[u8"DoSomething"] = &ISomeInterface::DoSomething;

Method 1, if used with a very large type generates massive compile time overhead. This also has a huge impact on file size because of, what I believe to be, Args... expansion. The resulting binary will create mini-stub calls that will invoke into themselves for every set of data passed to new_usertype. This means something that has say, 50 fields will result in 100 calls being produced just to expand out into the full type registration. That looks something like this in the end:
_DWORD *__thiscall sub_10135570(_DWORD *this, int a2, int a3, int a4, int a5, int a6, int a7, int a8, int a9, int a10, int a11, int a12, int a13, int a14, int a15, int a16, int a17, int a18, int a19, int a20, int a21, int a22, int a23, int a24, int a25, int a26, int a27, int a28, int a29, int a30, int a31, int a32, int a33, int a34, int a35, int a36, int a37, int a38, int a39, int a40, int a41, int a42, int a43, int a44, int a45, int a46, int a47, int a48, int a49, int a50, int a51, int a52, int a53, int a54, int a55, int a56, int a57, int a58, int a59, int a60, int a61, int a62, int a63)
{
  sub_101357A0(
    STACK[0x19C],
    a5,
    a6,
    a7,
    a8,
    a9,
    a10,
    a11,
    a12,
    a13,
    a14,
    a15,
    a16,
    a17,
    a18,
    a19,
    a20,
    a21,
    a22,
    a23,
    a24,
    a25,
    a26,
    a27,
    a28,
    a29,
    a30,
    a31,
    a32,
    a33,
    a34,
    a35,
    a36,
    a37,
    a38,
    a39,
    a40,
    a41,
    a42,
    a43,
    a44,
    a45,
    a46,
    a47,
    a48,
    a49,
    a50,
    a51,
    a52,
    a53,
    a54,
    a55,
    a56,
    a57,
    a58,
    a59,
    a60,
    a61,
    a62,
    a63,
    a64,
    a65,
    STACK[0x10C],
    STACK[0x110],
    STACK[0x114],
    STACK[0x118],
    STACK[0x11C],
    STACK[0x120],
    STACK[0x124],
    STACK[0x128],
    STACK[0x12C],
    STACK[0x130],
    STACK[0x134],
    STACK[0x138],
    STACK[0x13C],
    STACK[0x140],
    STACK[0x144],
    STACK[0x148],
    STACK[0x14C],
    STACK[0x150],
    STACK[0x154],
    STACK[0x158],
    STACK[0x15C],
    STACK[0x160],
    STACK[0x164],
    STACK[0x168],
    STACK[0x16C],
    STACK[0x170],
    STACK[0x174],
    STACK[0x178],
    STACK[0x17C],
    STACK[0x180],
    STACK[0x184],
    STACK[0x188],
    STACK[0x18C],
    STACK[0x190],
    STACK[0x194],
    STACK[0x198],
    STACK[0x19C]);
  this[98] = a4;
  this[99] = a3;
  return this;
}

This is done for literally every entry in the type definition, which generates so much call overhead for registering types.
Method 3 lands up creating a lot of table-usage overhead calls. For every entry you make there is the full indexing call setup, the validations, and updates for the data being set. This lands up creating a bunch of overhead for each entry added as the compiler does not seem to enjoy optimizing some of the situations created by this method.
Method 2 seems to be the happy medium here where the compile time is kept lower than the other 2 as well as the file size results in the lower of the 3.

Full new_enum usage is bad for compile times.

Another similar issue is with enums, large enums can result in very large file size output and inflated compile times. However, this is already addressed by using the newer std::initializer_list constructor for the enum.

sol causes a lot of RTTI to be generated, but it's not used.

This is more or less compiler and project dependent, but I saved 1mb+ by completely disabling RTTI.
As stated in sol's docs, RTTI information is not used by the library, and none of my project uses it either, so I disabled it.
As a side note, it does seem like #define SOL_NO_RTTI 1 does nothing and instead having to disable it in the compiler itself works.

Mysterious debug info left in by VS2019 latest update.

This isn't directly related to sol that I can tell, and seems to be more specific to just the compiler. VS2019's latest update seems to have added some extra CRT debug information that gets left in the resulting binaries, even with debug info disabled and in release mode. This causes directories to land up being left in the binary, such as the IMAGE_DEBUG_DIRECTORY directory. This is a result of POGO (Profile-Guided Optimizations) being forced on or something now by default. (Potentially a bug in VS2019's latest update.)
https://docs.microsoft.com/en-us/cpp/build/profile-guided-optimizations?view=msvc-160
This can be disabled by adding the following linker configuration options: /DEBUG:NONE /EMITPOGOPHASEINFO
Current result
Here's some information related to my current testing, edits and configurations to get things reduced:
Environment:

VS2019 16.8.3
Using MoonJIT as my Lua engine.
32bit project.
85 registered user types varying in size. (Largest one having over 100 functions/properties.)
10 registered enums.

sol is compiled with:
#pragma warning(push)
#pragma warning(disable : 26439) // This kind of function may not throw. Declare it 'noexcept'.
#pragma warning(disable : 26495) // Variable uninitialized; always initialize a member variable.
#pragma warning(disable : 26812) // The enum is unscoped. Prefer 'enum class' over 'enum'.
#pragma warning(disable : 26819) // Unannotated fallthrough between switch labels.

#define SOL_ALL_SAFETIES_ON 1
#define SOL_EXCEPTIONS_ALWAYS_UNSAFE 0
#define SOL_EXCEPTIONS_SAFE_PROPAGATION 1
#define SOL_NO_RTTI 1

#pragma comment(lib, "lua51.lib")
#include <sol/sol.hpp>
#pragma warning(pop)

Results before above tweaks/adjustments:

Compile times: ~5minutes.
Compiled binary size: 8-10MB

Results after above tweaks/adjustments:

Compile times: 30 seconds.
Compiled binary size: 4-5MB

Disassembling and static analysis shows there's still a lot of room for improvement to fold down excess calls but I'm not too sure if there's an easy manner for sol to account for this. The use of std::tuple and Args... expansion seems to be the main cause of this to happen and it doesn't seem like for Visual Studio, at least, that optimizations are being performed after the templates fully expand out. The call overhead, being the main one easily seen, seems like something the compiler could have easily compressed down to a few calls or even a single call but doesn't.
I'm interested to see/hear of any other suggestions or optimizations that can be made to help further reduce things though. I've spent the last few days tinkering with things to try and get things slimmed down as much as possible.
This project used to be bound to Lua using Luabind (deboostified) and the resulting binary for that is only 2.5-3MB.


Issue 391 - Updates to EFO feedback processing

Closes #391 . Some notes:

Updated spreadsheet template here. I've left the sample data in there but will remove once this is merged.
Updated code and SOPs - done in this PR.
Automating retrieval of MedGen/OMIM terms: Decided to do this properly in a separate issue, by extracting xrefs from ClinVar and including them in the curation spreadsheet so they're available for all traits, not just new ones. See #429.
QC of new terms (parent is present in EFO): This would require an extra manual step of exporting not just the main curation worksheet but also the new terms worksheet. I wasn't sure if this would be worth the effort given that it's created manually and checked manually by SPOT, so I left it out for now.
QC of import terms (term not present in EFO): This is doable since these URIs are present in the main worksheet, but I'm not sure of the value as it's only useful for mappings not already in the spreadsheet (those in the spreadsheet have already been checked for EFO containment). If we want to improve this further we could do it as part of #414.

Let me know if you think we should add the QC as part of this PR...

Tests are failing due to changes in Ensembl 112

It's a problem with BioMart, Ensembl is working on it... there are probably E2E tests to fix as well though.


MAINTAINERS: hawkBit: remove myself from the collaborator

Remove myself from the collaborator as there's a maintainer now.

Instead of saying "... remove myself from...", could you write "...remove ycsin from..." It is then easier to see who was removed without looking the details.

makes sense, updated the title


Maybe merge from fork https://github.com/xenit-eu/alfviral

It think it's good to merge some fixes from other forks, so this one keeps up to date.

Hi Tahir!
Yes, good idea!
But, from forks or to forks?
Fernando González Ruano
Skype: fegorama
LinkedIn: https://www.linkedin.com/in/fegor/
GitHub: https://github.com/fegorama/
Blog: http://www.fegor.com/
El jue, 6 oct 2022 a las 14:42, Tahir Malik @.***>)
escribió:

It think it's good to merge some fixes from other forks, so this one keeps
up to date.
—
Reply to this email directly, view it on GitHub
https://github.com/fegorama/alfviral/issues/25, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNYQWIRCG6GBVI3UCJMVSTWB3CKJANCNFSM6AAAAAAQ6SONPU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Rename lte-m to lte

https://ci.opensmartgridplatform.org/view/Nightly/job/SSS_osgp-applications-public-lighting_nightly/1551/
https://ci.opensmartgridplatform.org/view/Nightly/job/OSGP_open-smart-grid-platform_nightly/1773/


Not working with Python 32 bit (x86)

Describe the bug
A clear and concise description of what the bug is.
I installed the Reloadium plugin version 0.8.8, then tried to debug my code, and I got an error:
It seems like your platform or Python version are not supported yet.
Windows, Linux, macOS and Python >= 3.7 (3.9 for M1) are currently supported.
To Reproduce
Steps to reproduce the behavior:

Installed lates plugin (0.8.8) from this URL:
https://plugins.jetbrains.com/plugin/18509-reloadium--hot-reloading--profiling-for-python/versions
(File > Settings > Plugins - clicked the cogwheel icon and chose Install plugin from disk, installed from downloaded zip file)
Run or debug code with the orange icons
See error

Expected behavior
Debug without error
Screenshots
NA
Desktop (please complete the following information):

OS: Windows 10 Pro 64 bit (running on a VM on Hyper-V)
OS version: 10.0.19044.2251
Reloadium package version: 0.9.4
PyCharm plugin version: 0.8.8
Editor: PyCharm 2022.02.03
Run mode: Either Run or Debug

Additional context
I didn't understand, do we need to install both the Reloadium package and the Reloadium plugin for PyCharm too?
I thought I would just install the plugin and it would work. But I have installed the package too via pip, using this command below, and it's still not working:
pip install reloadium

Reloadium package is bundled with the plugin so it should work out of the box.
Could you run it again with RW_DEBUG = True environmental variable on and paste the error?

Hi Damian,
I did that and here is the error:
It seems like your platform or Python version are not supported yet.
Windows, Linux, macOS and Python >= 3.7 (3.9 for M1) are currently supported.
Please submit a github issue if you believe Reloadium should be working on your system at
https://github.com/reloadware/reloadium
Traceback (most recent call last):
File "C:\Program Files (x86)\Python38-32\lib\runpy.py", line 184, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
File "C:\Program Files (x86)\Python38-32\lib\runpy.py", line 143, in _get_module_details
return get_module_details(pkg_main_name, error)
File "C:\Program Files (x86)\Python38-32\lib\runpy.py", line 110, in get_module_details
import(pkg_name)
File "C:\Users\SNAGY.SCMAO.reloadium\package\3.8\reloadium_init.py", line 4, in
pre_import_check()
File "C:\Users\SNAGY.SCMAO.reloadium\package\3.8\reloadium_utils.py", line 20, in pre_import_check
import reloadium.corium
ModuleNotFoundError: No module named 'reloadium.corium'

Hey I just noticed you're using python 32 bit which is not supported anymore.
Please use 64 bit if possible.

OK, I have installed the latest Python, version 3.11 (64 bit), and I get a very similar error:
It seems like your platform or Python version are not supported yet.
Windows, Linux, macOS and Python >= 3.7 (3.9 for M1) are currently supported.
Please submit a github issue if you believe Reloadium should be working on your system at
https://github.com/reloadware/reloadium
Traceback (most recent call last):
File "", line 189, in _run_module_as_main
File "", line 148, in get_module_details
File "", line 112, in get_module_details
File "C:\Users\SNAGY.SCMAO.reloadium\package\3.7\reloadium_init.py", line 4, in
pre_import_check()
File "C:\Users\SNAGY.SCMAO.reloadium\package\3.7\reloadium_utils.py", line 20, in pre_import_check
import reloadium.corium
ModuleNotFoundError: No module named 'reloadium.corium'


Release v9.1.7 contains a module bug

components: build
reactstrap version #9.1.7
import method "esm/index.js"
react version #18.2.0
bootstrap version #5.2.3

What is happening?
After upgrading the parcel bundler cannot find the folder esm/ which is reference in the package.json like so "module": "esm/index.js",
Error message in console
Server running at http://localhost:8080
🚨 Build failed.

@parcel/core: Failed to resolve 'reactstrap' from './src/apps/project/pages/NotFound.tsx'

  C:\Users\User\project\src\apps\currentApp\pages\NotFound.tsx:4:24
    3 | import { Link } from 'react-router-dom';
  > 4 | import { Button } from 'reactstrap';
  >   |                        ^^^^^^^^^^^^

@parcel/resolver-default: Could not load './esm/index.js' from module 'reactstrap' found in package.json#module

  C:\Users\User\project\node_modules\reactstrap\package.json:7:13
    6 |   "main": "lib/index.js",
  > 7 |   "module": "esm/index.js",
  >   |             ^^^^^^^^^^^^^^ './esm/index.js' does not exist, did you mean './lib/index.js'?'
    8 |   "types": "types/index.d.ts",
    9 |   "sideEffects": false,

I'm also facing this error.
export 'Row' (imported as 'Row') was not found in 'reactstrap' (module has no exports)

Getting this issue in 9.1.7 version,
export 'Modal' (imported as 'Modal') was not found in 'reactstrap' (module has no exports)
export 'ModalHeader' (imported as 'ModalHeader') was not found in 'reactstrap' (module has no exports)
export 'ModalBody' (imported as 'ModalBody') was not found in 'reactstrap' (module has no exports)
export 'ModalFooter' (imported as 'ModalFooter') was not found in 'reactstrap' (module has no exports)

Getting this issue in 9.1.7 version,
export 'Modal' (imported as 'Modal') was not found in 'reactstrap' (module has no exports) export 'ModalHeader' (imported as 'ModalHeader') was not found in 'reactstrap' (module has no exports) export 'ModalBody' (imported as 'ModalBody') was not found in 'reactstrap' (module has no exports) export 'ModalFooter' (imported as 'ModalFooter') was not found in 'reactstrap' (module has no exports)

Fallback to version 9.1.6

The issue is probably easily fixed by the developers by just calling npm run build:esm, which they might have forgotten on this release.

When i upgrade to latest version start getting following error while creating build
Module not found: Error: Can't resolve './Container' in 'project_source/node_modules/reactstrap/lib'
Then after try to downgrade to v9.1.6 but start facing same issue, then i also try to downgrade up to v9.1.0 but still facing same issue. I have completely remove node_modules and package-lock.json file and tried but not working at all.  i am using below vrsions.
react 18.2.0
react-dom 18.2.0
bootstrap 5.2.3
node 16.14.0

For temporary fix i have removed "reactstrap": "^9.1.6", and set "reactstrap": "9.1.6", in package.json file and its working fine for me.

Closing when https://github.com/reactstrap/reactstrap/pull/2725 is done

@kai-dorschner-twinsity thank you for the detailed bug report. Made fixing it easier. :)


Found this very confusing for the validation step.

What is this asuid referred to - app service uid? I can find no such animal. My working TXT records also look nothing like this instead have:
TYPE: TXT
NAME: awverify.{subdomain}
VALUE: {appservicename}.azurewebsites.net
Only the naked domain appears to have required the validation id
TYPE: TXT
NAME: *
VALUE: {validation id}

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

ID: 224b73dd-c59d-a833-0d4d-a778af6086a9
Version Independent ID: c6b167c9-9589-45d0-ee6a-7a47a4aec41e
Content: Tutorial: Map existing custom DNS name - Azure App Service
Content Source: articles/app-service/app-service-web-tutorial-custom-domain.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@jeepwran We are checking this and will get back to you.

Hi @jeepwran, we apologize for the confusion in the validation steps. The "asuid" is referring to the verification ID you got earlier after you added a custom domain to your app. You only need to add a TXT record to your DNS in order to verify your domain ownership. Please use  asuid.{subdomain} instead of awverify.{subdomain} to verify your domain ownership
As doc said: "To add a custom domain to your app, you need to verify your ownership of the domain by adding a verification ID as a TXT record with your domain provider.
You can find your domain verification id for your app in azure by navigating to the left of your app page, click Resource explorer under Development Tools, then click Go.

In the JSON view of your app's properties, search for customDomainVerificationId, and copy its value inside the double-quotes.  this is the verification ID you need.

Hope that helps. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Bring back the idea to connect to a remote org please!!!

This idea is nice but hard to implement in the salesforce app version of OrgCheck.
But this brought me another idea.
I will port OrgCheck on Heroku or another server to let you do this.
Let's push this for 2.0

This will be possible with SFDX plugin approach but not with the salesforce application
See #184


Added 8 to make example more clear

Some exchanges have 8 to start their wallets: Binance, Bitfinex, KuCoinhave wallet adresses starting with digit '8'.
And the monero donate address starts with an 8, so saying they start with 4 might be confusing as alphatomcat said.
Closes #1947

@Mark-777-0 add Closes https://github.com/monero-project/monero-site/issues/1947 in your first comment so that it automatically closes, it doesn't work when you write it in the second comment.

@Mark-777-0 add Closes #1947 in your first comment so that it automatically closes, it doesn't work when you write it in the second comment.

I added it, but not sure if it worked.


Add nprime asm example

Describe your changes
This commit introduces a new example that will calculate the nth prime using the VM memory.
This is a naive approach to keep the code simple and clear.
Two nits in the docs were also fixed; the first one is about assertz, that checks constant 0 instead of b.
The second one is further clarification for the syntax of while to exemplify that the argument of the statement isn't a constant true, but expects true in the first element of the stack.
Checklist before requesting a review

[x] Repo forked and branch created from next according to naming convention.
[x] Commit messages and codestyle follow conventions.
[x] Relevant issues are linked in the PR description.
[ ] Tests added for new functionality. (N/A; example added)
[x] Documentation/comments updated according to changes.

I meant to add two very minor nits related to commit conventions -

we typically use semantic commits. You can see a bit more info about it in the contributor guidelines
I would prefer to have separate concerns in separate commits, i.e. put the docs updates into one commit and the new example into a different commit.

But there's no need to make changes for this PR


Update backup-azure-arm-restore-vms.md

Changed the line: "After you trigger the restore operation, the backup service creates a job for tracking. Azure Backup displays notifications about the job in the portal. If they aren't visible, click on the Notifications symbol and so, click View all Jobs to see the Restore Process Status." Including click in All Jobs due a frequent customers confusion on a missing step.

@mottach : Thanks for your contribution! The author, @geethalakshmig, has been notified to review your proposed change.

@GeethalakshmiG  - If the change is ok, please sign off on this article.

as requested in email, i have reviewed this PR and am merging based on approval by @dcurwin .


Optimize eval injection

Maybe make default as well. Perf seems way better

The first prototype of this was absurdly fast - probably a bit less maintainable though. Might be worth poking around.
Currently we resolve the execution order, start building data in memory, then start writing to the stream.
Perf-wise, it'd be better to:

write the bootstrap to the stream
resolve the execution order
iterate through write everything to the stream
write the init code to the stream

This would drop the time-to-first-byte, as well as reducing the memory load on the backend (not that it's really a problem).


Vendor support  and Validator

A feature request

Addition of web kits/ vendor prefixes on CSS along with validations from w3 to check correct syntax and markup to have uniform experience on all browsers!

@anushbhatia Sir, if considered valid I would like to work on it alone to avoid confusion! Thank you!.

Sure nobody will interfere in this

@anushbhatia Sir I am closing this since CSS was covered very nicely last time and not much has changed just a few lines only and people started adding it themselves as well so no work left here!


Comment and PM not working.

Auto comment and PM not working, I've tried it on memu and ldplayer but its still not working.
For Comment percentage, PM percentage, list for comment and DM already field but its still not working.
any suggestions?

if it doesn't comment, it writes the reason. if it crashes, you have to upload it here

i just tried again and it can't comment and dm.
i added the list for comment and pm in file .txt and its still not work.
but for like, story, follow, unfollow its working very good idk why.

Hey there - same here. The issu is
"warning can't comment this MediaType.Carousel because filters are: can_comment_photos = false, can_comment_videos = false, can_comment_carousels = false, can_comment_place-posts-top = false. check your filters.yml"
Unfortunately, there is no filter in the filter.yml file that excludes commenting. On the contrary, all are marked as "true".

I've added a more detailed log so you can find the problem


Improve footer-blue-14

Need to improve this component: footer-blue-14
Improvements required :

Improve google play and apple store buttons as per the Figma file
Adjust layout as per the Figma file

Any reference image?

Please assign me @Rajdip019

@Dibyendu303 go ahead


Should / How can we deal with unsupported operator warning?

How can I find where and how to solve these? Or I could ignore these?
/home/yisiang/miniconda3/envs/dl/lib/python3.9/site-packages/onnxruntime/training/ortmodule/_logger.py:51: UserWarning: There were one or more warnings or errors raised while exporting the PyTorch model. Please enable INFO level logging to view all warnings and errors.
  warnings.warn("There were one or more warnings or errors raised while exporting the PyTorch "
Warning: Unsupported operator ATenOp. No schema registered for this operator.
Warning: Unsupported operator ATenOp. No schema registered for this operator.
...
Warning: Checker does not support models with experimental ops: Scale
Warning: Checker does not support models with experimental ops: Scale
....
2021-07-20 22:00:01.572480474 [W:onnxruntime:, constant_folding.cc:134 ApplyImpl] Could not find a CPU kernel and hence can't constant fold Sub node 'Pow_10_Grad/Sub_1'
2021-07-20 22:00:01.580978404 [W:onnxruntime:, constant_folding.cc:134 ApplyImpl] Could not find a CPU kernel and hence can't constant fold Sub node 'Pow_10_Grad/Sub_1'
....

Training a transformer encoder
torch 1.9.0
torch-ort 1.8.1
onnx 1.9.0
onnxruntime-training 1.8.1+torch190.cu111

-- 2021.07.24 ---
I found if the forward pass of embedding is commented, Warning: Unsupported operator ATenOp.... will disappear. But UserWarning: There were one or more warnings... still exists. Wonder how to turn on INFO level logging.

Hi @richarddwang, all the warnings above are non-critical, and actually misleading. Are you able to run the training?
We will clean up these warning messages.

That will be nice, thank you.
The training ran smoothly. It seems like those warnings doesn't affect anything.


Can't connect to aiven db

Hello! After setting up an aiven db and testing the connection with rebar3 shell, it seems that it can't connect:
Pool creation:
pgo:start_pool(test, #{pool_size => 5, host => "[REDACTED].a.aivencloud.com", database => "defaultdb", port => 22381, user => "avnadmin", password => "[REDACTED]", ssl => true, ssl_options => [{{cacertfile, "./ca.pem"}, {verify, verify_peer}]}).

Test command:
pgo:query("select id from post", #{pool => test}).

and (because I don't know if it needs to be a string)
pgo:query("select id from post", #{pool => "test"}).

Return from both queries
{error,none_available}

Can someone help me?

And ther eare no logs about connections failing?

logger won't print anything by default, you'll want to create a file like config/sys.config:

[{kernel,
  [{logger_level, debug},
    {logger,
    [{handler, default, logger_std_h,
      #{level => debug, formatter => {logger_formatter, #{single_line => true}}}}
    ]}]}].

And run rebar3 as:
rebar3 shell --config config/sys.config

After running
pgo:start_pool(test, #{pool_size => 5, host => "pg-a4560fe-catgram.a.aivencloud.com", database => "defaultdb", port => 22381, user => "avnadmin", password => "AVNS_bnrCb3NoORvNXijLsp1", ssl => true, ssl_options => [{{cacertfile, "./ca.pem"}, {verify, verify_peer}}]}).

it spams unknown error when connecting to database: {option_not_a_key_value_tuple,{{cacertfile,"./ca.pem"},{verify,verify_peer}}}

Ah yea, that 2 2-tuples in a 1-tuple. Remove the surrounding {} .

After fixing that error and running again it returned the following
2024-03-23T13:18:34.527418-03:00 info: Supervisor: {<0.241.0>,pgo_pool_sup}. Started: id=connection_sup,pid=<0.242.0>.
2024-03-23T13:18:34.528201-03:00 info: Supervisor: {<0.241.0>,pgo_pool_sup}. Started: id=connection_starter,pid=<0.243.0>.
2024-03-23T13:18:34.529037-03:00 info: Supervisor: {<0.241.0>,pgo_pool_sup}. Started: id=type_server,pid=<0.244.0>.
{ok,<0.240.0>}
2> 2024-03-23T13:18:34.538168-03:00 info: Supervisor: {local,inet_gethost_native_sup}. Started: pid=<0.252.0>,mfa={inet_gethost_native,init,[[]]}.
2024-03-23T13:18:34.538260-03:00 info: Supervisor: {local,kernel_safe_sup}. Started: id=inet_gethost_native_sup,pid=<0.251.0>.
2024-03-23T13:18:35.376984-03:00 info: Supervisor: {<0.260.0>,tls_dyn_connection_sup}. Started: id=sender,pid=<0.266.0>.
2024-03-23T13:18:35.376987-03:00 info: Supervisor: {<0.263.0>,tls_dyn_connection_sup}. Started: id=sender,pid=<0.268.0>.
2024-03-23T13:18:35.377058-03:00 info: Supervisor: {<0.265.0>,tls_dyn_connection_sup}. Started: id=sender,pid=<0.269.0>.
2024-03-23T13:18:35.377009-03:00 info: Supervisor: {<0.261.0>,tls_dyn_connection_sup}. Started: id=sender,pid=<0.267.0>.
2024-03-23T13:18:35.377095-03:00 info: Supervisor: {<0.260.0>,tls_dyn_connection_sup}. Started: id=receiver,pid=<0.272.0>.
2024-03-23T13:18:35.377142-03:00 info: Supervisor: {<0.263.0>,tls_dyn_connection_sup}. Started: id=receiver,pid=<0.273.0>.
2024-03-23T13:18:35.377171-03:00 info: Supervisor: {<0.265.0>,tls_dyn_connection_sup}. Started: id=receiver,pid=<0.274.0>.
2024-03-23T13:18:35.377093-03:00 info: Supervisor: {<0.262.0>,tls_dyn_connection_sup}. Started: id=sender,pid=<0.270.0>.
2024-03-23T13:18:35.377117-03:00 info: Supervisor: {<0.264.0>,tls_dyn_connection_sup}. Started: id=sender,pid=<0.271.0>.
2024-03-23T13:18:35.377282-03:00 info: Supervisor: {<0.261.0>,tls_dyn_connection_sup}. Started: id=receiver,pid=<0.275.0>.
2024-03-23T13:18:35.377346-03:00 info: Supervisor: {<0.262.0>,tls_dyn_connection_sup}. Started: id=receiver,pid=<0.276.0>.
2024-03-23T13:18:35.377456-03:00 info: Supervisor: {<0.264.0>,tls_dyn_connection_sup}. Started: id=receiver,pid=<0.277.0>.

Then I ran the following tests:
2> pgo:query("select id from post", #{pool => "test"}).
** exception exit: {noproc,{pgo_pool,checkout,[default,[]]}}
     in function  pgo_pool:checkout/2 (/home/pedrohcf/pgo/src/pgo_pool.erl, line 58)
     in call from pgo:query/3 (/home/pedrohcf/pgo/src/pgo.erl, line 100)
3> pgo:query("select id from post", #{pool => test}).
** exception exit: {noproc,{pgo_pool,checkout,[default,[]]}}
     in function  pgo_pool:checkout/2 (/home/pedrohcf/pgo/src/pgo_pool.erl, line 58)
     in call from pgo:query/3 (/home/pedrohcf/pgo/src/pgo.erl, line 100)

try:  pgo:query("select id from post", [], #{pool => test}).
To pass the options you have to use query/3: query(Query, Params, Options)


Refactor Specifier to use resolvo::range::Range

The Specifier struct uses a custom implementation to create a range. Instead of returning half-open-ranges, it would be nicer to return a resolvo::range::Range
This does mean that the resolvo feature should also be enabled.. Should we get rid of the feature and always include resolvo then? Or should we move the Range struct into a separate crate?

IMO resolvo seems like a core piece of rip so we could always enable it. We could rather factor out lower level parts of rip into other crates (what konstin is already doing with pep440_rs and pep558_rs etc.
WDYT?

I agree! Im working on integrating pep508_rs and then this becomes obsolete.


Nuget Package Dependencies?

This might be out of the scope of this project but I was wondering if Nuget packages currently (maybe I'm doing something wrong) or in the future are going to be supported.
Currently I do see the suggestions, and I have already installed Nuget packages which are my current project dependencies but the suggestion for using them in atom is "The type or namespace name 'Example' could not be found (are you missing a using directive or an assembly reference?)". But in visual studio it doesn't say anything is wrong and the project builds correctly.
Env:
Windows 7 x64
Atom 1.21.0-beta1 x64
atom-ide-ui 0.3.3
ide-csharp 0.6.0

That's really a question for the upstream language server this package depends on I think.
Their repo is at https://github.com/OmniSharp/omnisharp-node-client


Extract ID from Path is broken if base path is provided

Question
After upgrading tusd package noticed 404 errors for PATCH request.

2024/07/04 16:51:17 INFO ResponseOutgoing method=PATCH path=/media/upload/63f0f86e643ed46472fb4fafa654b274+zzgpwSfRXuzhE1QskfccW6dRWG50j5dn48_kupnC.plOTtLd9_TtedwtBwOwvZmI3YD8ItxjOunTAcLhGJ04Dz2C5UsnDE7o9_I1zmcia90xHQQ_yZxV70Ox8Hxqr97.osT_E45G1zvB1qUOc5uppmMWXGG4Gcc7XTj0N_qjsxg- requestId="" id=media/upload/63f0f86e643ed46472fb4fafa654b274+zzgpwSfRXuzhE1QskfccW6dRWG50j5dn48_kupnC.plOTtLd9_TtedwtBwOwvZmI3YD8ItxjOunTAcLhGJ04Dz2C5UsnDE7o9_I1zmcia90xHQQ_yZxV70Ox8Hxqr97.osT_E45G1zvB1qUOc5uppmMWXGG4Gcc7XTj0N_qjsxg- status=404 body="ERR_UPLOAD_NOT_FOUND: upload not found\n"

While comparing the difference noticed the generated Upload ID seems odd.
Not clear why such lengthy ID is being generated and how to debug this further.
Setup details
Please provide following details, if applicable to your situation:

Operating System: [ Linux, macOS]
Used tusd version: v2.4.0 , also tested with v2.5.0-rc1
Used tusd data storage: [AWS S3]
Used tus client library: [Uppy.js]

This length is normal for the S3 store as it needs to encode the object ID and the multipart ID for S3 multipart uploads in the upload ID. That is not a bug. In future version I hope to change this and remove the multipart ID (the second part after the + sign) from the upload ID. But that is not the case yet.
The problem might be that it considers media/upload/ to be part of the upload ID, but I suppose it should be a path prefix instead. You might have to add -base-path /media/upload/ to the CLI.
If that doesn't work, please share you entire tusd configuration, as was also requested in the issue template.

You might have to add -base-path /media/upload/ to the CLI

Not using the CLI but embedded as Go package.
tusd.Config.BasePath is configured to domain_name/media/upload/ which is reflected here in logs,

path=/media/upload/63f0f86e643ed46472fb4fafa654b274+zzgpwSfRXuzhE1QskfccW6dRWG50j5dn48_kupnC.plOTtLd9_TtedwtBwOwvZmI3YD8ItxjOunTAcLhGJ04Dz2C5UsnDE7o9_I1zmcia90xHQQ_yZxV70Ox8Hxqr97.osT_E45G1zvB1qUOc5uppmMWXGG4Gcc7XTj0N_qjsxg-

Issue started after v2.2.2
In v2.2.2 extractIDFromPath method uses regex which removes the base path and only returns the id,

result := reExtractFileID.FindStringSubmatch(url)

In v2.4.0,

return strings.Trim(path, "/")

Also noticed the comment,

extractIDFromPath extracts the upload ID from a path, which has already been stripped of the base path (done by the user)

Unfortunately this is not clearly documented.
Is it expected to rewrite path before forwarding all request to tus unrouted handlers?

Do you use http.StripPrefix?
https://github.com/tus/tusd/blob/585d7a57110a544809fab98c683cdf7331b8e52a/pkg/handler/doc.go#L67
https://github.com/tus/tusd/blob/585d7a57110a544809fab98c683cdf7331b8e52a/examples/server/main.go#L60

Nope. Let me test this out. Thanks.

All works after removing the custom path http.Handle("/files/", http.StripPrefix("/files/", handler))


Style Fat Arrows

Right now it is interpreted as equal or bigger than.  But this should be possible see https://github.com/codemirror/CodeMirror/issues/3614

Arrow syntax is correctly highlighted as .cm-operator for me, it was added with #11528 (I think, that version contained tons of ES6 improvements).

=>  would be better colored in blue[or the color of function keyword].

The thing is stuff like >= is also .cm-operator right now which is different than an actual fat arrow ofc

Like @abose said it would be better to color it the same as function (blue in default(?), green for me ;))

Actually yeah, now that I think about it they should be .cm-function as => is not an operator at all, confused the naming with C-like arrow operators -> for a while.

codemirror/CodeMirror#3614 says, the coloring is correct as => is correctly colored as a CM operator- which makes sense in one way. Not entirely sure now if we should have a special treatment of an operator.

http://www.ecma-international.org/ecma-262/6.0/ does not define => as an operator. It is identified as Arrow Function Definitions .

@abose is this possible atm or does codemirror need to do something?
Also cc  https://github.com/adobe/brackets/issues/11644

@petetnt @zaggino @MarcelGerber
Is this something that we should do in the brackets side/code mirror side/ Not do at all.
I feel that => should be colored as function definition color as => is not specified as an operator rather a function def in http://www.ecma-international.org/ecma-262/6.0/

@abose I think the problem is the fat arrow is a function from a semantics standpoint, but from a syntax standpoint it is used like an infix operator. So, should syntax-coloring be based on semantics or on syntax? There are arguments for both sides, which usually signals a user preference change rather than a core change.
Regardless, not sure how you would easily implement either one. You are talking about customizing the CodeMirror Javascript mode, either directly in the file (which would change the core library code) or on the fly (no idea how to do that) so that a specific set of parsed characters returns a different style string.

@abose Actually, I take part of my previous comment back. I should probably drink my coffee before making early morning comments.
Changing a specific set of parsed characters to return a different string on the fly is exactly what a CodeMirror Overlay does although I haven't tested it yet. It could be done with an extension, so it wouldn't affect core code. Granted, it is a very specific extension :). I can at least look into it and see if it is possible.

Should the coloring not be based on the context, I get that looking at purely => it can be 2 things but in a context it will always be 1 no?

@AdriVanHoudt As I mentioned before, arguments on both sides make sense. That means it's a good user preference and/or an extension idea. I am looking into an extension solution for you.

@lkcampbell I really appreciate it!

+1
I am for => to be colored differently. But as you said it may be a personal choice. It will add better readability, like it will be eazy to locate arrow functions in code.

Thanks @lkcampbell  .
Once the PR lands, i guess more people will comment their opinions there :)

@abose My first solution is actually going to be an extension, not a PR, but we can keep this issue open to track the extension to completion. I suppose it could eventually be incorporated into the core code but it doesn't have to be incorporated.

Did anyone reach out to CodeMirror repo for at least a comment on this before we start hacking it?

@zaggino see https://github.com/codemirror/CodeMirror/issues/3614

Ah right, thanks, didn't read that much to the top, my bad.

@AdriVanHoudt @abose The extension is done and registered.
Go to the extension manager and look for Style Fat Arrows.
There is one known issue with modes that have embedded or mixed javascript that I haven't been able to fix, but overall, it seems to work fairly well.

@abose I saw you labelled this as Release 1.6 but I don't think you guys will want this solution in the core code. I suggest labelling it as Extension Available and closing it as such. Anyone who wants this change can use the extension.

Marked it as needs review for other opinions before closing.
NB: +1 for this in core :)

@lkcampbell installed and seems to work fine! Thanks a lot! :clap:
I am also still +1 for having this is core though

@abose you should know about the bug then. This code also changes the style color of fat arrows in non-Javascript code in mixed Javascript files. Open an HTML file with Javascript in it and type a fat arrow in the HTML part of the file, and you will see what I mean.
If there is a way to fix this bug, I don't know how to do it. Not sure how to figure out whether you are currently in Javascript mode or another mode when you are parsing a mixed file using a CodeMirror Overlay.

@AdriVanHoudt , I am really glad that my simple extension helped you out. It has received a surprisingly high number of downloads for a one-off. More power to you and enjoy the magic that is Open source!!
@abose, why is this bug still open? I solved it with an extension.
Let's have some closure. I am closing it and removing the priority labels.


Porting to Firefox

Hey, it would be great if this extension would also work in firefox. I did a little bit of research, but got stuck, because I couldn't compile(?) a .crx file without a manifest, but I found this site to check if the chrome extension can be ported to firefox right away: https://www.extensiontest.com/
I got the link from here: https://extensionworkshop.com/documentation/develop/porting-a-google-chrome-extension/

Thank you! This is definitely on our roadmap. I'll probably start looking into this in next couple weeks

@BjoernRave thanks for creating this issue - this is something we've been considering from early on in this project (#2).
I'll close this ticket for now but feel free to comment on the original issue if you have any thoughts or suggestions on how we can go about this 👍


Change variables to Protected on reports with Company Information pictures

Requesting variables used to include Company Information field Picture be set to Protected on reports:
ID	Name				Variables
116	Statement			CompanyInfo, CompanyInfo1, CompanyInfo2, CompanyInfo3
117	Reminder			CompanyInfo, CompanyInfo1, CompanyInfo2, CompanyInfo3
118	Finance Charge Memo		CompanyInfo1, CompanyInfo2, CompanyInfo3
208	Sales - Shipment		CompanyInfo1, CompanyInfo2, CompanyInfo3
210	Blanket Sales Order		CompanyInfo1, CompanyInfo2, CompanyInfo3
215	Archived Sales Quote		CompanyInfo, CompanyInfo1, CompanyInfo2
216	Archived Sales Order		CompanyInfo, CompanyInfo1, CompanyInfo2
418	Arch. Sales Return Order	CompanyInfo, CompanyInfo1, CompanyInfo2
1016	Job Quote			CompanyInfo
1305	Standard Sales - Order Conf.	CompanyInfo
1306	Standard Sales - Invoice	CompanyInfo
1307	Standard Sales - Credit Memo	CompanyInfo
1308	Standard Sales - Shipment	CompanyInfo
1309	Standard Sales - Return Rcpt.	CompanyInfo
1316	Standard Statement		CompanyInfo, CompanyInfo1, CompanyInfo2, CompanyInfo3
5176	Archived Blanket Sales Order	CompanyInfo, CompanyInfo1, CompanyInfo2
5900	Service Order			CompanyInfo, CompanyInfo1, CompanyInfo2
5902	Service Quote			CompanyInfo, CompanyInfo1, CompanyInfo2
5911	Service - Invoice		CompanyInfo, CompanyInfo1, CompanyInfo2, CompanyInfo3
5912	Service - Credit Memo		CompanyInfo, CompanyInfo1, CompanyInfo2, CompanyInfo3
5913	Service - Shipment		CompanyInfo1, CompanyInfo2, CompanyInfo3
5970	Service Contract		CompanyInfo, CompanyInfo1, CompanyInfo2, CompanyInfo3
5972	Service Contract Quote		CompanyInfo, CompanyInfo1, CompanyInfo2, CompanyInfo3
6631	Return Order Confirmation	CompanyInfo1, CompanyInfo2, CompanyInfo3
6646	Sales - Return Receipt		CompanyInfo1, CompanyInfo2, CompanyInfo3
10069	Sales Blanket Order		CompanyInfo1, CompanyInfo2, CompanyInfo3
10072	Customer Statements		CompanyInformation, CompanyInfo1, CompanyInfo2
10073	Sales Credit Memo NA		CompanyInfo1, CompanyInfo2, CompanyInfo3
10074	Sales Invoice NA		CompanyInfo1, CompanyInfo2, CompanyInfo3
10075	Sales Order			CompanyInfo1, CompanyInfo2, CompanyInfo3
10076	Sales Quote NA			CompanyInfo1, CompanyInfo2, CompanyInfo3
10077	Sales Shipment NA		CompanyInfo1, CompanyInfo2, CompanyInfo3
10080	Sales Shipment per Package	CompanyInformation, CompanyInfo1, CompanyInfo2
10153	Picking List by Order		CompanyInfo, CompanyInfo1, CompanyInfo2
10473	Service Credit Memo-Sales Tax	CompanyInfo1, CompanyInfo2, CompanyInfo3
10474	Service Invoice-Sales Tax	CompanyInformation, CompanyInfo1, CompanyInfo2, CompanyInfo3
10476	Elec. Sales Credit Memo MX	CompanyInformation, CompanyInfo1, CompanyInfo2
10477	Elec. Sales Invoice MX		CompanyInformation, CompanyInfo1, CompanyInfo2
10478	Elec. Service Cr Memo MX	CompanyInfo, CompanyInfo1, CompanyInfo2
10479	Elec. Service Invoice MX	CompanyInfo, CompanyInfo1, CompanyInfo2
11383	ExportElecPayments - Word	CompanyInfo

We have scenarios where we'd like to be able to change the picture.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11697.


web: limit the number of dropped targets

Closes #4134.
cc @beorn7 @brian-brazil
Here is the updated service-discovery page:

Sweet. Thanks for tackling this.
I'll leave the detailed review to Brian, since he is already on it.
Just one high level remark: Is 1k targets sufficient? In the SoundCloud case, the cluster had around 10k pods, and the size of the HTML on the SD endpoint was 1.4GiB. The math might be more complicated, but I would naively assume the limit of 1k will cut the size by a factor of 10. But 140MiB still sounds like a lot for hitting a simple status information endpoint.

The limit is only on the dropped targets, the active ones are always shown.

Idea: Perhaps do something like displaying everything as long as at most 1k dropped targets will actually display everything. However, if we have to limit the displayed targets anyway, there is not much gain between showing 100 or 1000. In that case, we could limit to something low, e.g. 100 or even less, and display a warning along the lines: "12,345 targets dropped, displaying only the first 100 as examples."

The limit is only on the dropped targets, the active ones are always shown.

To avoid misunderstandings: I'm only talking about dropped targets here.
By "Is 1k targets sufficient?" I mean "Is 1k targets sufficiently low?"

How many different kubernetes_sd_configs did ye have inside one Prometheus again?

That really depends. I think we need to cater for the use case of tens just by number of jobs configured, times a small factor if we have multi-port per pod setups.

I was trying to get a gauge of how many jobs that 1.4GB covered.

That particular config is gone by now. It would require some forensics to find out.
However, I don't think it matters so much as Prometheus is meant to scale nicely, and we should make absolutely sure that the scalability limit is not determined by the status page of the web UI.
Thus we should have very conservative limits.

Okay, let's go with 100.

I've updated the PR according to the comments.

Thanks!