Printer is not visible on windows

This is my code(ipp-printer.js):
var fs = require('fs')
var Printer = require('ipp-printer')
var printer = new Printer({name:"ipp-printer", port:8080})
console.log(printer);
printer.on('job', function (job) {
console.log('[job %d] Printing document: %s', job.id, job.name)
var filename = 'job-' + job.id + '.ps' // .ps = PostScript
var file = fs.createWriteStream(filename)
job.on('end', function () {
console.log('[job %d] Document saved as %s', job.id, filename)
})
job.pipe(file)
})
then i run the code > node ipp-printer.js
But i couldn't find the printer "ipp-printer" anywhere. How can i add/find the printer? Please help me. Any help will be appreciated. I am a beginner in Node. So sorry if i am asking anything wrong.

@jaidirectdsn  Hi, you solved this?

How did you guys actually solve this?

I created virtual printer:
this.printer = new Printer({ name: 'PrinterName', port: 3007 })

And then I used powershell script to install the printer:
# Step 1 - Enable InternetPrinting feature
$Feature = Get-WindowsOptionalFeature -Online -FeatureName "Printing-Foundation-InternetPrinting-Client"
if ($Feature.State -ne "Enabled") {
        Enable-WindowsOptionalFeature -Online -FeatureName "Printing-Foundation-Features" -NoRestart
        Enable-WindowsOptionalFeature -Online -FeatureName "Printing-Foundation-InternetPrinting-Client" -NoRestart
}

# Step 2 - Install printer
$Result = Test-NetConnection <IP_ADDRESS> -Port 2404
If ($Result.TcpTestSucceeded) {
     Add-Printer -Name "PixLetter" -DriverName $PrinterDriverName -PortName "http://$($env:COMPUTERNAME):2404"
} Else {
      throw "Printer port doesn't exposed"
}

I created virtual printer:
this.printer = new Printer({ name: 'PrinterName', port: 3007 })

And then I used powershell script to install the printer:
# Step 1 - Enable InternetPrinting feature
$Feature = Get-WindowsOptionalFeature -Online -FeatureName "Printing-Foundation-InternetPrinting-Client"
if ($Feature.State -ne "Enabled") {
        Enable-WindowsOptionalFeature -Online -FeatureName "Printing-Foundation-Features" -NoRestart
        Enable-WindowsOptionalFeature -Online -FeatureName "Printing-Foundation-InternetPrinting-Client" -NoRestart
}

# Step 2 - Install printer
$Result = Test-NetConnection <IP_ADDRESS> -Port 2404
If ($Result.TcpTestSucceeded) {
     Add-Printer -Name "PixLetter" -DriverName $PrinterDriverName -PortName "http://$($env:COMPUTERNAME):2404"
} Else {
      throw "Printer port doesn't exposed"
}

Hi   @itamardavidyan      can  you   explain   what is relation  of  powershell  script  with  use  of  ipp-printer
and    send  a full  instruction  for   create  a  virtual  printer  with  ipp-printer

@samantrader
The Powershell script seperated for 2 steps:

Enable InternetPrinting feature - I don't remember why I should enable those windows features but without enable them I can't send files to the virtual printer.
Install printer - The next command:
Add-Printer -Name "PixLetter" -DriverName $PrinterDriverName -PortName "http://$($env:COMPUTERNAME):2404"
Is a command line for adding the printer automatically to the printers list of the windows user - it's useful if you don't want that the user will add it manually

About creating virtual printer using ipp-printer you can use the code from the README.md file

Hi
If this  powershell  configuration  is  necessary  for use   ipp-printer   ?

It's not necessary because you can do each of the steps manually

I   used   exactly   this  code   but   printer  donot show  in  list of windows printer  why ?
`var fs = require('fs')
var Printer = require('ipp-printer')
var printer = new Printer('My Printer')
printer.on('job', function (job) {
console.log('[job %d] Printing document: %s', job.id, job.name)
var filename = 'job-' + job.id + '.ps' // .ps = PostScript
var file = fs.createWriteStream(filename)
job.on('end', function () {
console.log('[job %d] Document saved as %s', job.id, filename)
})
job.pipe(file)
})`

@itamardavidyan
Why  nobody   answer this question  ?

Hi
When I    run  this  command
$Result = Test-NetConnection <IP_ADDRESS> -Port 2404
powershell  return  error    :  WARNING: TCP connect to <IP_ADDRESS>:1002 failed
how  can I  fix   this  error ?

This command: var printer = new Printer('My Printer') deson't define the port of the virtual printer
Try to debug and see which port number the constructor define to the virtual printer


refactor: assert value for RxJS v7 compatibility

In RxJS v7, the type of Subject.next() will change from next(value?: T) to next(value: T) (change). No runtime behavior is affected, but this change will break users who build from source. This PR corrects types to ensure projects build successfully.
Changes

asserts T|undefined|null values to T where appropriate.
refactor instances of Subject<any> to Subject<void> so the next() method can be called without passing an argument.

All the void changes look good, Mailes should weigh in on the virtual scroll change

@MichaelJamesParsons can you update the API gold for snackbar?
yarn bazel run //tools/public_api_guard:material/snack-bar.d.ts_api.accept

The shorthand for updating the golden is yarn approve-api material/snack-bar.

Done


disable_postal_code_gather with override_service_body_id

Happens in 4.2.10.
When these two options are put together and you try to search for someone to talk to, it instead proceeds to the next menu where it asks you to search by location.  There is a conditional issues that I observed that needs to be fixed..
This condition is hit:
https://github.com/bmlt-enabled/yap/blob/968207e147cb1c7ffcd654526371b8efbe9dd557/legacy/input-method.php#L26-L27
Which causes a redirect to happen, when it's intended to go here first:
https://github.com/bmlt-enabled/yap/blob/968207e147cb1c7ffcd654526371b8efbe9dd557/legacy/input-method.php#L32-L34
I would fix this in the next version by writing tests to catch each condition.

will be fixed in 4.3.0


Feature: Bash Completion for SDKMAN

[x] I have read the CONTRIBUTING guidelines

The ergonomics of SDKMAN could be greatly improved by providing autocompletion for commands, subcommands, candidates and versions.

Hi @marc0der, I've just linked the sdkman-hooks PR to this issue. Is this enough, or should I create an additional feature request for the sdkman-hooks repository?

Don't worry about creating an issue, linking it here is perfect 👍


Add SPM support.

Thanks @makcakir
Added this commit "93d45570c6d3612a32b97d742755ef5ae106b399" via SPM and working now.
remove from pods first


ollama code coverge

Contributing to #168

Adding test for data volume name
More tests on the volume mounting

@Alirexaa I can't figure out how to get the Ollama tests to above 60% (admittedly part of it is the hook which is really hard to test), so this is probably as good a coverage as we can get (but at least it's a total over 80% now!).

@Alirexaa I can't figure out how to get the Ollama tests to above 60% (admittedly part of it is the hook which is really hard to test), so this is probably as good a coverage as we can get (but at least it's a total over 80% now!).

I think adding funtional test to ensure data volume presistance work could help us. I will take a look at it and try to add more funtional tests.


Table headers separator line unexpectedly changes on table format

Format table changes line separator that separates headers from data. Formating table puts a one space padding in each cell of this line.
This issue illustrates an example.
For example we've got this table:
| header_1 | header_2 |
|----------|----------|
| val1 | val2 |

After "Format all" we've got
| header_1 | header_2 |
| -------- | -------- |
| val1     | val2     |

As we can see, in second line the table formatter replaced some "-" signs with spaces. It was unnecessary and bad because we change table definition format.
Please, fix this because it is a common scenario - headers and separators line from this example can be created and handled with plugin TableEditor to Sublime.

I would be interested in this also.  I use Pandoc a lot, and the table parser in Pandoc seems to choke when the heading separator line has whitespace between the pipe character and a colon, as in the following example.
| header_1 | header_2 |
| :------- | :------: |
| val1     |   val2   |

Pandoc will parse this example just fine:
| header_1 | header_2 |
|:---------|:--------:|
| val1     |   val2   |

Basically, for Pandoc it seems best not to have any whitespace in the heading separator line. The whitespace in all the other cells is fine.
Would it be possible simply to remove all whitespace from the separator line in the formatting process?
If this change is something  you would prefer not to implement, could you show me the place in the code where that whitespace is added?  I've looked through it, but my javascript skills are not quite good enough for me to determine how every thing fits together.
Thanks for your time.  The extension is really well done.

Thank you for bug report and bug fix and using this extension.
I will check and merge and release it next week.
Wait a moment.

i'm planning to add config.
title : markdown header hyphen type

with space : | ----- |
no space : |-----|
minimum : |  ---  |
auto fill : chose 1 or 2 automaticaly

cf. https://help.github.com/articles/organizing-information-with-tables/

updated!
try set "tableformatter.markdown.oneSpacePadding: false"


Add .pre-commit-configuration

Add a .pre-commit-config.yaml file with linting configurations. Here's an example of some pre-commit configs I like.

Can take this up. Any action requirements that want to see in this file?

@krishnaduttPanchagnula It would be nice to see ruff run as a linter and black as a formatted for the code. And run the local unit tests with pytest.


Gas limit added in gas fees calculation

Gaslimit check in getFees() to calculate the transaction gas.

@surajsingla333  Please update the package name in the package.json along with the version and log all the changes in the CHANGELOG.


share log calculated size is unreasonable or the shared log may be damaged

Bug Report
Please answer these questions before submitting your issue. Thanks!

What did you do?

the machine was down, then restart the machine and node server
remote-command -t meta-server meta.lb.only_move_primary true
set_meta_level lively

What did you expect to see?
The node server can be restarted and no any error

What did you see instead?

the perfcounter report the shared log too large 25853163(MB) > 50000
the log show error  as soon as when the node server restart:

mutation_log.cpp:2057:read_next_log_block(): read data block body failed, size = 328 vs 676, err = ERR_HANDLE_EOF
replica_stub.cpp:552:initialize():some shared log state must be lost, smax(1301076891) vs pmax(1301079680)
replica_stub.cpp:565:initialize(): logs are not complete for some replicas, which means that shared log is truncated, mark all replicas as inactive

What version of Pegasus are you using?
pegasus-server-1.12.3-a948e89-glibc2.12-release.tar.gz

Suggestion
suggest dessart instead of derror if the shared log is damaged when restart the node server

What did you expect to see?
The node server can be restarted and no any error.
What did you see instead?
the perfcounter report the shared log too large 25853163(MB) > 50000
the log show error as soon as when the node server restart:

So what's the next result of a too-large-shared-log? Did it make the cluster unable to serve anymore? Or the replica-server is unable to start?

