Need to update the provided exemple in readme.md

In the readme.md of apicula:
https://github.com/YosysHQ/apicula/blob/master/readme.md
yosys -D LEDS_NR=8 -p "synth_gowin -json blinky.json" blinky.v
This works fine with yosys 0.12. more recent yosys like 0.14 (since 0.13 ?) need to have the following addition to work:
yosys -D LEDS_NR=8 -p "read_verilog blinky.v; synth_gowin -json blinky.json"
Both syntax depending on version should so be described.

oops, sorry, wrong project.


BCI Java: Java time module

https://progress.opensuse.org/issues/110689
VR: http://marvin5.arch.suse.cz/tests/716

Also, please put the java sources into a different directory, trainers was added by @m-dati for the python tests

With @m-dati we decided to keep there the files and in the future create a new PR to move the python ones to a directory python inside trainers

Also, please put the java sources into a different directory, trainers was added by @m-dati for the python tests

With @m-dati we decided to keep there the files and in the future create a new PR to move the python ones to a directory python inside trainers

Fair enough, but please pick a different name than trainers. That is not suitable for a various selection of files which have nothing to do with training.

Fair enough, but please pick a different name than trainers. That is not suitable for a various selection of files which have nothing to do with training.

Yes, I agree, but in a different PR to avoid mix things


Fails to update when surrounding DOM causes measured element to move

Have a look at this example and click on the orange field to start the animation.
Maybe I'm misinterpreting the scope of this component but I was expecting that the top property would be continuously updated here

fyi: for now I'm circumventing the issue by creating a wrapper component that calls measure() on a <Measure>-instance every 1000ms. Not ideal but good enough for my use case.
Or are there maybe some DOM-Events out there that might be more helpful in this situation?

Sorry, I could see how that is confusing. React Measure only measures the component when the dimensions have changed by using a Resize Observer. The only thing I can think of for a fix is to wrap the parent in a Measure component, then you will know when the child's position top changes.
@que-etc any idea on how this can be solved better?

The suggested fix only really works if you recursively wrap all parents in a Measure component because theoretically any of these could have an effect on the elements position.
That doesn't sound too feasible. So if there was a native DOM-Event one could listen to would be great!
I'm closing the issue for now because it seems quite out of scope indeed.

Sounds good. Now that I think about it, we might be able to detect that change with a Mutation Observer. I'll try and look into when I get a chance. I'd like to be able to see if any dimensions of a box model change if possible.

I just fell prey to this :sob:
I feel like it's almost more confusing to provide offset when changes to it are not detected. It sets up the expectation that the user does not have to worry about detecting changes anymore.


[DPP] [Release 24.08] Threat Modelling Analysis

Description
The security and threat modeling of the app must be ensured and approved by the security team.

[ ] Contact to the serurity team: @RoKrish14  and @szymonkowalczykzf to align with the security requiremnets

Acceptance Criteria

[ ] Approved by the security team

Just as a statement here:

Nothing changed from the Security Assessment this time compared with the R24.05

So I would consider this as approved, but can always be checked with @RoKrish14 ;)

I and @szymonkowalczykzf Approve 👍


Test 2 NumaflowControllerRollouts with "pause-and-drain" strategy

Summary
Paved Path team is adding the functionality for 2 (or potentially more) NumaflowControllerRollouts.
Their plan is for each Pipeline/MonoVertex to have the capability to update the version of Numaflow that it's on (if there's a new version, they will add another NumaflowControllerRollout).
Since "progressive" strategy isn't ready yet, it would be great if the code they're building can be used with "pause and drain" and I believe it should be. But this needs to be verified through testing.
Say there's:
controller 0
controller 1
ISBServiceRollout on controller 0
PipelineRollout on controller 0
MVXRollout on controller 0
Say they update all 3 Rollouts to Controller Instance Annotation 1.
I believe ResourceNeedsUpdating() function should determine PPND/Progressive for all 3 Rollouts. For Pipeline and isbsvc, this means it should do the PPND strategy. For MonoVertex, it should do standard direct apply since there's no PPND strategy.
Since ISBServiceRollout reconciler will request that its Pipelines pause, and also the Pipeline will want to pause on its own, it will pause (drain) and then both the isbsvc and pipeline should be updated and the Pipeline should go back to "Running".
Please confirm that all of what I've written above in fact happens and if not, let me know.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

@dpadhiar whenever you're done with the artifact improvements, could I bother you to try this out?

cc @Krithika3 @mshakira

Thinking through what will happen as far as the reconciliation within Numaflow, there is this line which I believe marks a Pipeline Failed if the isbsvc it's using is on the other Numaflow Controller.
Let's say the front end updates both ISBServiceRollout and PipelineRollout in the same PR, which I believe they would.
Whether the iSBServiceRollout change is reconciled first or the PipelineRollout change is reconciled first is non-deterministic. Therefore, the Pipeline could momentarily enter a "Failed" state while they're mismatched.

Unfortunately, it looks like Derek, Vigith, and the front end team have dropped the idea of having 2 Numaflow Controller Rollouts in favor of making things simple for the front end team. So, we won't be doing this after all.


Print evolved stats

Expected Behavior
Print evolved stats after evolving a pokemon.
Actual Behavior
Simply states it was evolved.
Steps to Reproduce
Set to evolve pokemon after capture.
Related to this, I would love to see all current items when we capture more of them, current EXP after EXP change, EXP gain from captures (including separate bonuses), current candies when transferring or after hatch (and add totals behind hatch info). Hatch count after hatch and distance to hatch. Distance walked to fort distance and distance travelled since last "moving towards fort..." line.

+1
I like to see some more feedback for distance, XP, eggs etc. also. not just after the script closes.
Maybe log all Pokémon with IV values, just like the "Captured !" message.


NetConstants configurable at runtime

It would be nice if NetConstants could be modified at runtime, that way you do not have to modify source code to tweak settings. It would make updating to newer versions easier with less risk of forgetting to change something.

@emrys90 most constants is really constants. Also this is critical for performance

Alright. The only reason I wanted it was to increase DefaultWindowScale to 128. I believe this feature request would cover that anyways though which would make this one not needed.
https://github.com/RevenantX/LiteNetLib/issues/110


one splash screen per ssid / per zone not safe for work

There are two ways how to set up a network with an active splash screen in ct cloud.
->The first way leads to create a new network with a captive-portal. Doing this will create a new splash screen which is assigned but is called "no name" (can be configured later)
->The second way is more tricky, you build a splash screen first with a sophisticated  configuration which needs to be assigned to an already existing or recently created ssid. Working this way, you will have to use the splash screens - network option which is bit hidden and has no check how many Splashscreens are already assigned to this one and only SSID.

so i managed to get two splashscreens active for one ssid. in fact only one became active but there is no warning or correct display in ct cloud

What do you mean 'safe for work?'

should just say that this "rule" is not stable with the described way to break it.

Can we be clear what you're actually expecting here, I don't understand.

for my understanding each network/ssid or even a zone can not  have more than 1 splash screen/captive page. this works for way 1 but on way 2 there are no limitations

Ok, got it. I will check the validation...

We're not going to fix this since we're shortly introducing multiple splash pages per SSID / network.


exporting schema

as I went through the docs I couldnt find exporting schema owl by API. if possible to add this feature it would be grate.
or maybe if it's exist and I didn't find it guid me please.
tqs

Get  https://<IP_ADDRESS>:6363/api/triples/admin/banker/local/branch/main/schema/main


.Net: Report function call failure in IFunctionFilter