What did you expect to see?
The node server can be restarted and no any error.
What did you see instead?
the perfcounter report the shared log too large 25853163(MB) > 50000
the log show error as soon as when the node server restart:

So what's the next result of a too-large-shared-log? Did it make the cluster unable to serve anymore? Or was the replica-server unable to restart?

we can cleanup the node, then restart

I think we can consider mocking such case in replica's UT, by intentionally append some mutations only to the plog, without appending to the slog. Let the server restart then, and see what happens.


[1.0] Add ability to provide a top level render method

This allows to inject a custom "route handler" (hah!). This is a useful hook to render something different from react-router's default call to React.createElement. This method will be called for every component on every step of the route tree and it can conditionally return a ReactElement. This is useful when building an application with Relay.
Actual Code Example:
function render(component, {params, route}) {
  var {name, queries, component} = route;
  if (name && queries && Relay.isContainer(component)) {
    return (
      <RelayRootContainer
        Component={component}
        route={{name, params, queries}}
      />
    );
  }
}

var routes = (
  <Route component={Root} render={render}>
    <Route …>
      <Route name="app" component={App} queries={{…}} />
      <Route name="profile" component={Profile} queries={{…}} />
      <Route name="events" component={Events} queries={{…}} />
    </Route>
  </Route>
);

The application code is not affected by this; components will just receive this.props.children.
It is possible that such a render function might be useful on more steps than just the top level. In this case I would consider changing my code to walk up the matched route tree and select the first render method that is defined. If we do this, we might also want to consider walking up the matched route tree and calling all render methods (closest ones first) until one of them renders to an element.

+1

Actually I like the idea about walking up the matched routes and calling render until one of them returns a valid element. It seems like it provides the biggest option value. What do other people think?

Would this be essentially equivalent to this?
BrowserHistory.listen(function (location) {
  Router.match(location, function (error, props) {
    props.components.each(component => render(component, ...));
    React.render(<Router {...props}/>, document.body);
  });
});

The discussion in #1211 might be relevant too :+1:

No it is not because props.components are the matched component constructors. Also it would be a mutative API which I don't want to encourage people to use.

Any reason App doesn't render a RelayContainer instead? you have this.props.route available.

I've updated the example to include more than one route on the same level. Yes, what you are saying works but it is really inconvenient. It means that the boilerplate code from the render function above needs to be written out manually for every component.
Relay uses a RelayRootContainer as an anchor point for a Relay app or part of a Relay app. A RelayRootContainer takes a component and a query config (a route with {name, params, queries}).
So without this pull request, the App component would look something like this:
App.render = () => {
  return (
    <RelayRootContainer
      Component={AppContainer}
      route={{name, params, queries}}
    />
  );
};

but then Profile.render and Events.render would look identical except for the component name. This is clearly not optimal as you might have 100 routes. Even App.render = createRelayRendererFor(App) is inconvenient as it requires the developer to type out this level of indirection manually every time. It also makes it more work to convert existing views to Relay one-by-one.
Now another solution could be something like this:
<Route name="app" component={RootContainerWrapper} relayComponent={App} queries={{…}} />
<Route name="profile" component={RootContainerWrapper} relayComponent={Profile} queries={{…}} />

but I think this is worse. It means that all the async loading logic you guys built won't work the same way. If you look at this example closely it is actually quite similar to the solution in this pull request. Except with my pull request (and the suggestion I posted above about picking the closest render) we could retain component for the actual component (a RelayContainer) and we can use render on the closest level where we automatically want to wrap components with a RelayRootContainer. In the app I'm currently using this with it works really well.

Sorry, not against this idea, just making sure we're thinking about acceptable alternative
var routes = (
  <Route component={createRelayContainer(Root)}>
    <Route …>
      <Route name="app" component={App} queries={{…}} />
      <Route name="profile" component={Profile} queries={{…}} />
      <Route name="events" component={Events} queries={{…}} />
    </Route>
  </Route>
);

Seems to have the same characteristics of what you're talking about, or I'm missing something completely.

It could work if we did something like this:
function wrap(component) {
  return class extends React.Component {
    render() {
      var {params, route} = this.props;
      var {name, queries, component} = route;
      if (name && queries && Relay.isContainer(component)) {
        return (
          <RelayRootContainer
            Component={component}
            route={{name, params, queries}}
          />
        );
      }
    }
  }
}

var routes = (
  <Route component={Root} render={render}>
    <Route …>
      <Route name="app" component={wrap(App)} queries={{…}} />
      <Route name="profile" component={wrap(Profile)} queries={{…}} />
      <Route name="events" component={wrap(Events)} queries={{…}} />
    </Route>
  </Route>
);

which is fine if you look at it like this. But the problem is now that on every route change you are wiping away the whole React tree because every route has its own wrapper component and React doesn't understand that they are doing the same. This means route transitions are more expensive than they have to be.
I think giving developers the ability to modify the default children makes sense from an API perspective. Just like it was possible previously to build your own <RouteHandler />.

I updated the pull request with a new version that calls render on every route up the stack from the current one. I also added a test for this behavior, which gets a little complex but it covers all the cases.
The way it works now is that routes can define render on any level and the first render method that returns something will be used for children.
Example Nested Routes: RouteA -> RouteB -> RouteC. Assume every route has a render method: renderA, renderB, renderC. When creating children for RouteC it calls renderC. If it doesn't return anything it calls renderB. It goes up the tree until one of them returns a React element. If none of them returns anything it falls back to the default behavior of react-router.
When creating children for RouteB it will call renderB and renderA (assuming routeB doesn't return anything). For RouteA's component it will only call renderA.

Just to throw out another random idea...
var routes = Relay.wrapRoutes(
  <Route component={Root}>
    <Route …>
      <Route name="app" component={App} queries={{…}} />
      <Route name="profile" component={Profile} queries={{…}} />
      <Route name="events" component={Events} queries={{…}} />
    </Route>
  </Route>
);

then Relay.wrapRoutes could use createRoutesFromReactChildren to get a tree and post-process it, wrapping any components it needs to.
This probably doesn't address your route transition concern and would put extra strain on your lib to handle async routes/components... but just throwing out ideas.

Another crazy idea: just let createElement be passed as a prop to Router instead. Then all of the render functionality can just exist as a Relay-HoC.

It is unlikely that we are going to ship something like this as part of
Relay. Relay is not opinionated about any routing system that you may want
to use. While your suggestion might work, it would be specific to the two
libraries and react-router would need to expose the internal functions that
deal with different kinds of routing objects.
The solution in this PR is generic and can work with anything. Even if we
decide against using this, a way to overwrite the children that
react-router creates will definitely be requested by others. It's also a
feature that exists in 0.13 via , which already can be
overwritten. My initial plan was to build  but this is
way more generic.
I'm not sure I understand your other proposal about createElement. How is
it different from this PR?
On Thursday, May 21, 2015, Gerald Monaco<EMAIL_ADDRESS>wrote:

Another crazy idea: just let createElement be passed as a prop to Router
instead. Then all of the render functionality can just exist as a Relay-HoC.
--
Reply to this email directly or view it on GitHub
https://github.com/rackt/react-router/pull/1215#issuecomment-104540723.

--
Christoph Pojer
http://cpojer.net

It is unlikely that we are going to ship something like this as part of
Relay. Relay is not opinionated about any routing system that you may want
to use. While your suggestion might work, it would be specific to the two
libraries and react-router would need to expose the internal functions that
deal with different kinds of routing objects.
The solution in this PR is generic and can work with anything. Even if we
decide against using this, a way to overwrite the children that
react-router creates will definitely be requested by others. It's also a
feature that exists in 0.13 via <RouteHandler />, which already can be
overwritten. My initial plan was to build <RelayRouteHandler /> but this is
way more generic.
Unless I'm missing something, the second example seems to match the first iteration of this PR – a way to overwrite createElement, except only on the top level. I decided to change it to visit every route in the stack because the top level route shouldn't be special cased.

But the problem is now that on every route change you are wiping away the whole React tree because every route has its own wrapper component and React doesn't understand that they are doing the same. This means route transitions are more expensive than they have to be.

Are you sure about that? The component classes are only defined once upfront, so as long as only some inner routes change, the components of the outer routes should be preserved, shouldn't they? I can see that it makes a difference when transitioning to a sibling route with the same component class though.
I've felt like the Router run callback was the right place to do this kind of processing on route changes, passing everything that's needed as props to Router (similar to @devknoll 's suggestion). But with the upcoming API changes, and the addition of named routes, this render() approach might be more reasonable.
I wonder if it would be a good idea to also use it for passing async data from the change callback
function render(component, {params, route, passProps}){
  var data = passProps[route.name]; // example mapping..
  return React.createElement(component, { params, route, data });
}

BrowserHistory.listen(function (location) {
  Router.match(location, function (error, props) {
    fetchData(props, function(err, data){
       React.render(<Router {...props} passProps={data} />, document.body);
    });
  });
});

There are some changes to 1.0 API which might actually make all of this way more straightforward. When @ryanflorence comes out of the API design cage he'll tell the world. With this new not-yet-shown API, it might be possible to implement Relay integration as a middleware component. (Stay tuned!)

With the new architecture this is kind of ridiculously easy now, no pull requests needed!
https://github.com/rackt/react-router/blob/next-ryan/doc/04 Middleware/RouteRenderer.md


validation.tsv not present in qrels folder

Hi
I'm  trying to run the below code on Colab
from mteb import MTEB
from sentence_transformers import SentenceTransformer
from mteb.tasks import QuoraRetrieval

model_name = "average_word_embeddings_komninos"
model = SentenceTransformer(model_name)

evaluation = MTEB(tasks=["QuoraRetrieval"]) # Only select clustering and retrieval tasks
results = evaluation.run(model, output_folder=f"results/{model_name}")

I get the following error
Retrieval
    - QuoraRetrieval, beir, s2s

ERROR:mteb.evaluation.MTEB:Error while evaluating QuoraRetrieval: File /root/.cache/huggingface/datasets/BeIR/quora/qrels/validation.tsv not present! Please provide accurate file.
ERROR:mteb.evaluation.MTEB:Please check all the error logs at: error_logs.txt

When I check the qrels folder, I only find dev and test tsvs. This issue occurs for other tasks as well, such as MSMARCO.
Any idea what I'm doing wrong?

I've just fixed it - you can upgrade via pip install --upgrade git+https://github.com/embeddings-benchmark/mteb.git
If you're only interested in evaling on the test split, it also works with your current version by specifying the split:
from mteb import MTEB
from sentence_transformers import SentenceTransformer
from mteb.tasks import QuoraRetrieval

model_name = "average_word_embeddings_komninos"
model = SentenceTransformer(model_name)

evaluation = MTEB(tasks=["QuoraRetrieval"])
# Only select clustering and retrieval tasks
results = evaluation.run(model, output_folder=f"results/{model_name}", eval_splits=["test"])

The problem was that there's a different split name when using the old BEIR loader (dev vs validation) - This should be fixed soon when we switch back to the new BEIR HF Data Loader cc @NouamaneTazi

Got a new error.
ERROR:mteb.evaluation.MTEB:Error while evaluating QuoraRetrieval: Retrieval tasks require beir package. Please install it with pip install mteb[beir]
I had this error earlier as well, but pip install from pypi with mteb[beir] solved it. Not sure how to do the same with a git repo install

You can just do
pip install --upgrade git+https://github.com/embeddings-benchmark/mteb.git
pip install beir

Hi,
Sorry to reopen but ran into another issue with the SGPT models.
Running this:
from mteb import MTEB
from sentence_transformers import SentenceTransformer
from mteb.tasks import QuoraRetrieval

model_name = "Muennighoff/SGPT-125M-weightedmean-msmarco-specb-bitfit"
model = SentenceTransformer(model_name)
evaluation = MTEB(tasks=['ArguAna'])
results = evaluation.run(model, output_folder=f"results/{model_name}", eval_splits=["test"])

Throws this error: TypeError: __init__() got an unexpected keyword argument 'pooling_mode_weightedmean_tokens
Am I doing something wrong when it comes to SGPT models?

I think you need to run pip install --upgrade git+https://github.com/Muennighoff/sentence-transformers.git@sgpt_poolings_specb or pip install --upgrade git+https://github.com/UKPLab/sentence-transformers.git depending on if you need to use the original sentence transformers or not.
See here & this issue: https://github.com/Muennighoff/sgpt/issues/14

Thank


Combined Query does not work

Hi,
you wrote in your doc:
Use linkedfrom:"$PATH$" OR linkedto:"$PATH$" to include markers that the active note links to and also markers that link to this file.
But if I specify that term in my settings, just the first $PATH$ ist evaluated, the second is not evaluated and therefore an error occurs

What an annoying bug! I'll take care of that as soon as I get a few hours to work on the next bug-fix version.


Feature/sdk 219

Current coverage is 0.00%

Merging #44 into develop will not affect coverage as of 668d4aa

No diff could be generated. No reports for #44 found.
Review entire Coverage Diff as of 668d4aa

Powered by Codecov. Updated on successful CI builds.


(Added) Highlight box on qr scanning viewfinder

I don't think adding the executor is accomplishing anything. I think it's just where the added listener runs and it really doesn't matter if it runs on the main thread since it only runs once. Unless it can be demonstrated that this is where the CameraX processing runs, I don't want to do this. It's slower to use a background thread for our listener and then switch several times to the main thread. This is just the listener setup so it wouldn't be moving CameraX processing as a whole as far as I can tell.

You're currently hard-wiring pixel sizes based on the resolution that it ends up choosing which isn't a usable approach. The resolution of both the preview and the camera is going to vary across devices. The suggested resolution from us is just that, a suggested resolution. You're asking for 1280x720 but that's not what it's actually using and you can't make assumptions based on either the requested size or the actual size that you end up with. We can still end up with a 640x480 or 480x640 resolution regardless of what we request. I want the square to be calculated based on a proportion of the size.

You're currently hard-wiring pixel sizes based on the resolution that it ends up choosing which isn't a usable approach. The resolution of both the preview and the camera is going to vary across devices. The suggested resolution from us is just that, a suggested resolution. You're asking for 1280x720 but that's not what it's actually using and you can't make assumptions based on either the requested size or the actual size that you end up with. We can still end up with a 640x480 or 480x640 resolution regardless of what we request. The square needs to be calculated based on a proportion of the size.

I applied the last part of this disabling the image capture use case. Not sure that will help with anything but we might as well.

It also seems that this is currently just the UI without cropping what's used.

This will need rebasing since I had to roll back the QR code changes in order to do the v29 release with Pixel 5a support without the QR scanning changes being ready yet.

The status bar portion of edge-to-edge support is still broken. It also needs to cover the QR activity for it to be covering all pages.
Focus changes should be done separately.
Going to close this for now since we got the scanning square working. It would have been nice for it to be Kotlin but I didn't want to reject it based on it being more Java code based on existing Java code.


g_iVisibleMouse crash

idk what the heck should i do

Try -bindless in launch options

Which mod are you running?

Which mod are you running?

Only metaaudio.

Which mod are you running?

Only metaaudio.

I mean "valve", "gearbox", "cstrike", "bshift", or what.

Which mod are you running?

Only metaaudio.

I mean "valve" (Half-Life), "gearbox" (opfor), "cstrike" (Counter Strike), "bshift" (Blue Shift), or what.

then it's valve.

Which mod are you running?

Only metaaudio.

I mean "valve" (Half-Life), "gearbox" (opfor), "cstrike" (Counter Strike), "bshift" (Blue Shift), or what.

then it's valve.

Did you replace vanilla Half-Life's client dll (\valve\cl_dlls\client.dll) with other third-party one such as AG or HLBugFix or what?

oh yea, i did with a beta hl2 hud mod client.dll, it's in valve_addons, so deleting it wouldn't be a problem.

Which mod are you running?

Only metaaudio.

I mean "valve" (Half-Life), "gearbox" (opfor), "cstrike" (Counter Strike), "bshift" (Blue Shift), or what.

then it's valve.

Did you replace vanilla Half-Life's client dll (\valve\cl_dlls\client.dll) with other third-party one such as AG or HLBugFix or what?

oh yea, i did with a beta hl2 hud mod client.dll, it's in valve_addons, so deleting it wouldn't be a problem.

So there's a confliction between CaptionMod.dll and client.dll from "beta hl2 hud". You can either remove CaptionMod.dll or   "beta hl2 hud" to mitigate the problem.

Which mod are you running?

Only metaaudio.

I mean "valve" (Half-Life), "gearbox" (opfor), "cstrike" (Counter Strike), "bshift" (Blue Shift), or what.

then it's valve.

Did you replace vanilla Half-Life's client dll (\valve\cl_dlls\client.dll) with other third-party one such as AG or HLBugFix or what?

oh yea, i did with a beta hl2 hud mod client.dll, it's in valve_addons, so deleting it wouldn't be a problem.

So there's a confliction between CaptionMod.dll and client.dll from "beta hl2 hud". You can either remove CaptionMod.dll or   "beta hl2 hud" to mitigate the problem.

hang on let me check if that is the case.

Which mod are you running?

Only metaaudio.

I mean "valve" (Half-Life), "gearbox" (opfor), "cstrike" (Counter Strike), "bshift" (Blue Shift), or what.

then it's valve.

Did you replace vanilla Half-Life's client dll (\valve\cl_dlls\client.dll) with other third-party one such as AG or HLBugFix or what?

oh yea, i did with a beta hl2 hud mod client.dll, it's in valve_addons, so deleting it wouldn't be a problem.

So there's a confliction between CaptionMod.dll and client.dll from "beta hl2 hud". You can either remove CaptionMod.dll or "beta hl2 hud" to mitigate the problem.

after removing caption mod, i'm having this crash:

Which mod are you running?

Only metaaudio.

I mean "valve" (Half-Life), "gearbox" (opfor), "cstrike" (Counter Strike), "bshift" (Blue Shift), or what.

then it's valve.

Did you replace vanilla Half-Life's client dll (\valve\cl_dlls\client.dll) with other third-party one such as AG or HLBugFix or what?

oh yea, i did with a beta hl2 hud mod client.dll, it's in valve_addons, so deleting it wouldn't be a problem.

So there's a confliction between CaptionMod.dll and client.dll from "beta hl2 hud". You can either remove CaptionMod.dll or "beta hl2 hud" to mitigate the problem.

after removing caption mod, i'm having this crash:

okay so you have to remove beta hl2 hud as it conflicts with more than one plugin.

Which mod are you running?

Only metaaudio.

I mean "valve" (Half-Life), "gearbox" (opfor), "cstrike" (Counter Strike), "bshift" (Blue Shift), or what.

then it's valve.

Did you replace vanilla Half-Life's client dll (\valve\cl_dlls\client.dll) with other third-party one such as AG or HLBugFix or what?

oh yea, i did with a beta hl2 hud mod client.dll, it's in valve_addons, so deleting it wouldn't be a problem.

So there's a confliction between CaptionMod.dll and client.dll from "beta hl2 hud". You can either remove CaptionMod.dll or "beta hl2 hud" to mitigate the problem.

after removing caption mod, i'm having this crash:

okay so you have to remove beta hl2 hud as it conflicts with more than one plugin.

now it's working! maybe i have to make a custom dll for this hud that supports the hud but keeps the dll like steam hl1? ill have to try someday.

on a side note? why does my game blink after a loading screen?

Fixed in https://github.com/hzqst/MetaHookSv/issues/280


Add data aggregation opt-out to Homebrew FAQ

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[NA] Have you written new tests for your changes? Here's an example.
[NA] Have you successfully run brew tests with your changes locally?

Using language found in other Homebrew documentation pages, added a statement on how to opt-out from the Google Analytics anonymous data collection.

I'd rather leave this in the analytics page but thanks for the PR (because it's not a FAQ).


Exports the cluster's name

RHSTOR-5500
Expands the StorageConsumer's status to include the cluster's name which will then be exposed to the GUI back-end service.

/cc @leelavg @nb-ohad

changes look ok to me.

/lgtm


Babel runtime fail after react-scripts update to 2.1.8 (tests fail)

Is this a bug report?
YES
After I upgraded from 2.1.5 to 2.1.8, my tests (with Jest) fail, giving the same error with each run.
Cannot find module '/Users/lukasz/projects/***/node_modules/babel-preset-react-app/node_modules/@babel/runtime/helpers/interopRequireDefault' from 'user-button.test.tsx'

at Resolver.resolveModule (node_modules/jest-resolve/build/index.js:221:17)
at Object.<anonymous> (src/app/layout/user-button/user-button.test.tsx:3:30)

Downgrade to 2.1.5 fixes the problem.
Also app works properly, only tests fail
Did you try recovering your dependencies?
Yes
Environment
Environment Info:

  System:
    OS: macOS 10.14.4
    CPU: x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  Binaries:
    Node: 10.15.1 - ~/.nvm/versions/node/v10.15.1/bin/node
    Yarn: 1.13.0 - ~/.nvm/versions/node/v10.15.1/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.15.1/bin/npm
  Browsers:
    Chrome: 73.0.3683.103
    Safari: 12.1
  npmPackages:
    react: ^16.8.6 => 16.8.6
    react-dom: ^16.8.6 => 16.8.6
    react-scripts: ^2.1.8 => 2.1.8
  npmGlobalPackages:
    create-react-app: 2.1.8

Package json:
"dependencies": {
        "@rematch/core": "^1.1.0",
        "classnames": "^2.2.6",
        "downloadjs": "^1.4.7",
        "formik": "^1.5.2",
        "history": "^4.9.0",
        "include-media": "^1.4.9",
        "include-media-export": "^1.0.3",
        "leaflet": "^1.4.0",
        "lodash": "^4.17.11",
        "moment": "^2.24.0",
        "react": "^16.8.6",
        "react-compound-slider": "^1.2.1",
        "react-dom": "^16.8.6",
        "react-leaflet": "^2.2.1",
        "react-redux": "^7.0.1",
        "react-router": "^5.0.0",
        "react-router-dom": "^5.0.0",
        "react-scripts": "^2.1.5",
        "react-testing-library": "^6.1.2",
        "recompose": "^0.30.0",
        "reselect": "^4.0.0",
        "typescript": "^3.4.3",
        "use-media": "^1.3.0",
        "yup": "^0.26.10"
    },
"devDependencies": {
        "@types/classnames": "^2.2.7",
        "@types/downloadjs": "^1.4.1",
        "@types/jest": "23.3.13",
        "@types/leaflet": "^1.4.3",
        "@types/lodash": "^4.14.120",
        "@types/react": "^16.8.10",
        "@types/react-dom": "^16.8.3",
        "@types/react-leaflet": "^2.2.1",
        "@types/react-redux": "^7.0.6",
        "@types/react-router-dom": "^4.3.1",
        "@types/recompose": "^0.30.5",
        "@types/yup": "^0.26.9",
        "husky": "^1.3.1",
        "jest-dom": "^3.1.2",
        "lint-staged": "^8.1.3",
        "node-sass": "^4.11.0",
        "prettier": "^1.16.4",
        "tslint": "^5.12.1",
        "tslint-react": "^3.6.0"
    },

After bump to 2.1.8 @babel/runtime:
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>
Removing node_modules and reinstall doesn't help. BTW I use npm (not Yarn, if it matters)
Babel runtime after removing node_modules nad reinstall:
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

One more thing. After upgrade to 2.1.8, downgrade to 2.1.5 by npm i<EMAIL_ADDRESS>doesnt fix the problem because package-lock is different.
Here is the diff between working version, maybe it helps.
https://pastebin.com/d7fjE6fg

Thanks @lkostrowski.
Unfortunately there isn't anything obvious here... as I said, this is an issue we're aware of, but are having a lot of trouble identifying the root cause of.
In the meantime, are you able to fix the issue manually in your package-lock.json?

No, I wasn't trying. Will try my luck when new CRA is released with some must-have feature

Bump to 3.0.0. fixes the problem

For me I didn't have this issue before using CRA 3.

I've seen this too (outside of CRA, but with babel-preset-react-app), @maracuja-juice, and will try to investigate this weekend. Did you remove your packages and lockfile?
Can you run npm ls @babel/runtime for us and post the results here?

So I should remove my workaround, properly reinstall and then run npm ls @babel/runtime for you to investigate? I tried removing the lockfile and packages before but that didn't help.
I'm using yarn by the way.

That would help, @maracuja-juice. We need more information, so we can understand where the issue is coming from.

Okay.

Removed the workaround
deleted node_modules and yarn.lock file
ran yarn
verified that I still run into the same problem with yarn test

Here's the output of npm ls @babel/runtime
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├─┬<EMAIL_ADDRESS>│ │ │ ├──<EMAIL_ADDRESS>deduped
│ │ │ └─┬<EMAIL_ADDRESS>│ │ │   └──<EMAIL_ADDRESS>deduped
│ │ ├─┬<EMAIL_ADDRESS>│ │ │ ├──<EMAIL_ADDRESS>deduped
│ │ │ └─┬<EMAIL_ADDRESS>│ │ │   └──<EMAIL_ADDRESS>deduped
│ │ ├─┬<EMAIL_ADDRESS>│ │ │ └──<EMAIL_ADDRESS>deduped
│ │ └─┬<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>deduped
│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     └─┬<EMAIL_ADDRESS>│       └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ ├─┬<EMAIL_ADDRESS>│ │ │ └──<EMAIL_ADDRESS>deduped
│ │ └─┬<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>deduped
│ ├─┬<EMAIL_ADDRESS>│ │ └─┬<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>deduped
│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>deduped
│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>deduped
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>deduped
└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>deduped
  └─┬<EMAIL_ADDRESS>    ├──<EMAIL_ADDRESS>deduped
    └─┬<EMAIL_ADDRESS>      └──<EMAIL_ADDRESS>deduped

This is still an issue. Have you been able to investigate yet Brody?

Hi @maracuja-juice, we think we've resolved this issue now. It was complex, and it should be working in the latest v3 releases. Have you tried that? It likely won't have any breaking changes for you.

I only had this error since CRA 3.

Can I confirm, as I just had this issue two minutes ago and solved it, have you tried this?

Delete package-lock.json.
Delete node_modules folder.
Run npm i.

Yes. (yarn.lock though)

OK, thanks @maracuja-juice. Can you also share the output of yarn list @babel/runtime?
Sorry you're facing this issue...

'src/**/*.{js,jsx}':
  - prettier
  - eslint --fix
  - git add
  - npm run test

Hello @mrmckeb
I've got an issue with setupTests.js file which is actuallt not read by jest on my tests, the file is inside /src folder here's a repo url https://github.com/belyas/node-commerce/tree/master/client/src so I'm trying to access localStorage object but in vain, can you please help?

@iOiurson I think that's a different issue, could you open a new ticket and mention me? I'll pick it up. It looks like a configuration issue... assuming tests work in other cases :)