IFunctionFilter.OnFunctionInvoked() allows us to be notified when the LLM has used a function successfully, but to my knowledge there is no way of knowing when the LLM has called a function that has failed (when an exception has been raised by the function, for example).
The solution would be that, in the event of an error, IFunctionFilter.OnFunctionInvoked() is also called, and provides the error message, or that another OnFunctionFailed() method is added to IFunctionFilter.

@Nurgo Thanks for reporting this issue! At the moment, as soon as you do kernel.InvokeAsync(function) and that function throws an error, you will be able to receive an error in place where you invoked a function, handle it with try/catch block and observe error message. Here is test example:

At the moment, IFunctionFilter.OnFunctionInvoked() is invoked only in case of successful function execution to observe the results, number of tokens used etc. Instead of handling exception in filters, it's possible to handle it with try/catch, which should be more native way for .NET.
Please let me know if that makes sense. You could also provide specific scenario where you think exception details in filters will be useful, so we can see how to improve it. Thank you!

We may need to have an ability for a developer to have a more local "try/catch" for a function failure (for example, you may want to catch an error within a planner instead of putting a try/catch around the entire plan invocation). This will likely require new events.
To complexify things, according to @alliscode, the planners already have some logic to handle failures that would need to rationalize with.
@dmytrostruk, please sync with @gitri-ms in case this impacts the work she's doing with the new function calling filters.

@dmytrostruk Thank you for your example. The problem with this approach is that if the KernelFuction is not called explicitly, but by the LLM during a call to IChatCompletionService.GetChatMessageContentAsync(), it is not possible to know whether the exception was raised by a KernelFunction. It is therefore not possible to know the plugin and the function names in order to display a useful error message.
The IFunctionFilter will often be used to show the user when the chatbot is calling a function, so it would make sense to also be notified of errors, and not just successful function calls, as when a chatbot fails to use a plugin it's useful to inform the user.

When the exception is raised by a KernelFunction that has been called automatically by the LLM, during a call to IChatCompletionService.GetChatMessageContentAsync(), no exception is propagated, and the ChatMessageContent returned indicates that no function has been called, which is therefore incorrect.
As far as I know, there's no way of handling exceptions raised by KernelFunctions in this case.
IFunctionFilter seems to me a good place to handle errors in function calls, and should allow either to handle the exception locally and block its propagation, or to let it propagate to GetChatMessageContentAsync().
What do you think?

@Nurgo Yes, I think that makes sense in case when function is called automatically by the LLM. Function filter should be a good place for it. Another option would be to add this feature to the new type of filters - tool filters. (PR: https://github.com/microsoft/semantic-kernel/pull/4922). These are the filters for functions that are called by LLM, we should check if it can cover this scenario.


ARTEMIS-311 - added broker name to jmx object name properties.

Its now possible to also add the broker name to jmx tree avoiding clashes when multiple brokers are in a single vm. This is now the default but the old way can be used with some configuration
https://issues.apache.org/jira/browse/ARTEMIS-311

@clebertsuconic ive updated it to use host as requested


MapView to support MKPointAnnotation using new attribute annotate in Map...

MapView to support Pin annotation
var pinLocation1 = {
		latitude: property.latitude,
		longitude: property.longitude,
		title: "I'm here.."
	};
	var pinLocation2 = {
		latitude: property.latitude + 0.1,
		longitude: property.longitude,
		title: "I'm here too!"
	};
this.state = {propertyPoints: [pinLocation1, pinLocation2]};
<MapView style={styles.map} region={this.state.region} annotations={this.state.propertyPoints}>
</MapView>

Please review the changes for supporting annotation inside MapView

Yes correct

Wouldn't it make more sense to provide an array of pins?
Also, we'd really want to be able to remove them. We could do that by maintaining a dictionary of annotations keyed by coordinate internally and when the array is updated we'd remove the ones that are no longer in the array.

libuicore is no longer required. If you wouldn't mind removing it, I'll get this merged.

Running UIExplorer, going into MapView, and tapping on the annotation freezes the app. I've tried this with a blank project with MapView, along with an ordinary annotation; same problem.
Occurs in both simulator, and on device. Inspecting memory usage via Xcode reveals that after annotation is tapped, memory usage keeps on rising, and CPU suddenly jumps to ~180%, and stays around there.

That's weird … I'm seeing this on iOS 8.1 simulator, but not pn iOS 8.3

OK, I've found the problem. I'm landing a fix ASAP, but in the meantime if it's blocking you, you can fix it by replacing the layoutSubviews method in RCTMap.m with
- (void)reactSetFrame:(CGRect)frame
{
  self.frame = frame;
}

- (void)layoutSubviews
{
  [super layoutSubviews];

  if (_legalLabel) {
    dispatch_async(dispatch_get_main_queue(), ^{
      CGRect frame = _legalLabel.frame;
      if (_legalLabelInsets.left) {
        frame.origin.x = _legalLabelInsets.left;
      } else if (_legalLabelInsets.right) {
        frame.origin.x = self.frame.size.width - _legalLabelInsets.right - frame.size.width;
      }
      if (_legalLabelInsets.top) {
        frame.origin.y = _legalLabelInsets.top;
      } else if (_legalLabelInsets.bottom) {
        frame.origin.y = self.frame.size.height - _legalLabelInsets.bottom - frame.size.height;
      }
      _legalLabel.frame = frame;
    });
  }
}

Why shouldn't the annotation be a node?
At least provide a way to customize the annotation, replace the default drop pin on iOS, leverage the appearance between iOS and Android.


refactor(definition-table): use data loader internally

To Reviewers

[ ] Skipping review is not a problem (style, chore ONLY)
[ ] Not that difficult

Type of Change

[ ] New feature
[ ] Bug fixes
[ ] Feature improvement

[ ] These changes require a usage change

[x] Others (performance improvement, refactoring, CI/CD, etc.)

Checklist

[x] Updated Storybook documents
[x] Tested with console

Description

SSIA!
docs(button-modal): do not use low dash in variable name

Things to Talk About

:tada: This PR is included in version 1.1.0-beta.415 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Not working

Sorry, but it is not working for me. No scroll at all. Latest version of Atom. I disabled all other markdown-related plugins except for the core markdown-preview.

I found the problem: I had to enable the language-gfm core plugin, otherwise it won't work.

Note for reproducing the bug: enabling the plugin language-gfm solves the problem immediately, but disabling it requires a restart of the IDE to make the problem manifest itself.

If you could make your plugin independent of the language-gfm plugin it would cause less frustration for other users that may stumble into this. If you thing it's not worth the trouble, I suggest that, at least, you could warn the user about this requirement on the Readme.

Why did you have it disabled?  Aren't core packages always supposed to be
enabled?
On Thu, Dec 17, 2015 at 7:23 AM, Cláudio Silva<EMAIL_ADDRESS>wrote:

I found the problem: I had to enable the language-gfm core plugin,
otherwise it won't work.
Note for reproducing the bug: enabling the plugin language-gfm solves the
problem immediately, but disabling it requires a restart of the IDE to make
the problem manifest itself.
If you could make your plugin independent of the language-gfm plugin it
would cause less frustration for other users that may stumble into this. If
you thing it's not worth the trouble, I suggest that, at least, you could
warn the user about this requirement on the Readme.
—
Reply to this email directly or view it on GitHub
https://github.com/mark-hahn/markdown-scroll-sync/issues/37#issuecomment-165482297
.

Well, one might not want the Github Markup Format functionality, or it may interfere with some plugin.
Also, sometimes you may need to disable a core package in order to replace it with another package (just one example: the Markdown Preview).

So language-gfm is for Github Markdown Format?  What format were you using?
markdown-scroll-sync has only been tested with the normal gihub markdown
preview.

Note: I disabled the package because I disabled all packages related to Markdown in order to find out which package was causing problems with the Markdown Preview (a problem that is not related to you, in any way). That's when your package stopped working, even after being re-enabled. Then, I just forgot to reenable language-gfm because it doesn't show up when one searches for 'markdown'.
Look, I didn't mean to bother you with this and I know you are a busy person. It's just that I spent a lot of time trying to make your package work again, and I was about to give up when I found out the culprit.
So I decided to let you know about this, in the hope that, at least, you could put a warning about it on the Readme, so that we could spare other users from, eventually (yes, I know it may be rare, but it happens!), going trough the same that I did.
Best regards, and thank you for this excelent package.

you could put a warning about it on the Readme,

Since you understand the problem can you put in a pull request with a
subtle warning?  It would really help.
I'm sorry I haven't thanked you for the work you've done.  I've been buried
in a ton of work.
On Fri, Dec 18, 2015 at 2:24 AM, Cláudio Silva<EMAIL_ADDRESS>wrote:

Note: I disabled the package because I disabled all packages related to
Markdown in order to find out which package was causing problems with the
Markdown Preview (a problem that is not related to you, in any way). That's
when your package stopped working, even after being re-enabled. Then, I
just forgot to reenable language-gfm because it doesn't show up when one
searches for 'markdown'.
Look, I didn't mean to bother you with this and I know you are a busy
person. It's just that I spent a lot of time trying to make your package
work again, and I was about to give up when I found out the culprit.
So I decided to let you know about this, in the hope that, at least, you
could put a warning about it on the Readme, so that we could spare other
users from, eventually (yes, I know it may be rare, but it happens!), going
trough the same that I did.
Best regards, and thank you for this excelent package.
—
Reply to this email directly or view it on GitHub
https://github.com/mark-hahn/markdown-scroll-sync/issues/37#issuecomment-165740893
.

> markdown-scroll-sync has only been tested with the normal gihub markdown preview.

Note that Github Flavoured Markdown (GFM) != 'normal markdown'.
GFM adds tables and syntax highlighting for code to the standard markdown core.
I don't see that there's any reason for markdown edit/preview synchronisation to depend on the formatting dialect? If this reliance exists, I'd suggest it's definitely a bug.

I don't see that there's any reason for markdown edit/preview
synchronisation to depend on the formatting dialect?

I check to make sure it is an md doc.  It should work otherwise.  What
grammar do your documents show?
On Thu, Feb 4, 2016 at 11:22 AM, Ollie Ford<EMAIL_ADDRESS>wrote:

markdown-scroll-sync has only been tested with the normal gihub markdown preview.

Note that Github Flavoured Markdown (GFM) != 'normal markdown'.
GFM adds tables and syntax highlighting for code to the standard markdown
core.
I don't see that there's any reason for markdown edit/preview
synchronisation to depend on the formatting dialect? If this reliance
exists, I'd suggest it's definitely a bug.
—
Reply to this email directly or view it on GitHub
https://github.com/mark-hahn/markdown-scroll-sync/issues/37#issuecomment-180011192
.

I check to make sure it is an md doc.

Ah, I see.
Well, without GFM there is no syntax-highlighting to be done; no language- package. I see your check for whether the name is one of [GFM, CS], but I'm not sure how to check what it is with language-gfm disabled? Could you just check for a .md file extension?
Also, there are currently 3  similarly titled issues.. Can I suggest re-titling this one along the lines of "not working with GFM disabled"? :)

Could you just check for a .md file extension?

I might be doing that.  I don't remember.  I'm buried right now and it
could speed things up if you looked at the code.  You don't need to change
anything and do a PR.  Just saving my time would help.
On Thu, Feb 4, 2016 at 12:50 PM, Ollie Ford<EMAIL_ADDRESS>wrote:

I check to make sure it is an md doc.
Ah, I see.
Well, without GFM there is no syntax-highlighting to be done; no language-
package. Without another language package installed, it auto-detects
plain-text, but markdown-preview still detects and renders the markdown
formatting. Could you just check for a .md file extension?
Also, there are currently 3 similarly titled issues.. Can I suggest
re-titling this one along the lines of "not working with GFM disabled"? :)
—
Reply to this email directly or view it on GitHub
https://github.com/mark-hahn/markdown-scroll-sync/issues/37#issuecomment-180041394
.

I did take a look, I'm afraid I couldn't give you a PR if I tried though - still new to Atom and CoffeeScript.

Could you just check for a .md file extension?
I might be doing that

Right now you're checking the name of the grammar in the editor (as auto-detected, or whatever)
https://github.com/mark-hahn/markdown-scroll-sync/blob/master/lib/main.coffee#L26-L29
isMarkdown = (editor)->
        for name in ["GitHub Markdown", "CoffeeScript (Literate)"]
          return true if editor.getGrammar().name is name
        return false

I suppose my suggestion would be to replace return false with return fileExtensionIsMD. I might have a crack at it later, but as I say I'm new to it all, and really don't know what that might look like.

Just wanted to thank Mr. Hahn and contributors for identifying the extension dependency. I had no qualms with mass-renaming my .txt files to .md (thus having atom identify the syntax as GFM), and that solved it for now.
Thank you so much for sharing this, not having Marked 2 on my Windows-PC was killing me, this is a solid replacement.

@funkinezz If you'd rather not rename to .md, you can set the format manually, overriding auto detection - or indeed set markdown to be the language used for .txts

You can also hack my code to remove the check.
On Fri, Feb 5, 2016 at 8:22 AM, Ollie Ford<EMAIL_ADDRESS>wrote:

@funkinezz https://github.com/funkinezz If you'd rather not rename to
.md, you can set the format manually, overriding auto detection - or indeed
set markdown to be the language used for .txts
—
Reply to this email directly or view it on GitHub
https://github.com/mark-hahn/markdown-scroll-sync/issues/37#issuecomment-180427568
.


[WIP] feat(react): add LeftNavigation component

Purpose
Add LeftNavigation and LeftNavigationItem components.
Related Issues

https://github.com/wso2/oxygen-ui/issues/2

Related PRs

None

Checklist

[ ] UX/UI review done on the final implementation.
[ ] Story provided. (Add screenshots)
[x] Manual test round performed and verified.
[ ] Unit tests provided. (Add links if there are any)
[ ] Documentation provided. (Add links if there are any)

Security checks

[ ] Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
[ ] Ran FindSecurityBugs plugin and verified report?
[ ] Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

Integrated with https://github.com/wso2/oxygen-ui/pull/28


Added access rule processor implementation in istio when feature togg…

…le enabled

Description
Changes proposed in this pull request:

Access rules will be deleted when switching on feature toggle
...
...

Related issue(s)

Resolves #41

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

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

/test all


php.extensions.pdo_mysql: Set default socket location

Motivation for this change
Set the default socket location to match the one used by the MySQL module, so PHP programs using pdo_mysql don't have to specify this themselves. This used to work before  #83896 was merged, since the module automatically picked up the value set by --with-mysql-sock= at compile time - this parameter is not available for pdo_mysql, though, so we'll have to set the variable directly instead.
This fixes the issues experienced in #84952, where the default config only specifies localhost for the MySQL host address.

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@talyz Thanks! :)


Releasing python packages as opentelemetry SQLCommenter

Renamed python packages from google cloud to opentelemetry SQLCommenter
Setup workflows which will publish the python package to testpypy and pypy