Hi @belyas, that is an interesting issue... it looks OK at first glance. Can you open a ticket for this one, so I can investigate it with you? Just mention me in the ticket and be sure to fill in the template.

Hi @mrmckeb, I'm still experiencing same problem and I'm running latest version of<EMAIL_ADDRESS>My app stopped working, so I tried creating a new app with create-react-app and yarn start, but I still got same error for the new create-react-app.

To fix it, I always copy babel\runtime\helper file from another repository and paste into every new create-react-app app I create. Is there anyway to solve this?

We ran into the same issue today and we still try to fix that. Does anybody have a clean solution yet :) ?
thanks in advance

Upgrade to latest react-scripts (3.1)
Do a clean install (remove node_modules, possibly yarn.lock)
try adding "**/babel-preset-react-app/@babel/runtime" to "nohoist" option for yarn in package.json.


Explore UI touches found in "Protocol"

They seem to have some nice UI touches that would be nice to bring into fwoosh.

Minimap

Side by side code blocks

https://motion.dev/dom/in-view


Issue connecting to data base as Backend from Cloud Config Server

I have configured - cloud-config-server for connecting to DB backend (postgreSQL ) , when i start my Config server i'm getting below error:
--------------------- Error On Startup-------
APPLICATION FAILED TO START
Description:
Invalid config server configuration.
Action:
If you are using the git profile, you need to set a Git URI in your configuration. If you are using a native profile and have spring.cloud.config.server.bootstrap=true, you need to use a composite configuration.
---------------------- End Of Error -------------------------
i have set "spring.profiles.active=jdbc" in server - application.properties file.
Config-Server Code:
config-db-server.zip
Config-Server-Client Code:
config-db-client.zip
DDL:
CREATE TABLE PROPERTIES (
application VARCHAR (10),
profile VARCHAR (10),
label VARCHAR (10),
key VARCHAR (10),
value VARCHAR (10)
);

Please try using spring-boot-starter-jdbc

Please try using spring-boot-starter-jdbc

Thank you very much @ryanjbaxter  , it works!!
Curios to know , will @RefreshScope restart Spring Application context as well ? when we do actuator/refresh.
will any of the inflight transactions gets affected when we Refresh any bean marked @RefreshScope

Curios to know , will @RefreshScope restart Spring Application context as well ? when we do actuator/refresh.

Yes

will any of the inflight transactions gets affected when we Refresh any bean marked @RefreshScope

yes


Move the Main.hs out of src directory

The executable should depend upon the library in cabal, but if the Main is in same folder as other files, it will try to compile it as part of executable creation (instead of using via library)

Already fixed. main.hs is now in src-bin


fix: Add crossorigin attribute to script HTML tags

The Problem
When an error occurs in a script that is not served by the
default server spawned by karma, the stack trace gets lost and
only the message "Script Error" is captured and reported back.
This makes it hard to pin-point where the error originated from.
The Solution
Add crossorigin attribute to generated script tags.
Solution is inspired by this article:
https://blog.getsentry.com/2016/05/17/what-is-script-error.html

To help better explain what is being fixed here, see the following images.
Here's the issue I'm experiencing due to running tests from another server (which given my setup, I require this to be the case). Notice the "Script Error" output circled in red.

With the code in this PR, I was able to get the full stack trace of the error:

I signed it!

Thanks for this. Can you please change the commit message to follow our convention

Sure thing, let me try that.

@dignifiedquire updated

Hmm, I see errors in tests. I'll take a look

I've updated the unit tests
I still haven't figured out how to update the e2e tests for cucumberjs:ci which are still failing (locally)

Looks like all checks passed.

Thanks, just one last thing can you squash the two commits into one?

Done, let's wait for the tests to run again. I've also rebased my branch.

Thanks :octocat:

My pleasure 👍