@aabmass @lonewolf3739 We need to add PYPI_API_TOKEN and TEST_PYPI_API_TOKEN to this repository to create a release from here. I am not aware of the process to get these tokens for opentelemetry account. Can you guys help here ?

I still believe these packages are better merged to their corresponding instrumentations in opentelemetry-contrib-{js/py/rb/java}. If they are released as standalone packages sometimes they might even conflict with instrumentations (ex: both sqlcommenter and sqlalchemy-instrumentation use before_execute hook) or double patching may lead to strange issues. What do you think?
If we decide to continue releasing these packages we need to get the tokens shared from the opentelemetry-python maitainers team (I can request). I think they have something like 1password to share across the org maintainers.

I still believe these packages are better merged to their corresponding instrumentations in opentelemetry-contrib-{js/py/rb/java}. If they are released as standalone packages sometimes they might even conflict with instrumentations (ex: both sqlcommenter and sqlalchemy-instrumentation use before_execute hook) or double patching may lead to strange issues. What do you think?
If we decide to continue releasing these packages we need to get the tokens shared from the opentelemetry-python maitainers team (I can request). I think they have something like 1password to share across the org maintainers.

@lonewolf3739 I agree to the point that merging the changes to opentelemetry-contrib-* is the better way to do. But there are few tradeoffs and challenges we have to accept in that case:

SQLCommenter would loose the ability to be installed in a standalone way.
How much time it will take for opentelemetry-{py | js | ruby | java} maintainers to accept the merging into contrib repositories. At present we could not deprecate the google-cloud-sqlcommenter repository as there has been no release from here. Maintaining 2 repositories is getting difficult.

I was thinking can we do something like integrate opentelemetry-sqlcommenter library into opentelemetry-contrib-*.  Like would it be feasible to call opentelemetry-sqlcommenter-python library methods from opentelemetry-contrib-python if some flag is enabled like use_sqlcommenter=<true|false> in open telemetry ?

How much time it will take for opentelemetry-{py | js | ruby | java} maintainers to accept the merging into contrib repositories

Reviews happen reasonably quickly and packages get released at least once a month.

would it be feasible to call opentelemetry-sqlcommenter-python library methods from opentelemetry-contrib-python if some flag is enabled like use_sqlcommenter=<true|false> in open telemetry

Not sure I understand this completely, if the intent is to make instrumentations take dependency on opentelemetry-sqlcommenter-python, then it is techinically possible. That is similar to what we do with this. But maybe it would be easier to just update the instrumentation directly.

Reviews happen reasonably quickly and packages get released at least once a month.

I am not sure if the review is only needed by otel-python-maintainers. I had the impression that it requires a discussion with otel-specs SIG first for accepting the proposal to merge code into contrib repositories.

Not sure I understand this completely, if the intent is to make instrumentations take dependency on opentelemetry-sqlcommenter-python, then it is techinically possible. That is similar to what we do with this. But maybe it would be easier to just update the instrumentation directly.

Thank you, that was what i was asking. Like if there are no major cons, we could make the library work with/without opentelemetry. Any thoughts on this ?
google-cloud-sqlcommenter-python has been an actively downloaded library from pypi. I was thinking if we can atleast do a release from here, we will go ahead and deprecate the code from google repository. In parallel we can start a discussion about merging the instrumentations into contrib repositories. If it is fine can you request keys from otel-python maintainers team ?

I had the impression that it requires a discussion with otel-specs SIG first for accepting the proposal to merge code into contrib repositories.

didn't know that is the process.

we could make the library work with/without opentelemetry.

This is where I am conflicted. There is a decent info commenter adds to query other than trace context provided OTEL but trace context can be really useful to lookup and drill down to find the issues. Considering open-telemetry org is the new home for these packages I would expect the first class support for OTEL related stuff.

we will go ahead and deprecate the code from google repository. In parallel we can start a discussion about merging the instrumentations into contrib repositories

This sounds good to me. I will bring up the tokens matter with python maintainers team today.

This is where I am conflicted. There is a decent info commenter adds to query other than trace context provided OTEL but trace context can be really useful to lookup and drill down to find the issues. Considering open-telemetry org is the new home for these packages I would expect the first class support for OTEL related stuff.

trace context do provide very useful information as it is possible to join dots end to end. Example here.
It makes sense that the repo being inside opentelemetry, it should have the first class support.

This sounds good to me. I will bring up the tokens matter with python maintainers team today.

Thank you very much!

@sjs994 I brought up the idea of using the same account as opentelemetry-python/contrib. Only one of the maintainers was there in the meeting so there was no decision made. It would be ideal if you can join the next meeting when all the maintainers are present and we discuss about this. As there are holidays next meeting will be on first week of Jan. Does that sound good for you?

Thanks @lonewolf3739. Sure, will join the next meeting. It was good to have it quickly, but i expected there will be delay due to holidays. In the meantime, should we start a thread with otel-python-maintainers regarding what they think about moving sqlcommenter code into contrib repos ?

We can do that but I don't think there will be any response as most of core team members are on leave starting from next week. We can still go ahead and start the discussion so that it sets some context and gives broader idea before we meet.

We discussed to make this PR into smaller ones. One for package rename and other for release actions.
Release actions would require the tokens for deployment, but package renames, we can review and merge before that.


Improve wording

Based on thread from #6404.

I added 1.1.0, 'cause I think this as well as the previous doc change (#6404) should be cherry-picked there as well.

okay, the wording changes (both of them) were pushed to master and 1.1.0


Some errors from time to time

I got these erros:
Error detected while processing function <SNR>183_RepeatMotion:
line   15:
E1206: Dictionary required for argument 1

Error detected while processing function <SNR>183_RepeatMotion:
line   15:
E1206: Dictionary required for argument 1

I am not sure when.

Thanks for the feedback! I'll analyze the code and search for a solution. Of course it would be nice if you could provide a way to reproduce the problem :-)

I had a look at the code and it would help me to understand the problem if you could share with me your remotions configuration. In particular the way the g:remotions_motions value.

I have push some changes to make the code more robust (or even to correct a bug). I believe it will solve your problem but since I can't reproduce it I can't be sure. I'll let the issue open until you confirm that the new version solves your problem :-)

OK, thanks!  I actually copied your configuration of lazy and used it.

Seems to be working. Thanks!

Thanks for your fast feedback!


feat(extra): add undotree

undo history visualizer for VIM

I suggest telescope-undo.nvim. It might suit better since it's written in Lua and uses telescope.

I suggest telescope-undo.nvim. It might suit better since it's written in Lua and uses telescope.

Yeah I was gonna go for that but this seems to be more popular

Thanks for the PR, I also would like to see this. However, note that the key conflicts with 'Toggle Treesitter Highlight'.

Thanks for the PR, I also would like to see this. However, note that the key conflicts with 'Toggle Treesitter Highlight'.

thanks will remap to something else

Thanks, that looks free indeed. Sorry but I just noticed.. I would recommend the following change (or similar) to avoid cluttering the home directory:
local undodir = vim.fn.stdpath("data") .. "/undotree" -- or /undodir

Thanks, that looks free indeed. Sorry but I just noticed.. I would recommend the following change (or similar) to avoid cluttering the home directory:
local undodir = vim.fn.stdpath("data") .. "/undotree" -- or /undodir

(personal preference)
EDIT: My reasoning for the specific dir (~/.local/share/nvim/) is because other plugins use it for similar purposes (neo-tree logs, mason, project history, telescope history).
EDIT 2: The default undodir is ~/.local/state (stdpath('state')).
See :h stdpath():
		state        String  Session state directory: storage for file
				     drafts, swap, undo, |shada|.

And :h undodir:
'undodir' 'udir'	string	(default "$XDG_STATE_HOME/nvim/undo//")

Maybe this is a better dir, unless it conflicts with the default undo files.
EDIT 3: I think the whole part can simply go away:
      local undodir = vim.fn.expand("~/.undo-nvim")

      if vim.fn.has("persistent_undo") == 1 then
        if vim.fn.isdirectory(undodir) == 0 then
          os.execute("mkdir -p " .. undodir)
        end

        vim.opt.undodir = undodir
        vim.opt.undofile = true
      end

undodir already has a default from nvim and undofile is enabled in LazyVim
https://github.com/LazyVim/LazyVim/blob/ae381c91a1ec420cce082443501bace1ac7aaa3f/lua/lazyvim/config/options.lua#L85

yeah that makes sense to use whats already set on options


Update country flag images: Martinique (PNG and SVG files)

This PR updates the Martinique flag to resolve issue #44.
•	The flag has been redrawn and optimized.
•	SVG and PNG versions are updated.
•	The flag is vertically centered and rounded, aligning with other Twemoji flags.
•	SVG overlap are optimized for deficiencies of SVG renderers.

This ensures visual consistency across the emoji set.
Related PR: https://github.com/twitter/twemoji/pull/1116
Source:
Wikipedia: Flag of Martinique
Martinique article: Wikipedia

Hi @jdecked,
I wanted to kindly check if you had a chance to review my pull request. Please let me know if there’s anything I can adjust or improve. I’m happy to make any changes if needed.
Thank you for your time and consideration!
Thierry


Windows CI performance improvements

Under our current setup, Windows builds can really slow down CI jobs, but there are a few tasks that could speed them up:

[ ] Add one more Windows node to Jenkins that can perform Windows CI
[ ] Use the D:\ drive for all CI jobs on the Windows CI systems. The D:\ drive is the default temp drive on Windows Azure systems, and has significantly faster performance: https://blogs.msdn.microsoft.com/mast/2013/12/06/understanding-the-temporary-drive-on-windows-azure-virtual-machines/

I think this is really high priority because our CI runs are taking an entire hour per job right now, which is bad.

@andschwa @ionutbalutoiu Yes I agree, this should be one of the highest priority tasks in right now in https://github.com/Microsoft/openenclave/projects/4


Failed to load the background-matrix package

[Enter steps to reproduce below:]

...
...

Atom Version: 1.0.19
System: Mac OS X 10.9.5
Thrown From: Atom Core
Stack Trace
Failed to load the background-matrix package
At Cannot read property 'prototype' of undefined

TypeError: Cannot read property 'prototype' of undefined
    at __extends (<anonymous>:1:1)
    at <anonymous>:7:3
    at Object.<anonymous> (<anonymous>:7:3)
    at Object.<anonymous> (<anonymous>:1:1)
    at Module._compile (module.js:428:26)
    at Object.defineProperty.value [as .coffee] (/Users/edzye101/Desktop/Atom.app/Contents/Resources/app.asar/src/compile-cache.js:169:21)
    at Module.load (module.js:353:32)
    at Function.Module._load (module.js:308:12)
    at Module.require (module.js:363:17)
    at require (module.js:382:17)

Commands

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "showIndentGuide": true,
    "invisibles": {}
  }
}

Installed Packages
# User
atom-jshint, v2.0.0
auto-indent, v0.5.0
background-matrix, v0.0.2
jshint, v1.8.1
language-lua, v0.9.4

# Dev
No dev packages

The background-matrix package appears to have been unpublished.  Please remove it from your packages list.

Ok thanks


Hm, release-notes script fails to find the 3.7.0 milestone (claims it's not closed, while it is). I'll do this one manually.


Trying to follow does nothing

For the past couple of days I noticed something weird - whenever I try to follow someone I get a normal JSON response, except neither the outgoing request is created nor following is added - it's like the action is completely ignored by IG. Anyone else had this issue recently?

Yes. Looks like ut's new IG filter mechanism. Can't say for sure how to deal with it.

Yes

@IvanMMM this doesn't happen to all accounts though. Can it somehow be related to the changed payload for likes? Maybe the follow action needs to specify the source too now?

Maybe the new IG v.<IP_ADDRESS>.201 and new key signature with updated requests resolve that @IvanMMM ?

@ibrunotome, I'm pretty sure it will.  Yet, we can't say for sure until we check it :)

Привет. Не появилось версий по данной проблеме?


liquibaseCatalogName not include in generated SQL

Liquibase Snowflake version : 4.4.3
Database Vendor & Version: snowflake
Description
The calalog name is not include in generated sql orders for liquibase objects (with snowflake database)
For snowflake, catalogName represents database name
So if the databasechangelog tables are not in the same database with another schema name, Liquibase returns that the schema does not exists
Steps To Reproduce
Set liquibaseCatalogName and liquibaseSchemaName in properties file :
liquibaseCatalogName: MY_DB
liquibaseSchemaName: MY_SCHEMA
Run liquibase updateSQL
Actual Behavior
generateed SQL orders :
CREATE TABLE MY_SCHEMA.DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP_NTZ, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID));
Expected/Desired Behavior
generated SQL order should be
CREATE TABLE MY_DB.MY_SCHEMA.DATABASECHANGELOGLOCK (ID INT NOT NULL, LOCKED BOOLEAN NOT NULL, LOCKGRANTED TIMESTAMP_NTZ, LOCKEDBY VARCHAR(255), CONSTRAINT PK_DATABASECHANGELOGLOCK PRIMARY KEY (ID));
┆Issue is synchronized with this Jira Bug by Unito

Moving this to liquibase/liquibase now that the snowflake support has moved there

Still an issue for liquibase 4.16.1

@nvoxland By any chance, is there an ETA for this bugfix? My Snowflake organization scheme keeps the DATABASECHANGELOG tables in one catalog, but I wish to create objects in many other catalogs. It is annoying to embed raw sql in my changelogs instead of using the createTable change type.

Hi Team, any update? The issue is still there in V  4.20.0

When I provided all 4 values ( db, schema, warehouse, and role) in the URL, it worked. If the value for the role is not provided, then Liquibase throws a generic error
"Caused by: liquibase.exception.DatabaseException: liquibase.exception.DatabaseException: Error executing SQL SELECT COUNT(*) FROM DATABASECHANGELOGLOCK: Cannot perform SELECT. This session does not have a current database. Call 'USE DATABASE', or use a qualified name."
So, this issue is resolved for me as of now ( I am not worried about the wrong error message :)

Thanks for the input! @Erik-vdg this is still on the queue to fix, if what @ashitabh says is true, then the issue has been fixed without us noticing it. @Erik-vdg Can you try to reproduce it in your environment? Thanks!

We're currently blocked by this, too.
The problem seems to be with SnowflakeDatabase incorrectly reporting Snowflake's capabilities:
    @Override
    public boolean supportsCatalogInObjectName(Class<? extends DatabaseObject> type) {
        return false;
    }

Snowflake does in fact support catalog names in table definitions. I've added a patched SnowflakeDatabase in my project, and returning true for Tables works here.
I'll see if I can raise a PR fixing this tomorrow.

Thats great! Thanks


e2e: add gce/ and TestNoPanicWithWrongPVProvisioner

Depends on #347 , #348

ref: #342, https://github.com/coreos/etcd-operator/pull/344#issuecomment-258621105