In retrospect, this "bug fix" released in a patch version (v1.1.1) is in fact an entirely new restriction that is imho considered a breaking change. Anyone using Karma with one of the test files served from another server needs to add crossOriginAttribute: false to the configuration. (And that option doesn't exist until v1.4.0).
This happens to coincide with regression fix https://github.com/karma-runner/karma/pull/2220 for https://github.com/litixsoft/karma-mocha-reporter/issues/67.
Upgrading to v1.1.1 fixed that but then broke everything else. The only way to get it fixed was to update directly to v1.4.0.
This could've been avoided if the option was disabled by default and kept opt-in until a later semver-minor or semver-major release.
Alternatively, it would've been avoided if it was supported to have Karma serve one of conf.files from a path in conf.proxies. That way it would've come from the same origin by default.


create abstract model BaseChant from which Chant and Sequence can inherit their fields

it already passed test_models before the pull request was opened; this comment is to confirm it also passes test_views_general.


support deferred libraries in smoke

This requires a small change in our codegen strategy that allows specifying the static configuration in pieces, so each deferred library can add some bits as they come along.

This issue has been moved to dart-lang/smoke#8.


After changing display resolution my custom layout is not selected

Microsoft PowerToys version
0.55.2
Running as admin

[ ] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
After changing display resolution my custom layout is not selected but the layout "Prioritätsraster"
✔ Expected Behavior
changing display resolution does not change selected layout
❌ Actual Behavior
changing display resolution does change selected layout to layout "Prioritätsraster"
Other Software
No response

This is expected behavior, as Display devices (e.g. monitors/virtual desktops/etc..) are currently preserved using unique ID consisted of few values including screen resolutions. So , if you change resolution, FancyZones will detect that as new display device. So, you'll have to select the layout again, after changing resolution to preserve that layout settings for that resolution configuration

Closing due to elapsed time and seemingly intended behavior of the tool.


Script to restart on demand workers automatically

On-demand workers get stuck for reasons like,

Overpass failure
CPU utilisation or
some other unknown reasons

@kshitijrajsharma is working on a script to restart the on demand workers whenever a run is stuck for more than 1 hour. This is a temporary fix for the Export Tool to run without any manual intervention. Architectural fixes should fix this long term.

Done ! And not needed anymore , since we are not receiving worker stuck problem ! Even if we did , script is inside the prod env !


Unclear what target Workspace info to specify ("unsupported data format : text/html; charset= utf-8")

I am a Power BI user attempting to implement incremental refresh and running into the issue defined at the bottom of https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh.
I would like to use ALM Toolkit to update my BI report (charts, measures, etc.) while leaving the underlying dataset alone on the server (which has been incrementally accruing data).
When it asks for a target workspace and I enter something like "https://app.powerbi.com/groups/76288xxx-26xx-4cxx-a7xx-xxxxxxxxxx"
I get
"unsupported data format : text/html; charset= utf-8"
I am not clear on where to go to get the correct workspace string and what format you are looking for.
Thanks for the help.

Try
powerbi://api.powerbi.com/v1.0/myorg/

From: fordmaxson<EMAIL_ADDRESS>Sent: Wednesday, May 27, 2020 9:56 AM
To: microsoft/Analysis-Services<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [microsoft/Analysis-Services] Unclear what target Workspace info to specify ("unsupported data format : text/html; charset= utf-8") (#58)
Sent by an external sender

I am a Power BI user attempting to implement incremental refresh and running into the issue defined at the bottom of https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh.
I would like to use ALM Toolkit to update my BI report (charts, measures, etc.) while leaving the underlying dataset alone on the server (which has been incrementally accruing data).
When it asks for a target workspace and I eneter something like "https://app.powerbi.com/groups/76288xxx-26xx-4cxx-a7xx-xxxxxxxxxx"
I get
"unsupported data format : text/html; charset= utf-8"
I am not clear on where to go to get the correct workspace string and what format you are looking for.
Thanks for the help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/Analysis-Services/issues/58, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGCJFWUAL3GKEDSXBPLQ6JTRTUL2NANCNFSM4NMFC32A.

Thanks for response.
That got me a "ClaimsToken Authority Not Found"
Is there any supporting installs required?   Where does my login and password come into play here?

Is your workspace on a Premium capacity? (xmla only works on Premium). If yes, Dylan's format is correct, but you can confirm by copying from the workspace settings.
https://docs.microsoft.com/en-us/power-bi/admin/service-premium-connect-tools#connecting-to-a-premium-workspace

OK, I am not on Premium, but we have purchased Embedded via an A1 server on Azure.
I dug through more of your documentation and went and installed Visual Studio Community and installed the 2 extensions.  At that point I just left it running.  Have not pulled any code into Visual Studio.
So success!  I am now able to get ALM Toolkit to run a comparison between my pbix on Desktop and what has been Published.
I inserted a simple text box into my pbix report view.  Unfortunately, I see nothing in the comparison tool that caught this.  My goal is to leave all the data alone and just send up the new page with the new text box.
Help?

Great. Glad you got past that hurdle.
If you're on Premium (including A skus) you shouldn't even need VS or the extensions if all you want to do is run ALM Toolkit.
It won't pick up (or deploy) report changes. It's only for datasets. You may want to copy the visuals into a separate live connect report to separate it from the dataset for ease of redeployment. Deploying the report alone normally doesn't have much overhead

Very frustrating, Microsoft keeps having us have to upgrade, change, switch to something else to get features working.  The doc at https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh should be updated to indicate ALM can't update just the report.  It's misleading and the whole point should be how do you update the report without messing up the dataset that used incremental refresh.
Our datasets query mySQL.  Not sure if I can do a live connect report as a result.  Also not sure if live connect is available on our embedded A1, if there is a cost impact, performance impact.  More research and hunting...sigh
Thank you for your help though.

That's a fair point about updating the documentation about this. I'll submit the request today.
There are technical reasons why XMLA write doesn't work on Pro. We could enable read only access, but currently focusing on getting it (& large models) to GA.
Not sure I understand the live connect over mySQL scenario, but there should be no feature loss on an A1 AFAIK


No map data shown for "London, United Kingdom"

See: https://staging.eahub.org/profile/14037

Worked for me. lat/lon updates once you save changes to your profile, is this what you're doing?


Logging & Debugging the npm script vscode:uninstall hook for extension authors

Need/Requirement
I am building an extension and would like to ensure when my extension in uninstalled that I get a telemetry event so I can track uninstall numbers.
uninstall.ts
import TelemetryReporter from 'vscode-extension-telemetry';

// all events will be prefixed with this event name
const extensionId = 'iis-express';

// extension version will be reported as a property with each event
const pkgJson = require('../package.json');
const extensionVersion = pkgJson.version;

// the application insights key (also known as instrumentation key)
const key = 'e0cc903f-73ec-4216-92cd-MY_AWESOME_KEY';

// telemetry reporter
// create telemetry reporter on extension activation
const reporter:TelemetryReporter = new TelemetryReporter(extensionId, extensionVersion, key);
reporter.sendTelemetryEvent('iisexpress.uninstall');

console.log('hello world I AM UNINSTALLED');

Package.json script
"vscode:uninstall": "node ./out/uninstall"
Why
My above code did not work, but I have no insight into why or went wrong. I would love to be able to use the debugger or see some logs in order to help understand what is going wrong. My current workflow is to create the .visx of the extension and install it manually into VSCode Insiders and then uninstall it. Not the most fun workflow to trial & error something without any insights into what is happening.
Bonus
If you know how to solve my telemetry problem I would be grateful 😍

My current way of debugging is writing a JSON object to a text file, again not the most friendly developer experience
It seems 'vscode' is not available to use in this uninstall hook, as soon as I remove them from my example code below then its all fine & something is written to disk.
Debugging with a file written to disk 😱
Is vscode NPM package & some vsacode.env properties available ?
import * as fs from 'fs';
import * as os from 'os';
import * as vscode from 'vscode';

// extension version will be reported as a property with each event
const pkgJson = require('../package.json');
const extensionVersion = pkgJson.version;

const commonProperties = Object.create(null);
commonProperties['common.os'] = os.platform();
commonProperties['common.platformversion'] = (os.release() || '').replace(/^(\d+)(\.\d+)?(\.\d+)?(.*)/, '$1$2$3');
commonProperties['common.extname'] = 'iis-express';
commonProperties['common.extversion'] = extensionVersion;

// These seem not to be available or to use VSCode
commonProperties['common.vscodemachineid'] = vscode.env.machineId;
commonProperties['common.vscodesessionid'] = vscode.env.sessionId;
commonProperties['common.vscodeversion'] = vscode.version;

fs.writeFileSync('c:/code/test-uninstall.env', JSON.stringify(commonProperties));

VSCode Specific ENV variables available in uninstall hook
I then thought there maybe some useful or magic stored in ENV Variables that I could use and done the following
const envValues = process.env;
fs.writeFileSync('c:/code/test-uninstall.env', JSON.stringify(envValues));

And in there are a couple of VSCode specific ENV variables, so the uninstall script is aware that it has been run from VSCode but seems we do not have access to the vscode npm package
"VSCODE_CWD": "C:\\Users\\warre\\AppData\\Local\\Programs\\Microsoft VS Code Insiders",
"VSCODE_IPC_HOOK": "\\\\.\\pipe\\9260d5401ef6df01ef46190fa2e30e66-1.48.0-insider-main-sock",
"VSCODE_LOGS": "C:\\Users\\warre\\AppData\\Roaming\\Code - Insiders\\logs\\20200731T120256",
"VSCODE_NLS_CONFIG": "{\"locale\":\"en-us\",\"availableLanguages\":{},\"_languagePackSupport\":true}",
"VSCODE_NODE_CACHED_DATA_DIR": "C:\\Users\\warre\\AppData\\Roaming\\Code - Insiders\\CachedData\\c9a2f78283b6e5ef708fb8869e2a5adaa476e42f",
"VSCODE_PID": "5440"


trace: warning: mdadm: Neither MAILADDR nor PROGRAM has been set. This will cause the mdmon service to crash.

Describe the bug
After updating the unstable channel to the recent version, and trying to run nixos-rebuild switch, I get this warning.
Steps To Reproduce
Steps to reproduce the behavior:

Update nix-channel (unstable)
Run nixos-rebuild switch
Trace will show on the console

Expected behavior
-
Screenshots
-
Additional context
I am not sure how this trace could affect the working of my current instance.
Notify maintainers
@Ekleog
@arcnmx
@yu-re-ka
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.51, NixOS, 23.11 (Tapir), 23.11pre521611.e56990880811`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(ashvith): `""`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I also noticed this warning, but why do you think I am a maintainer of an affected module or package? :D

@ctheune @mweinelt

@yu-re-ka oh, apologies. In the history of commits, your name came on the second list, so I thought adding the recent contributors made sense.

@Ashvith10 are you using software raid? if so, does your /etc/mdadm.conf show any of the two options? does the mdmonitor service run?

@ctheune I believe that I am not using raid. My configuration file is closest to the default GNOME desktop setup, and with the exception of enabling firewall and using GRUB. Also, /etc/mdadm.conf is empty.

I am experiencing this as well. I think it is not GRUB-related, as switching to systemd-boot still trigger this warning.

Alternatively, would you mind double checking your hardware-configuration.nix?

@ctheune the default value of boot.swraid.enable is true for stateVersions older than 23.11

Hmm. Interesting. That's a weird combination we end up with ... :) I'll think about that.

@yu-re-ka made the right observation. The options boot.swraid.mdadmConf and boot.swraid.enable aren't in 23.05, but in the unstable channel. But I've never touched these settings before.

The issue is that it was enabled silently and by default previously (which is a bit weird because that basically means there are lots and lots and lots of systems out there with a non-functional broken unit an "unclean" overall systemd state ... o_O)

Ooooooooh. Maybe those systems aren't really running with broken systemd states. Would you guys mind checking? I think the complexity of the software raid module working on upstream systemd units and upstream udev rules that poke each other might mean that if it's enabled but not running then it won't ever trigger the monitor unit ... maybe ... Brrrrrrr. This thing is a bit of a nightmare.

Just noticed this error on a rebuild.
Not sure if related, but I run on ZFS root.
I see in the docs for this option https://search.nixos.org/options?channel=unstable&show=boot.swraid.enable&from=0&size=50&sort=relevance&type=packages&query=swraid that the logic for defaulting it to true is simply a check for whether your stateVersion is older than 23.11. Mine is 22.05, which I guess is why it's true, but I don't think it should be. Not sure why the logic for defaulting this to true has anything to do with the stateVersion (or more particularly I guess, why it ONLY has to do with the stateVersion...)

I get this error message when running nixosTest on package where we definitely don't set any raid array.

Maybe those systems aren't really running with broken systemd states. Would you guys mind checking?

Can you share how can we check the same? What should we look for while checking out journalctl?

I am quite sure this is what happened:

boot.swraid.enable used to default to true on all systems (no matter if they were actually using raid or not). This would just mean it supports booting from raid, but nothing would break if there was no raid configured.
People noticed that we don't need to ship these units on systems where they are never used/activated, and built a detection into nixos-generate-config to dynamically set boot.swraid.enable in hardware-configuration.nix when required.
The default was then changed to false for systems with stateVersion >= 23.11, because older systems that were installed with a version of nixos-generate-config that did not detect and enable the option might depend on it being implicitly enabled
The warning was added for all systems where the boot.swraid.enable is true, but additional config options are not set

My suggestion: Add a condition to only show the warning on systems with stateVersion >= 23.11, since we can't assume the users of older systems actually intended to use swraid functionality.

A link to this issue or a little more text around boot.swraid.enable would also be helpful. The current warning requires reading this issue to understand what's actually being complained about.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/dict-offline-version/33004/2

Not sure if the Nix language has something like an "only set this option if it's an understood/defined option" function

@0mp it's possible, but it's not very pretty. You'd need to inspect the options argument that's passed to your module to see if the option is there, something like
{ options, config, ... }: {
  config.boot.${if options.boot ? swraid then "swraid" else null} = ...;
}

Where we rely on the fact that if the attribute name is null, nix ignores it (as documented in the manual).

@yu-re-ka can I remove the boot.swraid.enable option, now that it is disabled by default?

@Ashvith10 the way you phrase it: no. but also I might be missing context.

@yu-re-ka I'm still not sure if I understand the new changes well enough: Is boot.swraid.enable a compulsory option in the configuration.nix file? Because most general users don't want this enabled by default, right? So, naturally, wouldn't it make sense to false as the default value, so as to not use raid, and also avoid the warning?

@yu-re-ka I'm still not sure if I understand the new changes well enough: Is boot.swraid.enable a compulsory option in the configuration.nix file, starting from 23.11? Because most general users don't want this enabled by default, right? So, naturally, wouldn't it make sense to false as the default value, so as to not use raid, and also avoid the warning?

No, it's not a compulsory option. It's just enabled by default if your system.stateVersion is older than 23.11. If it's 23.11 or higher, then it's disabled by default.

@ctheune is it possible to add a parameter that disables the monitor service?
I have mdmonitor disabled this way, but a warning pops up:
  systemd.units."mdmonitor.service".enable = false;

The problem with that is that the services are enabled/disabled imperatively and dynamically by the udev rules. To clarify: do you have any swraid volumes in your system?

Not sure if messing around with the stateVersion has screwed my instance of NixOS, but now I do not get any warning while rebuilding, even after reverting the stateVersion back to 23.05. But earlier, when my stateVersion was untouched at 23.05, I had to manually add the option to disable.

We did change the situation so that systems that rely on implicit configuration from older stateVersions will not generate the warning any longer.

To clarify: do you have any swraid volumes in your system?

Yes, there is one volume.
cat /proc/mdstat

Personalities : [raid1]
md127 : active raid1 sda2[0] sdc2[1]
      2097088 blocks [2/2] [UU]

unused devices: <none>

For a long time in boot logs I encountered an error when starting mdmonitor. In the end I just turned it off.

In that case, I'd strongly recommend to actually configure it. It's fine to add a non-sensical email address (nobody@example.com). The dynamic tooling that mdadm does (with a whole suite of pre-defined systemd units and udev rules that interact dynamically) isn't really made to override this from a nixos environment. As its so dynamic we also decided to not re-invent the wheel and try to play continuous catch up with the upstream project by replicating their very intricate work.

Ok. Just need to add an email address? Or should PROGRAM also be specified?

One of either is sufficient. I'd use an email if you don't care.

Yeah, I'd suggest to add a non-functional example email in that config to silence the warning and get the mdadm working in an installation environment.

If you don't use raid, then just set boot.swraid.enable = false;

@ctheune or is setting the PROGRAM to /dev/null  a good idea?

Not sure whether /dev/null will cause issues. Maybe /usr/bin/true would be more appropriate here.

Not sure if I should open a new issue or not, but I found this issue while running into the same thing. That being said, instead of mdadm logging to an email address or a program, you can also make it log to syslog. Annoyingly though, it cannot be configured to do that from mdadm.conf. I had to override the mdmonitor systemd unit file in a roundabout way (couldn't directly override the  ExecStart= command, and the unit file was ending up with two because mdadm packages its own services files instead of the nix module creating them. Might still be a better way to do this though):
  # Override mdmonitor to log to syslog instead of emailing or alerting
  systemd.services."mdmonitor".environment = {
    MDADM_MONITOR_ARGS = "--scan --syslog";
  };

mdmonitor.service works now, without having MAILADDR or PROGRAM specified, and logs to syslog as expected. Perhaps having an option boot.swraid.syslog might be nice to allow this behavior while also supressing the warning? Does allow avoiding redoing too much of the upstream mdadm tools if I understand correctly.


A problem appeared when i run quick-start-Realtime.sh

The whole cluster(zookeeper, kafka, pinot broker, pinot server, pinot controller) can be start.
"netstat -npl|grep java "shows that port:2191,2123,19092,7000,8000,9000 are open.
Pinot broker return "null", when i send a query.
{
    "traceInfo": {},
    "numDocsScanned": 0,
    "aggregationResults": [],
    "timeUsedMs": 0,
    "segmentStatistics": [],
    "exceptions": [],
    "totalDocs": 0
}

Are there some where delay time should be longer?

Can you run pinot-admin.sh showClusterInfo
On Apr 5, 2016 11:08 PM, "ChenJianJunCJJ"<EMAIL_ADDRESS>wrote:

The whole cluster(zookeeper, kafka, pinot broker, pinot server, pinot
controller) can be start.
"netstat -npl|grep java "shows that port:2191,2123,19092,7000,8000,9000
are open.
Pinot broker return "null", when i send a query.
{
"traceInfo": {},
"numDocsScanned": 0,
"aggregationResults": [],
"timeUsedMs": 0,
"segmentStatistics": [],
"exceptions": [],
"totalDocs": 0
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/linkedin/pinot/issues/100

The Cluster Info is:
`Opening socket connection to server localhost/<IP_ADDRESS>:2123
Socket connection established to localhost/<IP_ADDRESS>:2123, initiating session
Session establishment complete on server localhost/<IP_ADDRESS>:2123, sessionid = 0x153ea9f87d50009, negotiated timeout = 30000
zookeeper state changed (SyncConnected)
Connecting to Zookeeper at: localhost:2123
!!com.linkedin.pinot.tools.admin.command.ShowClusterInfoCommand$ClusterInfo
brokerInfoList:

name: Broker_<IP_ADDRESS>_7000
state: ONLINE
tags: [DefaultTenant_BROKER]
clusterName: QuickStartCluster
controllerInfo: {leaderName: <IP_ADDRESS>_9000}
serverInfoList:
name: Server_<IP_ADDRESS>_8000
state: ONLINE
tags: [DefaultTenant_OFFLINE, DefaultTenant_REALTIME]
tableInfoList:
segmentInfoList: []
tableName: meetupRsvp_REALTIME
tag: meetupRsvp_REALTIME
 There are another zookeeper too,  its address is "localhost:2191".

Thanks!

I find two zookeeper started. The ones address is "localhost:2191", anothers "localhost:2123".
Kafka start in "localhost:2191", Pinot cluster start in  "localhost:2123".It sames Kafka and Pinot cluster not in the same zookeeper.It is that OK?
`
_zookeeperInstance = ZkStarter.startLocalZkServer();// "localhost:2191"
final KafkaServerStartable kafkaStarter =
    KafkaStarterUtils.startServer(KafkaStarterUtils.DEFAULT_KAFKA_PORT, KafkaStarterUtils.DEFAULT_BROKER_ID,
        KafkaStarterUtils.DEFAULT_ZK_STR, KafkaStarterUtils.getDefaultKafkaConfiguration());

`
but
  public void startAll() throws Exception {     StartZookeeper();//"localhost:2123"     StartController();     StartBroker();     StartServer();   }

There should be only one zookeeper started at 2123. Can you print the
output of ./quick-start-realtime.sh.
On Wed, Apr 6, 2016 at 1:43 AM, ChenJianJunCJJ<EMAIL_ADDRESS>wrote:

I find two zookeeper started. The ones address is "localhost:2191",
anothers "localhost:2123".
Kafka start in "localhost:2191", Pinot cluster start in
"localhost:2123".It sames Kafka and Pinot cluster not in the same
zookeeper.It is that OK?
`
_zookeeperInstance = ZkStarter.startLocalZkServer();// "localhost:2191"
final KafkaServerStartable kafkaStarter =
KafkaStarterUtils.startServer(KafkaStarterUtils.DEFAULT_KAFKA_PORT, KafkaStarterUtils.DEFAULT_BROKER_ID,
KafkaStarterUtils.DEFAULT_ZK_STR, KafkaStarterUtils.getDefaultKafkaConfiguration());
`
but
public void startAll() throws Exception {
StartZookeeper();//"localhost:2123"
StartController();
StartBroker();
StartServer();
}
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/linkedin/pinot/issues/100#issuecomment-206223221

if [ -z "$JAVA_OPTS" ] ; then
  ALL_JAVA_OPTS="-Xms1G -Xmx1G -Dlog4j.configuration=conf/quickstart-realtime-log4j.properties"
else
  ALL_JAVA_OPTS=$JAVA_OPTS
fi

exec "$JAVACMD" $ALL_JAVA_OPTS \
  -classpath "$CLASSPATH" \
  -Dapp.name="quick-start-realtime" \
  -Dapp.pid="$$" \
  -Dapp.repo="$REPO" \
  -Dapp.home="$BASEDIR" \
  -Dbasedir="$BASEDIR" \
  com.linkedin.pinot.tools.RealtimeQuickStart \
  "$@"

It can`t work also, when i was try to started realtime flow with script. I followed tutorial:https://github.com/linkedin/pinot/wiki/How-To-Use-Pinot
Here is my step:
bin/pinot-admin.sh StartZookeeper &

bin/pinot-admin.sh StartController &

bin/pinot-admin.sh StartBroker &

bin/pinot-admin.sh StartServer &

bin/pinot-admin.sh AddSchema -schemaFile flights-schema.json –exec

bin/pinot-admin.sh AddTable -filePath flights-definition.json -exec

bin/pinot-admin.sh StartKafka &

bin/pinot-admin.sh StreamAvroIntoKafka -avroFile flights-2014.avro -kafkaTopic flights-realtime &

When i posted a query to pinot broker ,pinot return null.


Add negation support to FindSourceFiles

Eg **/!(CertainFileName)IT.java, like HasSourcePath used to support.

Fixed in

https://github.com/openrewrite/rewrite/pull/3980


Validation messages for nested embeds

👋 First of all cheers for making this library!
I'm currently experiencing some issues with validating nested embeds and hope ya can provide some insights. I have the following data-structure:
%{
  foo: %{
    bar: %{ <= Polymorphic embed
       __type__: "x",
      title: "test",
      images: %{ <= embeds_one
        large: "https://foo.bar/x.png",
        small: "https://foo.bar/x.png",
      }
    }
  }
}

Where the field title is required and so are the fields large and small under images.
With the current implementation it will return the correct validation error for the title field (e.g. required field) but will not show any validation errors for fields under images. Any ideas on how to resolve this?

Hi there!
Could you try with the following branch?
{:polymorphic_embed,
  git: "git://github.com/mathieuprog/polymorphic_embed.git",
  branch: "nested_embeds_errors",
  override: true}

Hey! Awesome that seems to be working! 🎉


Add verbiage around privacy/data flow

I love this idea, but I think it would help alleviate security concerns if there was clear verbiage/architecture diagram about how data is captured in the README.

Thanks Troy! I've added that information.


SSL->session double free after ssl3_send_alert()

I recently upgraded an OmniOS system to a new release, which also upgraded OpenSSL from 3.0 to 3.1.
Since that upgrade, I have been seeing frequent crashes in Cyrus IMAP that I believe to be an issue with OpenSSL. It's of course possible that Cyrus is not correctly using the API but I haven't been able to spot anything there.
This is a system-provided OpenSSL package:
mailstore0# openssl version
OpenSSL 3.1.4 24 Oct 2023 (Library: OpenSSL 3.1.4 24 Oct 2023)

The following analysis is from a core file created while the application was running under the illumos libumem memory allocator, with debugging turned on.
The crash occurs when attempting to free an SSL structure via SSL_free()
fffffaffffdf8a60 libcrypto.so.3`CRYPTO_free_ex_data+0x4c()
fffffaffffdf8a80 libssl.so.3`SSL_SESSION_free+0x44()
fffffaffffdf8ab0 libssl.so.3`SSL_free+0x14e()
fffffaffffdf8ae0 libcyrus_imap.so.0.0.0`tls_reset_servertls+0x2b(46fcd0)
fffffaffffdf8b60 service_main+0x438(2, a34f20, fffffaffffdfb8a0)
fffffaffffdfb830 main+0x71c(2, fffffaffffdfb888, fffffaffffdfb8a0)
fffffaffffdfb860 _start_crt+0x87()
fffffaffffdfb870 _start+0x18()

The SSL object concerned was originally allocated by SSL_new(), as can be seen by looking at the allocation stack trace:
> 46fcd0/K | ::whatis
d87010 is d87000+10, allocated from umem_alloc_8192:
            ADDR          BUFADDR        TIMESTAMP           THREAD
                            CACHE          LASTLOG         CONTENTS
          d8aee0           d87000  10cdb04daa6b9b7                1
                           9d7028           8f3c00                0
                 libumem.so.1`umem_cache_alloc_debug+0x213
                 libumem.so.1`umem_cache_alloc+0xe3
                 libumem.so.1`umem_alloc+0x9f
                 libumem.so.1`umem_malloc+0x46
                 libcrypto.so.3`CRYPTO_zalloc+0x11
                 libssl.so.3`SSL_new+0x3b
                 libcyrus_imap.so.0.0.0`tls_start_servertls+0xaf
                 cmd_starttls+0x82
                 service_main+0x684
                 main+0x71c
                 _start_crt+0x87
                 _start+0x18

The crash occurs because SSL->session was previously freed in ssl3_send_alert():
> 46fcd0/K | ::print SSL session | ::whatis
df9b50 is df9b40+10, freed from umem_alloc_1152:
            ADDR          BUFADDR        TIMESTAMP           THREAD
                            CACHE          LASTLOG         CONTENTS
          dfae00           df9b40  10cdb04e39240fa                1
                           9b8028           7e1c00                0
                 libumem.so.1`umem_cache_free_debug+0x16e
                 libumem.so.1`umem_cache_free+0x48
                 libumem.so.1`umem_free+0xb4
                 libumem.so.1`process_free+0x111
                 libumem.so.1`umem_malloc_free+0x1d
                 libssl.so.3`SSL_CTX_remove_session+0xee
                 libssl.so.3`ssl3_send_alert+0xdd
                 libssl.so.3`ossl_statem_fatal+0xb0
                 libssl.so.3`ssl3_read_n+0x405
                 libssl.so.3`ssl3_get_record+0xb5
                 libssl.so.3`ssl3_read_bytes+0x248
                 libssl.so.3`ssl3_read+0x60
                 libssl.so.3`SSL_read+0x29
                 libcyrus.so.0.0.0`prot_fill+0x19e
                 service_main+0x3b9

Looking at ssl3_send_alert():
https://github.com/openssl/openssl/blob/58eeb4350ca89c52d603b42119a0893129a25c09/ssl/s3_msg.c#L60-L62
The call to SSL_CTX_remove_session(s->session_ctx, s->session); seems problematic as it is possible that s->session was freed if the reference count dropped to 0, but nothing sets s->session = NULL.
Please let me know if there is anything I can do to help track this down.

The call to SSL_CTX_remove_session(s->session_ctx, s->session); seems problematic as it is possible that s->session was freed if the reference count dropped to 0, but nothing sets s->session = NULL.

Hmmm. But this should never happen. The SSL object itself should be holding a reference, and the session cache held in s->session_ctx should also be holding a reference. Therefore the ref count should always be at least 2 prior to calling this function at this location.
Does Cyrus IMAP ever call SSL_SESSION_free directly? Plausibly if the ref count is decremented incorrectly, then it would not cause a problem at the site of the incorrect free call, but later on when SSL_free is called as you are experiencing.

Thanks for looking.

Does Cyrus IMAP ever call SSL_SESSION_free directly?

It does, in a few places. I'll see if I can reproduce this by triggering ssl3_send_alert() and watch the reference - I'll report back when I have more data.

I am suspicious of a change fairly recently in Cyrus IMAP - https://github.com/cyrusimap/cyrus-imapd/commit/a3523d4067c502a52cb7ee859c1493d1a980b7e0
I am now running a build with this patch reverted. It was previously crashing several times a day so I'll be fairly confident if there are no crashes in the next 24 hours.

@citrus-it Yeah, that change is wrong. The SSL_SESSION objects are refcounted but the refcount is not bumped when this the remove_session_cb is called, so there should be no SSL_SESSION_free() call done. If they are seeing leaks under valgrind there is probably another case where there is a missing SSL_SESSION_free() call but this place is not right.

Thank you, and apologies for wrongly assuming this was a problem with OpenSSL. I've opened https://github.com/cyrusimap/cyrus-imapd/issues/4785 and will close this issue.


why the process of sending event is single threaded(goroutine) ?

Problem Statement
I see in the code base that all of events send to a single channel and that process with a single goroutine.
Is there any reason for that? if our code want to send a lot of events, most of them drop but we want to have track of all of them.
Solution Brainstorm
We can add another custom transport type to handle event with more workers.

do you accept if I make a PR for that?

Most likely not, as I fail to see the issue at hand. Potentially, there might be cases were an error event could be dropped due to the queue being full. If you have indeed such high throughput, it's more likely that you'll get rate-limited server side, so all events get's dropped anyways.


remove allocations + optimize them

For better performance you want to remove allocations and store the state (ie string escaped or not etc) on the stack, if possible.
Check the file size to estimate, if allocation is necessary.
Also: I dont see that you use arena allocation. Did I miss that?

We were of the same thinking initially, and our first (unreleased) zsv version used alloca and other means to allocate on the stack instead of heap for the parser state memory. To our surprise, the benchmark figures showed no material improvement, so we decided against it to keep the code simple and more portable, and to allow for higher limits for certain options that impact memory usage.
If there is evidence that may contradict our findings and that would suggest that changing its current heap calls to stack would have a material impact on performance, we'd be happy to review it and reconsider. The best form of that evidence would be a pull request accompanied by some benchmark figures, but we'd be happy to look at other forms


Geometry Filtering

Users can use draw layer as an input and filter their selected layer by this geometry. If target layer is a MultiPolygon layer we need to use turf to decide this polygons inside the drew geometry. If target layer is a LineString or Point layer we can use maplibre expression "within" or turf

We will use turf.js for polygon filtering. This functionality requires each polygon to have a unique identifier within its properties section, which could be labeled as id, gid, uuid, or another term. When applying a geometry filter, users must specify the name of this unique identifier property; without it, the filtering process cannot be performed. For point and linestring geometries, there is no need to define such an identifier.

Users cannot apply a geometry filter on layers that contain multiple types of geometries.


properly tagging storage option based on zcl.json

Codecov Report

Merging #1140 (e15a46e) into master (142858f) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1140      +/-   ##
==========================================
- Coverage   65.21%   65.20%   -0.01%
==========================================
  Files         170      170
  Lines       18213    18212       -1
  Branches     3922     3922
==========================================
- Hits        11877    11875       -2
- Misses       6336     6337       +1

Files Changed
Coverage Δ

src-electron/db/query-config.js
80.50% <ø> (ø)

src-electron/zcl/zcl-loader-silabs.js
94.42% <100.00%> (-0.01%)
:arrow_down:

... and 1 file with indirect coverage changes

Also @paulr34 this does not in fact fix https://github.com/project-chip/zap/issues/543.  What was it trying to fix?

@bzbarsky-apple it fixes this https://github.com/project-chip/zap/issues/1110 but in my opinion it was the first step in the natural progression of fixing all of the attribute storage issues. The front end needs to reflect reality before I can fix anything else. Will work on that one ASAP.

also @bzbarsky-apple this issue https://github.com/project-chip/zap/issues/543 I have this one fixed locally but it requires me to change the XML files. Working on making a couple PR's.

@bzbarsky-apple it fixes this https://github.com/project-chip/zap/issues/1110

Saying that in the description, or at least linking the issue would have been helpful.  No idea how someone is supposed to review a PR if it does not say what it's trying to do.


Enable sitemap.xml

Fixes https://github.com/Kotlin/dataframe/issues/697
enables sitemap according to https://www.jetbrains.com/help/writerside/generate-sitemap.html

@Jolanrensen thanks for carrying about this question

We need to check with WriterSide that our version gets updated so the sitemap generation feature works. It probably won't hurt to merge this already, waiting for the update, but we need to take into account it won't work right away.


Lost scroll position after fetch balances

Small issue after this improvement https://github.com/beefyfinance/beefy-app/pull/143.
If scroll down to show additional vaults and then wait for balance refresh - scroll position will be lost and only initial 10 vaults become visible.
Easier to reproduce locally if change fetch interval to 1-3 seconds here:
https://github.com/beefyfinance/beefy-app/blob/d24adacf5adc5fae09f672409b3cda8ba37f3fc2/src/features/vault/components/Pools/Pools.js#L14

@9ineMile maybe you can take a look on this one 🙏


Whats the difference between jest-enzyme vs installing jest & enzyme

Hi,
I was wondering what the difference is between installing jest-enzyme vs. just installing jest and enzyme separately.
Thanks,
Derek

Hey @darewreck54
jest-enzyme compliments jest + enzyme. To explain a little more:
jest is a test runner.
enzyme is a utility library for testing React components.
jest-enzyme is a set of matchers which are added to jest to simplify using enzyme.
Here is an example with and without this library.
// without jest-enzyme
const wrapper = mount(<Component className="bar" />);

expect(wrapper.props().className).toBe('bar');

// WITH jest-enzyme
const wrapper = mount(<Component className="bar" />);

expect(wrapper).toHaveProps('className', 'bar');

I'm going to close this issue as there isn't anything for me to action on. Feel free to keep asking questions here though!


GeoSparql Documentation Contains Wrong WKT Literals

The documentation on using GeoSPARQL at http://docs.rdf4j.org/programming/#_geosparql contains both example triples and a SPARQL query. The triples encode the locations of Tower Bridge and the Eiffel Tower  as WKT literals each containing a single POINT object. The sample query then calculates the distance between them as being<PHONE_NUMBER>0928696 kilometres. Unfortunately the answer is wrong as the real distance between them is only 334.355 kilometres (see this WGS-84 distance calculator if you want to be sure).
The problem isn't the distance calculation though, rather the locations in the sample data are wrong. A POINT object encoded as WKT should list the coordinates as X Y, which means when representing a geographical location we need Longitude Latitude, unfortunately the example triples list the locations as Latitude Longitude which results in the erroneous distance result.
I can't find the documentation in this repo or I'd have done a pull request, but the sample data should read as follows
@prefix geo: <http://www.opengis.net/ont/geosparql#> .
@prefix sf: <http://www.opengis.net/ont/sf> .
@prefix ex: <http://example.org/> .

ex:eiffelTower a ex:Landmark ;
          geo:hasGeometry ex:coordinates-et.
ex:coordinates-et a sf:Point;
        geo:asWKT "POINT(2.2945 48.8584)"^^geo:wktLiteral .
ex:towerBridge a ex:Landmark ;
          geo:hasGeometry ex:coordinates-tb.
ex:coordinates-tb a sf:Point;
        geo:asWKT "POINT(0.0754 51.5055)"^^geo:wktLiteral .

Thank you for reporting this, there is actually another (far less relevant) error: the Tower Bridge is located in the Western hemisphere, thus the X coordinate should read minus 0.0754.
Note that the calculated distance in the corrected example can still be off by a few km, since spatial4j simplifies calculations by modeling the Earth as a perfect sphere (see #1161)

Oh yes, I hadn't even spotted the East/West issue with Tower Bridge.

Should be fixed.
In case you were wondering, the documentation resides in the https://github.com/eclipse/rdf4j-doc (subproject / repo), but all issues are tracked here in the "main" rdf4j repo.
Feel free to create a PR if you would spot any other issue.
(in that case, there is also the small formality of creating an Eclipse account and signing the Contributor Agreement... https://github.com/eclipse/rdf4j/blob/master/.github/CONTRIBUTING.md)

Looks good to me, thanks for sorting it so quick. If I spot anything else, I'll jump through the hoops for the CLA and do a PR now I know where everything lives.


android splash image distortion

Home screen image is squashed when using the android app. It's either not wide enough or too tall. It looks fine when viewed with just a browser.

@Nate-Wessel What model phone are you using? OS version?

I used two different devices and got the same problem.
The first is a Motorola phone, model #XT907 running 4.4.2. The second is an Asus Tablet, model #K010 running 4.4.2.


Distinguish between research and clinical group

This should be specified when the group is created. Once created, this should be immutable.

Also need to define the difference between client-facing and researcher-facing form


Some documents include translations in Korean

Some additional content has been included in the Korean-translated documents.
Fixed typos in documentation
Added content to use_versatiles_in_qgis.md

Wow! Thank you so much!


⚠ Bofrost.nl has degraded performance

In 99edcb8, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 2713 ms

Resolved: Bofrost.nl performance has improved in 30a7871.


When typing in the top bar, make Ctrl+Enter add the item (same as clicking "+ Add as todo")

Version: v1.3.1
Description:
I would like to request the addition of a keyboard shortcut to streamline the process of adding items in the top bar of the app. Specifically, I propose that pressing Ctrl+Enter should have the same function as clicking "+ Add as todo." This feature will make it quicker and more efficient for users to add items to their to-do list or other lists.
Use Case:
This feature would be highly beneficial for users who frequently add items to their lists in the app. Instead of reaching for the mouse and clicking the "+ Add as todo" button, users could simply type the item they want to add and then press Ctrl+Enter to instantly add it. This not only saves time but also provides a more fluid and seamless user experience.
Implementation Details:
To implement this feature, the development team can follow these steps:
Add a keyboard event listener to the input field in the top bar.
When the user presses Ctrl+Enter, trigger the same action as clicking the "+ Add as todo" button.
Ensure that this functionality is clearly documented in the app's user guide or keyboard shortcut reference.
Additional Context:
Keyboard shortcuts are a valuable feature for power users and those who prefer a more keyboard-centric approach to using the app. This addition would enhance the overall user experience and make the app more efficient to use. It's a small but meaningful improvement that can have a positive impact on user productivity.
Important Note:
Please consider implementing this feature to improve the app's usability and efficiency. Keyboard shortcuts are a standard feature in many applications and can greatly enhance the user experience.

This is neither a proper feature request. Could you please stick to the template, which is provided?

Updated the original ticket!

@DeflateAwning released as part of 2.0.0.

Hi @ransome1 ,
2 suggestions:

Could this shortcut be added in the "Add a new todo"-field as well? I tried every modifier key + enter, it didn't work. Right now I have to shift-tab, enter, or use the mouse. Am I missing something here?
After entering a new todo via "Find", either (chooseable in settings)

refresh/update the ToDo-list below. Right now it is only refreshed when deleting or adding a character in the find-field, OR
clear search results and go back to the main list - maybe scroll to the new todo and highlight it for a few moments?

Thanks!

Could this shortcut be added in the "Add a new todo"-field as well? I tried every modifier key + enter, it didn't work. Right now I have to shift-tab, enter, or use the mouse. Am I missing something here?

You're right, on Windows and Linux systems this shortcut is missing. I only implemented it in the Mac releases. Here it is CMD & Enter. The respective shortcut for Windows and Linux will be added to the next release.

refresh/update the ToDo-list below. Right now it is only refreshed when deleting or adding a character in the find-field, OR

When you add a new todo using the search textfield, the list will refresh itself. This should already work in almost all previous version, so maybe I need more details here.
The upcoming flow (implemented as part of 2.0.5) is:

enter something in search textfield
This will most likely empty the list
either click the button or use the keyboard shortcut to add it
the previously entered search string will persist in the textfield, as will the focus
the list will reload, but since the search string is still present, you will only see the newly created todo
since the focus is still in the textfield, pressing escape will clear the search textfield and the list will be fully available again

Hello @ransome1 ,
I was gone for the past couple of weeks, thanks for your patience. I just updated to 2.0.10-rc.1 and:

You're right, on Windows and Linux systems this shortcut is missing. I only implemented it in the Mac releases. Here it is CMD & Enter. The respective shortcut for Windows and Linux will be added to the next release.

This is working now, thanks!

When you add a new todo using the search text field, the list will refresh itself. This should already work in almost all previous version, so maybe I need more details here.

There must have been a bug on the version I was using back then. Pressing CTRL-F, typing "test", pressing TAB, SPACE/ENTER left me with an empty list. Only after deleting the last character OR adding any extra character and then deleting it in the find-field, the todo showed below.
It did not happen again when I tested it today, I could not reproduce it. I will report back here if it happens again.
Thanks : )


Token crypto

Learning positive constructive criticism will be a great thing! Thank you! Sorry for Sent from my iPhoneOn Aug 6, 2023, at 1:38 PM, sven @.***> wrote:
:(
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

#221


Color connection

I would like to be able to open a colored editor from particular connections.
I feel stupid, I am pretty sure the feature is there, just properly burried. And apparently not mentioned anywhere within Google's reach. Closest I could find was this. No mention of how to reach that feature...
If the feature is already there, can you please add some lead to it, somewhere in the connection properties pane? (F4, or Alt+Enter...?)

You can have different colours based on Connection Type.
Edit Connection -> General -> Connection type
In there you can change the colour for as many types as you like. You can also use it for its presumably intended purpose, to save you from accidentally executing queries on production databases.

oh thank you very much, kind sir! :)

You can have different colours based on Connection Type.
Edit Connection -> General -> Connection type
In there you can change the colour for as many types as you like. You can also use it for its presumably intended purpose, to save you from accidentally executing queries on production databases.

Thank you so much searching for long time


Can't remove plasteel panel from door wiring

Description
You can't remove the plasteel panel on door wiring because you can't perform the crowbar step.
Reproduction

Get a door with a plasteel panel, open up the panel
Weld it, then try to crowbar it
Get stuck at the crowbar step
Cry

Screenshots

maybe caused by prying refactor

This issur should be closed by #20664

ok