@etcd-bot retest this please

closing this in favor of #356


Add descriptions for workflows and actions

This pull request adds detailed descriptions for the workflows and actions in the "Workflows_Actions_Descriptions.md" file. The provided descriptions help to better understand the different workflows and actions used in the project.

Replaced by a PR on develop


Check on async compatibility

In getting pages

Since Requests is blocking, I'm going to investigate how it behaves in Responder, which uses async stuff. I might have to switch to aiohttp, but I'm not sure how that works outside of the event loop. Do I just put async in front over everything. Lets see!

I was able to get this to work. Key takeaway: don't block the main thread! Move things to a background task and have the client request the data, or establish a Websocket connection to communicate.
It's still worth it to write utilities for gathering many large pages of a collection in parallel though, and even do special handling in the subscribers endpoint
import responder
from drip import Client

api = responder.API()
drip_api = Client(API_TOKEN, ACCOUNT_ID)

@api.background.task
def bak():
    print('starting')
    print(len(drip_api.subscribers()))

@api.route('/')
async def index(req, resp):
    bak()
    resp.media = 'processing'

api.run(debug=True, port=8000)

Hitting that route from two different tabs at the same time results in:
starting
INFO: ('<IP_ADDRESS>', 65160) - "GET / HTTP/1.1" 200
starting
INFO: ('<IP_ADDRESS>', 65160) - "GET / HTTP/1.1" 200
1231
1231


example for configuring dockerhub with credentials

on the project checks.. commits have to be signed (suggest using git commit -s --amend)  and there seems to be some whitespace that needs to be removed..


Enable own start/end adornments for DatePicker

https://github.com/dohomi/react-hook-form-mui/blob/d8cefc9cbef0f19178059039c15e6d19d95d203b/packages/rhf-mui/src/DatePickerElement.tsx#L83
I need to specify startAdornment with keeping calendar endAdornment. In rednerInput params, there is already endAdornment defined.
I need to make this to work. Generally, It would be nice to have some option to customize renderInput params. Thanks
renderInput={(props) => {
                        const inputProps = {
                            ...props.InputProps,
                            startAdornment: showLearningNode ? (
                                <SomeAdornment />
                            ) : null,
                        };
                        return (
                            <TextField
                                InputProps={inputProps}
                            />
                        );
                    }}

fixed in v6


Report user location to server

Closes #118

There are some FIXMEs left in the code that we weren't able to fix, so if anyone knows anything that could help, feel free to point us in the right direction :)
@chrisma One of these comments is about cleaning a global Hash every once in a while. In JS, we would use setInterval, we didn't find anything similar except for infinite sleep-loops or really heavyweight libraries like whenever or resque-scheduler. Do you (or anyone else reading this) know any practical approaches to this problem?

@chrisma One of these comments is about cleaning a global Hash every once in a while. In JS, we would use setInterval, we didn't find anything similar except for infinite sleep-loops or really heavyweight libraries like whenever or resque-scheduler. Do you (or anyone else reading this) know any practical approaches to this problem?

I don't think I really understand why the data is held in this global hash in the first place. Regardless, my intuitive approach for limiting the amount of cached data (which is what I assume is the goal?) would be to record only X tuples for each user, and to overwrite the oldest entry once X is reached.
If the data is only required on the client side, localStorage could also be an option

We already only save only one tuple per user, no location history is kept (at least for this sprint :D). We don't want to persist the location data in the database, because we a) don't need it anymore after like 5 mins and b) don't want to keep it for privacy reasons. Cleaning on login/logout seems like a good idea!
I don't know exactly how performant the concurrent data structures we picked here are, but in case of a bad implementation of just having a mutex around the entire Hash (which I think is what it does here?), we would introduce contention between the threads that serve the html pages. That could make it much slower. Of course, we would have to investigate this before actually drawing a conclusion, but I would refrain from writing to the map when loading the page for this reason for now at least

Maybe keeping the one last known position is fine and we don't need to be as strict as we set out to be when first sketching out this feature. We could also provide a DELETE route that the browser requests when the checkbox is disabled again, but would users actually do that instead of just closing the tab?

Good to hear that you have thought about some of the issues.
My thoughts:

you could still keep the current user location info on the client side and then submit it to the server in requests that actually need that information. Then the server would not need to store the info at all (and no special data structures would be needed).
You could alternatively also try to play with the beforeunload event, that is called before a page is closed

I think we will postpone UI for deleting you position and other additional features so that the issues that are waiting on this PR can be worked on. There are some TODOs left that we would also handle in this follow up, but please feel free to share thoughts if you know something about anything there, reviewers :^)

From looking at CI and a local run of git bisect it appears that 0b5b14f breaks some javascript tests, we can't really figure out why. @JulianEgbert @Finn-HPI you set the tests up at some point, right? Do you have any clue what could cause the failures?
My only guess right now is that the document.querySelector is too slow and things are not added to the DOM in time, but I also tested with increased arguments to wait: and that didn't fix anything. Note: we should document that you have to have chrome installed to run the tests somewhere :D

Does document.querySelector('meta[name="csrf-token"]').getAttribute("content"); even work in leafletMap.js? This file should just be a helper file that doesn't know anything about the page or document, etc.

Using your own location for a routing request is currenty failing here as well

Just need to write this down: I was playing around with the test setup on my machine, moving selenium setup around, trying to register a driver myself, but not installing anything or so (except, I believe one gem we have will silently update webdrivers?) and now the tests pass considerably more often. I don't know why, I don't know what I changed. Still though, the tests are not passing 100% of the time, sometimes one fails seemingly at random, but most of the time all pass. Before my computer decided to make the tests pass, I also noticed that the success rate increases when commenting out the line
const CSRF_TOKEN = document.querySelector('meta[name="csrf-token"]').getAttribute("content");

which matches our finding that the commit introducing this line is the first to break the tests. This is so weird, could be some kind of data race or something similarly nasty and unpredictable...

I investigated the behavior with different vm settings, each time running the building_map_spec tests 100 times and counting exit codes (see https://unix.stackexchange.com/a/322308/494598). I tried two different system configurations and one additional setup where I added synthetic system load in a second window using stress. Here are the results (0 means tests pass, 1 means at least one failed):
6 cpus, 8192mb ram
    0 46
    1 54
1 cpu, 1024mb ram
    0 76
    1 24
6 cpus, 8192mb ram, with stress --cpu 4 --io 4 --hdd 4
    0 85
    1 15

The failing tests are almost always failing at find(".routing-path", wait: 15) and find(".time-icon", wait: 15) (the same error appears in several different tests). Needless to say, but those are terrible results in all three setups. The fact that the one with no additional load but more cpu cores fails considerably more often may hint at a concurrency problem, but again, I wouldn't know what and it may all be noise in the measurement. :shrug:

On my machine, I had 100/100 tests pass when using the setup from 5f835f9, but in CI they don't work at all (with both firefox and chrome).

@christian-helms @laugengebaeck We reapplied our changes on the current dev branch and force pushed these commits here (the old commits are saved in the other branch feature/tobias_118_pls_ignore_just_a_backup). Please work in your feature again, the PR branch is yours :)

\o/

I added back the tracking switch, which is now in the topbar. Feel free to suggest better locations for the switch :)


Richross O365 REST API URL updates

The domain of the url pointing back to the Office 365 REST API documentation was changed from www.msdn.com to msdn.microsoft.com.  I only found 2 instances of this in the documents referencing the v2 model.

Hi @richross, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

Hey @richross - thanks very much for your contribution.
Adding @dstrockis for awareness.


[stable/sumologic-fluentd] add repo archive notice

See #24030

Manually merging as this is a required action and independent of anything being tested.


Navigate through the projects

Hi @sgbaird,
it would be nice to be able to smoothly navigate through projects, now that they are done!
Going back and forth is not  convenient at all:
what about adding "Previous Project" and "Next Project" links to each project page, so that one can navigate easily through them.
Thanks for considering this feature.

Great idea! This was based on a template, so I'm not as familiar with the scheme as I am with my usual webpages. I will look into it though! You're welcome to take a look and implement as well.

In the meantime, I'd suggest the silly workaround of leaving the main page open and then opening projects in a new tab and closing them out.. I've had the same trouble with the navigation. Definitely room for improvement!


QC Lockstep tests: tweak test case generation

This is an attempt to get the QLS tests to get more coverage of the duplicate table feature, and more generally to have more interesting coverage.
In particular, we move several of the boring special cases out of the QLS test and into unit tests. This is for things like operating on closed table handles, or opening non-existent snapshots. These things of course must be covered, but they don't have interesting interactions so they don't need to be covered in complex situations. This lets the limited length of action sequences to be used for more interesting things.
See quickcheck-dynamic#85 for further details on why action sequences are so short.
We also change how actions are generated to have fewer tables, and thus more actions per table. We limit the number of tables at once to 5.
Initial results (from 28c4890faff19eb39cea957113dec395b1f0da84):
      Interleaved actions on table duplicates (270 in total):
      88.1% DupTableActionLog "1 <= n < 2"
       6.3% DupTableActionLog "2 <= n < 4"
       3.3% DupTableActionLog "4 <= n < 8"
       1.9% DupTableActionLog "8 <= n < 16"
       0.4% DupTableActionLog "16 <= n < 32"

and now we get:
      Interleaved actions on table duplicates (125 in total):
      55.2% DupTableActionLog "1 <= n < 2"
      12.8% DupTableActionLog "4 <= n < 8"
      11.2% DupTableActionLog "2 <= n < 4"
      11.2% DupTableActionLog "8 <= n < 16"
       7.2% DupTableActionLog "16 <= n < 32"
       2.4% DupTableActionLog "32 <= n < 64"

So this is considerably improved, with 45% of runs now having non-trivial interleavings rather than 12%. And where previously we had only 2.3% of original tables with interleavings of length 8 or more, we now have over 20%.
One important caveat is that the change in the key and value types mean the tests run longer. Summary of running times from my system:
    propLockstep_ModelIOImpl:           OK (11.15s)
    propLockstep_RealImpl_RealFS_IO:    OK (24.24s)
    propLockstep_RealImpl_MockFS_IO:    OK (77.06s)
    propLockstep_RealImpl_MockFS_IOSim: OK (111.07s)

In the first version of this PR the running times on my machine were:
    propLockstep_ModelIOImpl:           OK (17.80s)
    propLockstep_RealImpl_RealFS_IO:    OK (86.42s)
    propLockstep_RealImpl_MockFS_IO:    OK (251.20s)
    propLockstep_RealImpl_MockFS_IOSim: OK (284.86s)
Test.Database.LSMTree.Normal.StateMachine.DL
    prop_example:                       OK (455.09s)

But with a couple changes they're down to this:
    propLockstep_ModelIOImpl:           OK (11.15s)
    propLockstep_RealImpl_RealFS_IO:    OK (24.24s)
    propLockstep_RealImpl_MockFS_IO:    OK (77.06s)
    propLockstep_RealImpl_MockFS_IOSim: OK (111.07s)

Those changes are:

Use SerialisedBlob rather than LargeRawBytes for the Blob type.
Disable the StateMachine.DL.prop_example test

In particular, the latter was not justifying its long running time with any crucial coverage.

Oh and so hopefully this will mean we do not need to adjust the CI testsuite timeouts. :crossed_fingers:


Troubles applying GAN for anomaly detection

Hi Mr Houssam Zenati,
My name is Norbert and I was amazed with the opportunities of your code. I was trying to use it in a real image dataset to classify inbetween one class of image and a diferent one (one good image and the rest, like "cat" and "no cat"). But I was unable to understand your readme instructions completely. Could you provide and easy example with a real dataset? I've lost a bunch of hours to figure out how to run your code, because I could not completely comprehend it.
If you have little time, also a chat or videochat would be a possibilty,
Thank you very much and I am here for any question or suggestion,
Norbert.

Hi Norbert,
Do send me an email with more details about the versions of TF and Python you use, as well as the specifics details of the problems you are facing.
Thank you for your interest in my research project,
Best,
Houssam

I am just getting started with this.  Running into this error.
[13:10:42 ERROR @AnomalyDetection] cannot import name 'do_roc'
Traceback (most recent call last):
File "C:/Users/t842211/Documents/Python/GAN/Efficient-GAN-Anomaly-Detection-master/main.py", line 40, in run
mod = importlib.import_module(mod_name)
File "C:\ProgramData\Anaconda3\lib\importlib_init_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 994, in _gcd_import
File "", line 971, in _find_and_load
File "", line 955, in _find_and_load_unlocked
File "", line 665, in _load_unlocked
File "", line 678, in exec_module
File "", line 219, in _call_with_frames_removed
File "C:\Users\t842211\Documents\Python\GAN\Efficient-GAN-Anomaly-Detection-master\gan\run_mnist.py", line 9, in
from utils.evaluations import do_prc, do_roc
ImportError: cannot import name 'do_roc'
[13:10:42 ERROR @AnomalyDetection] Uhoh, the script halted with an error.

Hi Daniel,
Thanks a lot for reporting this, it should be fixed. If you notice something else, please let me know,
Best

hello,have you run the code successfully?


Replace expires with expires_in

Facebook has changed the name of the expires value
https://developers.facebook.com/docs/facebook-login/access-tokens/expiration-and-extension

Removed this after I saw PR 155. Our value switched from expires to expires_in today out of nowhere.


Failed to find exported plugin component for app-page-yourorg-simple-app-root-page-react

When deploying this plugin to a local grafana (master) version, the main entry page
http://localhost:3000/plugins/yourorg-simple-app/page/root-page-react
is unable to render but displays in the javascript console:
Plugin component error: "Failed to find exported plugin component for app-page-yourorg-simple-app-root-page-react" (plugin_component.ts:265)

Same. I notice that when you try to access the root page via the link on the app title, it's
/plugins/yourorg-simple-app/page/react-root-page

but when you access it via the link in the main nav, it's
/a/yourorg-simple-app/


rnv run -p androidtv without simulator results in launching simulator but not recognising it

ReNative run - _runGradle:androidtv - Starting!
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
? What emulator would you like to start? Android_TV_1080p_API_22 | TV 📺  | arch: x86 | udid: unknown
ReNative run - launchAndroidSimulator:androidtv:Android_TV_1080p_API_22 - Starting!
execCLI:androidEmulator:-avd "Android_TV_1080p_API_22"
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 1/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 2/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 3/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 4/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 5/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 6/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 7/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 8/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 9/10
ReNative run - _listAndroidTargets:androidtv - Starting!
execCLI:null:echo "avd name" | nc localhost 5554
execCLI:null:echo "avd name" | nc localhost 5556
Can't find service: tv_input
Can't find service: tv_input
looking for active emulators: attempt 10/10
ReNative run - _askForNewEmulator - Starting!
❓ Do you want ReNative to create new Emulator (Android_TV_1080p_API_22) for you? (y) to confirm:

Same issue here
? What emulator would you like to start? Android_TV_720p_API_24 | TV 📺  | arch: x86 | udid: unknown
$ rnv run -p androidtv - launchAndroidSimulator:androidtv:Android_TV_720p_API_24 - Starting!
execCLI:androidEmulator:-avd "Android_TV_720p_API_24"
$ rnv run -p androidtv - _checkForActiveEmulator:androidtv - Starting!
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 1/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 2/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 3/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 4/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 5/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 6/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 7/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 8/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 9/10
$ rnv run -p androidtv - _listAndroidTargets:androidtv:false:true:false - Starting!
looking for active emulators: attempt 10/10
┌──────────────────────────────────────────────────────────────────────────────┐
│  🚀  SUMMARY | 8/8/2019, 1:46:13 PM                                          │
│  $ rnv run -p androidtv                                                      │
├──────────────────────────────────────────────────────────────────────────────┤
│  Project Name: hello-renative                                                │
│  Project Version: 0.1.0                                                      │
│  App Config: helloWorld                                                      │
│  Supported Platfroms: androidtv                                              │
│  Master Template: renative-template-hello-world                              │
│  Env Info: darwin | x64 | node v10.13.0 | rnv v0.24.0-alpha10                │
│  Platform: androidtv                                                         │
│  Executed Time: 0h:0m:52s:96ms                                               │
│                                                                              │
│ ⚠  $ rnv run -p androidtv - WARNING: You're missing /Users/steve/.rnv/hello-renative/appConfigs/helloWorld/config.private.json for this app: . You won't be able to make production releases without it!
│ 🛑  $ rnv run -p androidtv - ERRROR! Could not find any active emulatros
│                                                                              │
└──────────────────────────────────────────────────────────────────────────────┘

I have this same issue. I was able to resolve it by changing a setting on my virtual device:

Under "Advanced Settings" > "Boot Option", select the "Cold boot" option
Open 2 terminal windows

rnv start
rnv run -p androidtv

It will boot up the AndroidTV emulator, take some amount of time, and then wala!!!

I think this process doesn't work when reloading a saved image because it adds something to the boot loader/startup sequence to connect for a live streaming install onto the device.

Unstale
On Mon, Oct 7, 2019, 23:18 stale[bot]<EMAIL_ADDRESS>wrote:

This issue has been automatically marked as stale because it has not had
recent activity. It will be closed if no further activity occurs. Thank you
for your contributions.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/pavjacko/renative/issues/104?email_source=notifications&email_token=ABEQ5OULFT3REQNEUYRE4NLQNORQZA5CNFSM4HZK3YG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAR2W6Y#issuecomment-539208571,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABEQ5OVA6XLUMQYWKPND6DTQNORQZANCNFSM4HZK3YGQ
.

should be fixed by now


Wrong expiration computation in HardTimeoutExpirationPolicy

In 4.2, we had:

return (ticketState == null)
                || (System.currentTimeMillis() - ticketState.getCreationTime() >= this.timeToKillInMilliSeconds);

In 4.3, we now have:
return (ticketState == null) || ticketState.getCreationTime()
          .plus(this.timeToKillInMilliSeconds, ChronoUnit.MILLIS).isAfter(ZonedDateTime.now(ZoneOffset.UTC));

In fact, the ticket is expired if now is after creation date + timetokill. So there is an issue with the new test. It should be:
return (ticketState == null) || ZonedDateTime.now(ZoneOffset.UTC).isAfter(ticketState.getCreationTime()
          .plus(this.timeToKillInMilliSeconds, ChronoUnit.MILLIS));

or
return (ticketState == null) || ticketState.getCreationTime()
          .plus(this.timeToKillInMilliSeconds, ChronoUnit.MILLIS).isBefore(ZonedDateTime.now(ZoneOffset.UTC));

I can fix that with OAuth refresh tokens support (this is how I discovered the bug).

PR: https://github.com/Jasig/cas/pull/1629


Automated Package Upgrade

:tada: This PR is included in version 7.0.25 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: support and refactor for query radio

Description
Refactoring and add support for query radio (repo)

Moving shared structs from POI radio to here
Adding Prometheus crate and error variant for Queries

Will add an issue to update POI radio when upgrading to new SDK versions

Also included changes on targeting ~5min block interval for all networks and removing ETH_NODE env var


i + 1 Changes from Previous - Proposal

Multilingual Support
Include support for English and Spanish using available APIs. This feature aligns with enhancing accessibility for users. Prioritizing English and Spanish for now is practical.
Text Enhancement
Add functionality for enhancing or formatting text. This feature appears redundant for the project as it does not involve extensive text usage. I recommend omitting it unless future requirements demand otherwise.
Thesaurus
Use APIs to add a thesaurus feature, possibly in a separate tab. While not directly related to unit conversion, this could be added as a separate feature if necessary. Suggest evaluating its relevance to the project goals.
Customizable Conversion
Allow users to define custom conversion parameters. This feature seems partially implemented already. Clarification on the scope of "customizable" is needed to determine feasibility and implementation gaps.
Voice Input and Output - We can keep this a low-level priority as I feel this might complicate the project. If needed can we include this in the latter stages?

Let me know your comments on this @Ks-Weasley  and @Sanjaeyss

Multilingual support - Instead of Spanish, can we try to integrate Google Translate API so that multiple languages can be supported?

Thesaurus - I do not know how this will be useful for a Unit converter.

Multilingual support makes sense to me, as discussed earlier, it would enable a variety of users to utilize the extension.
In my opinion, I see no need for a thesaurus for this application and especially not at this time. Maybe along the line when this application evolves into a Multi functional tool, rather than a conversion tool.

Lets Continue the work going on and See where it takes.


:feet:  In VMware provider, use ca cert instead of fingerprint

Issue:
in Forklift 2.6, the vmWare provider will use ca cert similar to RHV and Openstack
Fix:
Remove the fingerprint code for vmWare provider and replace with ca cert similar to what we currently have for RHV and Openstack
How it is now (need fixing for 2.6):

How it should be in vmWare too:

Addressed by #894


[Issue 699] - Reporter should receive DM when someone comments on their issue  fixes #699

This PR modifies appendCommentNotifications so both Assignee and Reporter will get a notification when someone comments on their issue (previously, only Assignee gets the notification)
ticket here
https://github.com/mattermost/mattermost-plugin-jira/issues/699

@mickmister closing this PR as feel it would be more easy to implement the changes in new branch as some code breaks the plugin


Fix/implement display of local files

At the moment, it's not possible to open local files, neither via file:/// URL nor by visiting an about: page.
It's not apparent from the logs where the error happens.
(0.211791) [INFO netsurf] content/content.c:666 content_add_user: content resource:welcome.html (0x1dceb20), user 0x1202f4 0x1d72b80
(0.214915) [INFO netsurf] content/content.c:695 content_remove_user: content resource:welcome.html (0x1dceb20), user 0x1202f4 0x1d72b80
(0.215757) [INFO netsurf] desktop/browser_window.c:3783 navigate_internal_query_fetcherror: bw:0x1d58910 params:0x7ec599e4
(0.216057) [INFO netsurf] desktop/browser_window.c:3544 navigate_internal_real: Loading 'about:query/fetcherror'

This was because when opening a local file, netsurf sets the target encoding to Windows-1252, and calls iconv for conversion. This conversion is not supported on the iconv available on reMarkable.
A fix for now is achieved with a fork of libhubbub, which sets the default encoding to UTF-8.
However, the real long-term solution would be to link to a version of iconv that can handle these encodings.