ISPN-13931 SoftIndexFileStore is increasing the size of the data folder

https://issues.redhat.com/browse/ISPN-13931
Persist the file stats upon shutdown so upon restart we know what the previous free space was.
The test passes however there is still an issue with the case when the stats file is not present that the free space is not read in properly afaik. I am still trying to fix this last part, as it is required for migration of existing directories and should clean those up if they have old files lying around.

Looking closer today I found the discrepancy with the free value is due to the index being updated asynchronously. After adding in joins to the index built at startup the values match up properly, so this PR should be good to go.

Updated

Looks like there are some related test failures I didn't see before.. checking those as well.

@wburns NullPointerException in testsuite.

@wburns NullPointerException in testsuite.

Yeah, I mentioned above that there are a bunch of tests failures. Not sure what is going on exactly. It appears to be a concurrency issue that I haven't tracked down yet.

The failure is related to rebuilding the index for some reason the compactor isn't populating the free size properly anymore.

Actually upon further inspection this issue is MUCH bigger... If a value is overwritten and the index is lost when reloading the index it uses the first value it finds and not the most up to date one...
Tweaking the test a bit I can see it resurrecting an old value :(

Tests should be fixed now, waiting on CI. Logging a JIRA to fix the zombie entry being brought back that is commented out for now.

CI is still complaining...
I think the issue is that clear() is invoked before stop() and it is setting logFile=null. When onComplete lambda is invoked, it throws the NPE.
Also, running locally, all tests are green but there are some NullPointerExceptions in the log file
Caused by: java.lang.NullPointerException
        at org.infinispan.persistence.sifs.Index$Segment.run(Index.java:537) ~[classes/:?]
        at io.reactivex.rxjava3.internal.subscribers.LambdaSubscriber.onComplete(LambdaSubscriber.java:94) ~[rxjava-3.1.3.jar:?]
        at io.reactivex.rxjava3.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.checkTerminated(FlowableObserveOn.java:217) ~[rxjava-3.1.3.jar:?]
        at io.reactivex.rxjava3.internal.operators.flowable.FlowableObserveOn$ObserveOnSubscriber.runAsync(FlowableObserveOn.java:396) ~[rxjava-3.1.3.jar:?]
        at io.reactivex.rxjava3.internal.operators.flowable.FlowableObserveOn$BaseObserveOnSubscriber.run(FlowableObserveOn.java:178) ~[rxjava-3.1.3.jar:?]
        at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker$BooleanRunnable.run(ExecutorScheduler.java:324) ~[rxjava-3.1.3.jar:?]
        at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker.runEager(ExecutorScheduler.java:289) ~[rxjava-3.1.3.jar:?]
        at io.reactivex.rxjava3.internal.schedulers.ExecutorScheduler$ExecutorWorker.run(ExecutorScheduler.java:250) ~[rxjava-3.1.3.jar:?]
        at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) ~[jboss-threads-2.3.3.Final.jar:2.3.3.Final]
        at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) ~[jboss-threads-2.3.3.Final.jar:2.3.3.Final]
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) ~[jboss-threads-2.3.3.Final.jar:2.3.3.Final]
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) ~[jboss-threads-2.3.3.Final.jar:2.3.3.Final]

2022-06-22 13:54:21,773 ERROR (testng-SoftIndexFileStoreTest) [org.infinispan.persistence.sifs.Compactor] ISPN029021: File id 3 encountered an exception while compacting, file may be orphaned
java.lang.NullPointerException: null
        at org.infinispan.persistence.sifs.IndexNode.applyOnLeaf(IndexNode.java:299) ~[classes/:?]
        at org.infinispan.persistence.sifs.Index.getInfo(Index.java:240) ~[classes/:?]
        at org.infinispan.persistence.sifs.Compactor.compactSingleFile(Compactor.java:482) ~[classes/:?]
        at org.infinispan.persistence.sifs.Compactor.accept(Compactor.java:381) ~[classes/:?]
        at io.reactivex.rxjava3.internal.subscribers.LambdaSubscriber.onNext(LambdaSubscriber.java:65) ~[rxjava-3.1.3.jar:?]
       ... removed since it is quite large stack trace
       at org.infinispan.persistence.sifs.NonBlockingSoftIndexFileStore.start(NonBlockingSoftIndexFileStore.java:216) ~[classes/:?]
       ....

I pushed some more changes that fixed a couple more things that were causing the free value to be attributed to the wrong file thus causing test failures. Due to the asynchronous nature of indexing it was only easily reproducible running with less CPU cores.

After rebase and recent changes CI is now passing and I am unable to see any exceptions logged when running with full trace on a single core.

merged! thanks @wburns !


LokiJS sensible defaults thinks application is running in node-webkit (react + babel + webpack project)

This issue was originally about LokiJS having a call to require('fs'), but then I found that was actually not the issue, so I've refactored the issue. Sorry about all the confusion (and notifications)

We've got a React web application being built using Webpack (with Babel 6), with the Webpack CDN plugin.
For some reason, global.window is set, causing LokiJS to think it's running in a node-webkit env (due to line 829), and thus trying to use the fs adapter.
https://github.com/techfort/LokiJS/blob/71139c9fb8ae35a5a03a5d2fdc55678fcad9f255/src/lokijs.js#L819-L840
I've not used node-webkit, so I can't try and compare the two Window objects to try and find a consistent difference that can be used for comparison.
I did find this babel issue however, that suggests checking if process is defined, which should be defined if you're using node-webkit, but not in the browser (if I'm understanding node-webkit correctly).
For now, I'm just going to specify the environment explicitly.

Ugh as soon as I posted this i went back and saw that it's actually because it's trying to use that adapter (if it wasn't, it wouldn't hit the require call, and so not have a problem).
Still, this might mean that the sensible defaults are not properly detecting the browser?
I'll come back once I've adjusted the defaults on my end :)

So LokiJS figures out what it's running in using this logic:
https://github.com/techfort/LokiJS/blob/master/src/lokijs.js#L819-L840
The problem seems to be that for some reason global.window is defined, making LokiJS think it's running in a node-webkit environment?
I'm trying to figure out what defines global.window, and for possible workarounds. This project is using React, React-DOM, React-Redux, Webpack and Babel, so there are some major players it could be coming from.

Your suggestion make sense so I have updated environment detection as recommended.  Eventually this will make it into a 1.5.4 release but probably not too soon.  Until then it is on main branch.
Thanks!


Address JOSS review comments

I will be using this issue to address the JOSS review comments by @alexgleith in https://github.com/openjournals/joss-reviews/issues/7025#issuecomment-2297757431
PRs will be created to address each comments if needed.

Some very minor comments on code quality:

There are some unused imports, like numpy in desis.py and others that are probably imported for the context function (not the right word), but should be annotated, like import hvplot.xarray  # noqa F401. These are little, but my linter highlights them, and it's cleaner to fix it.
In the main hypercoast.py file, there are * imports, which are not recommended from .aviris import *
spectral is used, but isn't in the dependencies list
I'll make a PR with some example code cleanups.

Some opinions from me:

I don't like that EMIT data has been stored in GitHub, like this: https://github.com/opengeos/datasets/releases/tag/netcdf. I would much prefer that the notebooks point to the data direct at NASA.
Following on from the first point, wrapping up the EarthData access into the download_nasa_data function, which calls leafmap.nasa_data_download, which then calls earthaccess.download is two abstractions too far! It does make it simple, though. I have an example over here that uses NASA's STAC API to find EMIT granules and load them, and it's still pretty complex, but what is good is that it uses the open standard STAC to discover granules.
It's great that the function emit_xarray has been adapted to make wavelength a dimension!
I can't see how this method, in the emit.ipynb notebook is working, or if it works. I tried changing the numbers and nothing changed: m.add("spectral", xlim=(400, 1400))
The function m.spectral_to_df() structures the dataframe in an unexpected way. I think exporting something with a geometry, or with lon/lat columns and 285 more spectral columns would make more sense, even if the structure is a bit clumsy.

On the review points, I'd like a couple of changes please:

For installation, please make sure all dependencies are listed in the pyproject.toml file (spectral was not, and neither was pyvista). Edit: resolved by removing unused code.
For community guidelines, please include a contributing file. Edit: my mistake, there's a contributing file in the docs folder.

I don't like that EMIT data has been stored in GitHub, like this: https://github.com/opengeos/datasets/releases/tag/netcdf. I would much prefer that the notebooks point to the data direct at NASA.

The purpose of those three sample files was to make the GitHub Actions unit tests run faster. It takes ~30 seconds to download the sample data, a bit faster than downloading using earthaccess. As we have many notebook examples that use EMIT and PACE data, I try to avoid using my personal NASA EarthData account for authentication to repeatedly downloading these datasets for every commits in a PR.
Additionally, the sample data lowers the barriers for users to try out the HyperCoast features. Users can launch the notebook on Google Colab and explore the functionality without having to sign up for a NASA EarthData account and authenticate it in the notebook. We do provide a separate notebook example (search_data.ipynb)  that demonstrates how to download NASA EarthData interactively and programmatically.
@alexgleith   Would these arguments be acceptable to you?

I can't see how this method, in the emit.ipynb notebook is working, or if it works. I tried changing the numbers and nothing changed: m.add("spectral", xlim=(400, 1400))

The xlim parameter is used to limit the wavelength range to be displayed on the plot. It works as expected on my end.
Without xlim
m = hypercoast.Map()
m.add_basemap("SATELLITE")
m.add_emit(dataset, wavelengths=[1000, 600, 500], vmin=0, vmax=0.3, layer_name="EMIT")
m.add("spectral")
m

With xlim
m = hypercoast.Map()
m.add_basemap("SATELLITE")
m.add_emit(dataset, wavelengths=[1000, 600, 500], vmin=0, vmax=0.3, layer_name="EMIT")
m.add("spectral", xlim=(400, 1200))
m

wavelength range to be displayed on the plot

Ah, on the plot! I was expecting it to stretch on the map. Now it makes sense that it's xlim and not zlim for the actual visualisation.

The function m.spectral_to_df() structures the dataframe in an unexpected way. I think exporting something with a geometry, or with lon/lat columns and 285 more spectral columns would make more sense, even if the structure is a bit clumsy.

The strcture of the dataframe looks like this. It is easier to plot a data strucutre like this with bqplot (the libary we use for plotting spectral profiles), which takes a dataframe with x and y columns.
However, I do like your suggestion for export something with a geometry. I will create a spectral_to_gdf method for exporting a geodataframe. One caveat is that the shapefile format generally does not like >256 columns. Anyway, we can let users decide what vector data format they want to convert the GeoDataFrame to.

The purpose of those three sample files was to make the GitHub Actions unit tests run faster.

This makes sense.

We do provide a separate notebook example (search_data.ipynb) that demonstrates how to download NASA EarthData interactively and programmatically.

It does, but it also wraps the earthdata functions in a leafmap function that is used by the separate hypercoast function. I'm not really sure why it does this, and it obfuscates the way that the underlying earthdata API, and Python libraries work.

I will create a spectral_to_gdf method for exporting a geodataframe.

Good idea!

the shapefile format generally does not like >256 columns

Hmm, yeah, a bit of an issue, but it's nice to have an excuse to not support Shapefiles! haha

The Map.spectral_to_gdf() method has been added in https://github.com/opengeos/HyperCoast/pull/118

It does, but it also wraps the earthdata functions in a leafmap function that is used by the separate hypercoast function. I'm not really sure why it does this, and it obfuscates the way that the underlying earthdata API, and Python libraries work.

The leafmap.nasa_data_search() function wraps the earthaccess.search_data() method with additional inprovements, such as returning the data footprints as a GeoDataFrame, or saving it as a vector format (e.g., geojson, shapefile).
https://github.com/opengeos/leafmap/blob/a6dae078146064a870fa2aada5d462259651e3bc/leafmap/common.py#L13296
The reason that hypercoast wraps the leafmap functions is to simplify the import statements in the notebook examples. Most notebook examples only need import hypercoast so that users don't need to learn other dependencies.

@alexgleith I have fixed the linter warnings in https://github.com/opengeos/HyperCoast/pull/128. Thank you once again for taking the time to review it and providing constructive feedback.

Thank you once again for taking the time to review it

You're very welcome, @giswqs. Thank you for being receptive to the feedback!


Moving history to new ~/.dlv config path

Fixes #81
This is also a setup for a ~/.dlv/,dlv.conf file to allow commands to be run at startup (i.e. change display modes).

It does give USERPROFILE on windows.
While the official recommendation from MS is to use the LocalAppData system folder pretty much all the cross platform apps on my Win7 box appear to use a dot directory in USERPROFILE including VirtualBox, Vagrant, Maven, Netbeans, Babun, Atom, and CMake.

This looks good but I'm going to wait until #88 lands to pull this in.

@epipho now that #88 has been merged, can you take a look at rebasing this and pushing back up? I'd be happy to pull this in after that.

Yep I'll take a look this weekend.
On Wed, Apr 29, 2015 at 10:20 PM, Derek Parker<EMAIL_ADDRESS>wrote:

@epipho https://github.com/epipho now that #88
https://github.com/derekparker/delve/pull/88 has been merged, can you
take a look at rebasing this and pushing back up? I'd be happy to pull this
in after that.
—
Reply to this email directly or view it on GitHub
https://github.com/derekparker/delve/pull/98#issuecomment-97635545.

Closing this in favor of #124


Track player inventory

The Players now have a PlayerInventory component to store the items.
The current status is usable. At the moment it is possible:

to give and remove items within the source code
players see which item other players have in the hand
to give players items with /give

I think the biggest todo before this PR can be merged is to support the moving/splitting of items in the inventory. And to other inventories like chests or something.

looks good so far :)

It mostly works now.
Players can move the items in the inventory.
The eqipment like armor is shown to other players.
At the moment The ClickMode and button does not really have an effect.
It just applies the slot changes sent by the client and checks if the sum of the items is still correct. I am not sure if this is the best way to do it.
Open Todos are:

[ ] make sure that there are no edge cases which allow clients to create new items
[ ] unittests for inventory
[ ] cleanup

great work :)
I am ready to merge when we are decently confident.

make sure that there are no edge cases which allow clients to create new items

I could see this being a big issue in an event.

I improved a couple things; merging :)


Refactor/fix Usul subDAO veto guard handling

After implementing  https://github.com/decent-dao/fractal-interface/pull/971 - we discovered that there're certain cases in code, where we're ignoring vetoGuard for Usul-based subDAOs.
So, something like following code in useActivities - should be fixed and proper veto guard should be passed.
vetoGuardType === VetoGuardType.MULTISIG
      ? (vetoGuardContract?.asSigner as VetoGuard)
      : undefined

This makes sense to focus on -- I'm assuming some Usul functionality is broken due to this issue, which would make it a solid priority.

I feel like we should hold this issue until we're done with Azorius adoption on Front-End side

yeah good call

This should be taken care of as well


Opitimize the resource status display of cloud provider resources that do not support status synchronization

Version: main
UI: dev-6168160
Commit ID: 2123c63e14cb8461eb00fc5a594999b5bc82483d
Env: MacOS 13.1, Apple M2
For cloud provider resources that do not support status synchronization, the resource status is displayed as -.

Environment

Walrus version: main fb8dcbba8e926e4fe7b1498ae88344c9d8cbff7a
UI version: dev-807612f

Test Result: pass


Add reCAPTCHA to both frontend and backend.

Due to errors in production, Google reCAPTCHA was removed in both the repos. It would be a really helpful if this could be fixed on either or both the repos through a PR.

Frontend Repo
Backend Repo

Done


Simplify scoring rules

Separate "precondition" and "when do you get the points"
--> auch in R-Script umsetzen.

Another goal would be that users can adjust the scoring interactively in the dashboard of the RESQUER package.
I have no solution for that, but maybe you can keep that in mind when you take a look at score.R


Disable insecure parameters by default

This patch sets by default for all test pods:

runAsNonRoot: true
automountServiceAccountToken: false

These two parameters shouldn't be enabled unless necessary for any
pods in the OCP cluster. The runAsNonRoot parameter ensures that
the container process does not run as root nor does it switch to
root user after it has been spawned.
And the automountServiceAccountToken makes sure that we are not
mounting service account tokens into the test pods. This would
allow them to modify the state of the OCP cluster. As of now the
service account tokens are not required by any of the test pods.
This behavior can be overridden by setting privileged: true.

recheck

/hold
Let's first merge this one -> https://github.com/openstack-k8s-operators/test-operator/pull/256

/test test-operator-build-deploy

/test test-operator-build-deploy

/test test-operator-build-deploy


Please update staticcheck/megacheck

The vendored version of staticcheck/megacheck does not include all present bugfixes, e.g., it does not find deprecated methods, see https://github.com/dominikh/go-tools/issues/215 . Please update.

This has now been merged. But now honnef.co tools have $year.$release version numbers, we should probably follow those instead.


Add linux support

Hey Paradoxis,
I'm using your script already on linux but the syntax is a little different.

shuf -n 1
I'm using mpv --really-quiet to play the music files but maybe there is a more generic solution.

# Copyright (c) 2017 - Paradoxis
function gordon()
{
    if [[  $? != 0 ]]; then
        insult=$(ls $GORDON_INSULTS | shuf -n 1)
        mpv --really-quiet $GORDON_INSULTS/$insult &
        disown
    fi
}
GORDON_INSULTS=~/.insults
PROMPT_COMMAND=gordon

I've put this script in my ~/.bashrc ;)
Edit: You can also use ffplay
ffplay v 0 -nodisp $GORDON_INSULTS/$insult & disown

Implemented in 357a33d95a9bb665664c054c0c35d1735f0322e9


Make it clear what color means

Problem
I found it hard to know what color stands for in Rust Machine Learning Ecosystem section.
Can we clarify what each color means?
Prior art
In Are we web yet, we have following explicit label on each states.

everything is awesome
stable, tested and mature
stuff's pretty great
getting there
stable but still maturing
not yet stable, but progressing
unstable/incomplete, needs work
barely there, needs serious work
basically nonexistent

Not revive an old-ish issue, but if you look at the about page on the website (link at the bottom of the page) it has the color key.

Then it's a discoverability issue. It'd better put a label on the main page.


Lambda Layer Update - OTel Java 1.11.1

This PR updates OTel Java dependencies to 1.11.1 and other dependencies to their latest available
It also updates the _HANDLER for the layer scripts with available wrappers

Thanks @anuraaga


Accented characters in NFO cause it to show up as blank

I was categorizing a Mexican TV show called El Chapulín Colorado, and the presence of í in the NFO causes it to render blank.

Is the folder called El Chapulín Colorado? Try renaming the folder for test

The folder does not have any accents, path is:
E:\Temporary files\New folder\El Chapulin Colorado

I can toggle between it working and not working by saving the NFO with/without an accented character


feat: optimize the developer experience

Here is my list of things to do to optimize the developer experience.
Documentation: build development environment (with docker), deploy (with docker)
Code: optimizing the scope of functions, adding comments
Testing: remove test cases written in java code, test with e2e

I have submit a PR : #213 to enhance the quick start experience, but it is still not convenient to developing a java plugin. I will  continue to improve the developing experience.
My basic idea is  mounting  apisix-java-plugin-runner.jar to apisix container. This action should along with docker run ... or dcoker-compose up ... command. Now I am using a docker compose config  as a template. How could I submit my changes,if i complete the work ?  In repo
apisix-java-plugin-runner or  apisix-docker?

My basic idea is mounting apisix-java-plugin-runner.jar to apisix container. This action should along with docker run ... or dcoker-compose up ... command.

I would like to divide this matter into two topics.

rapid build development environment
deploying as a container image

if i complete the work ? In repo
apisix-java-plugin-runner or apisix-docker?

this repo


fix F.convolution_2d and F.deconvolution_2d to work without cuDNN

Without cuDNN, _cudnn_version is undefined.
Related to #3494.

I think you can define it with a single expression.
            use_cudnn = (
                chainer.should_use_cudnn('>=auto')
                and not self.cover_all
                and x.dtype == W.dtype
                and ((self.dy == 1 and self.dx == 1) or _cudnn_version >= 6000)
                and (self.group <= 0 or _cudnn_version >= 7000)
            )

(also it's better to split x.dtype == W.dtype in a separate line.)

@niboshi Thanks! Fixed as suggested.

Please merge this after #4078.

Jenkins test this please

Now #4078 is merged.

Rebased.

LGTM!


Calling a Getter with parameters

Is there a solution for this use case?

If a getter needs to be dynamic then it should be composed of another getter that represents the parameter as state in the system.
For example, imagine we have a store mantaining the state of a map of id => ListItem, and a store maintaining the currently selected item id.
var selectedItemGetter = [
  ['listItems'],
  ['selectedItemId'],
  function(items, id) {
    return items.get(id)
  }
]

The idea of using getters is it provides a unit of immediate evaluation for some state in the system.  Another way to think about a Getter is it represents a question, in our case "What is the currently selected item?"  We can get the answer to that question immediately via flux.evaluate(selectedItemGetter) or get notified whenever the answer changes via flux.observe(selectedItemGetter, handlerFn)
If you want to create a function that evaluates a getter based on the parameters it would look like:
function getItem(id) {
  return flux.evaluate([
    ['items'],
    function(items) {
      return items.get(id)
    }
  ])
}

Could you also use a function to create a getter?
function getItem(id) {
  return [
    ['items'],
    function(items) {
      return items.get(id)
    }
  ]
}

@jordangarcia In your getItem() example, where do you imagine that living? In actions.js? It seems like a fundamental requirement of a getter is that it is an array, so even though this is technically gets data, it seems like it cannot go there since it doesn't fit into the prescribed pattern. The only other place I can see it logically going is actions, or maybe index, however I wanted to get your perspective. Thanks.

It should live in your getters.js as it is related to getters.


Add filter toArray;

The PR adds new filter toArray. The purpose of the filter is to fix the problem from #302.
With the new filter the problem that was mentioned can be solved by doing:
{% for type in types.protocols|annotated:"TypeErase" %}
{% for key,value in type.annotations %}
{% for values in value | toArray %}
Do something witht the annotation value
{% endfor %}
{% endfor %}
{% endfor %}

The logic of the filter is:

If value is already array - do not modify value
If value is not array - convert it into array with one value

          1 Error

:no_entry_sign:
Any changes to library code need a summary in the Changelog.

  Generated by :no_entry_sign: Danger


Pom updates, deprecate createSciView, fix race condition in makeSciView

Getting an error from copy-jars when i upgrade to pom-scijava 28.0.0
https://travis-ci.org/github/scenerygraphics/sciview/builds/668456987#L1336

@ctrueden if you have any thoughts about ^^^ they would be appreciated

Here is a patch which avoids the miglayout problems:
commit 3044b87f4a18560ef69936e551cbdaf58f54eec8 (HEAD -> prebvv-update)
Author: Curtis Rueden<EMAIL_ADDRESS>Date:   Sun Mar 29 21:05:01 2020 -0500

    POM: update dependency versions

    And pin to new-enough component versions
    to avoid miglayout dependency skew.

diff --git a/pom.xml b/pom.xml
index da66d9d..3b474b8 100644
--- a/pom.xml
+++ b/pom.xml
@@ -5,7 +5,7 @@
        <parent>
                <groupId>org.scijava</groupId>
                <artifactId>pom-scijava</artifactId>
-               <version>27.0.1</version>
+               <version>28.0.0</version>
                <relativePath />
        </parent>

@@ -108,7 +108,11 @@
                <!-- NB: Deploy releases to the SciJava Maven repository. -->
                <releaseProfiles>deploy-to-scijava</releaseProfiles>

-               <imagescience.version>3.0.0</imagescience.version>
+               <scijava-ui-awt.version>0.1.7</scijava-ui-awt.version>
+               <scijava-ui-swing.version>0.13.1</scijava-ui-swing.version>
+               <scijava-search.version>0.7.0</scijava-search.version>
+               <script-editor.version>0.5.4</script-editor.version>
+               <imagej-ui-swing.version>0.23.2</imagej-ui-swing.version>

                <scenery.version>754815c</scenery.version>
                <cleargl.version>2.2.10</cleargl.version>
@@ -215,14 +219,6 @@
                        <artifactId>joml</artifactId>
                </dependency>

-<!--           only added to resolve maven issues-->
-               <dependency>
-                       <groupId>sc.fiji</groupId>
-                       <artifactId>imagescience</artifactId>
-                       <version>${imagescience.version}</version>
-                       <optional>true</optional>
-               </dependency>
-
                <!-- Optional dependencies - for sc.iview.Main only! -->
                <dependency>
                        <groupId>io.scif</groupId>

But then there is another error:
[ERROR] Failed to execute goal org.scijava:scijava-maven-plugin:1.1.1:copy-jars (copy-jars) on project sciview: Couldn't determine scijava.app.subdirectory for org.scala-lang.modules:scala-xml_2.12:jar:1.0.6: Some problems were encountered while processing the POMs:
[ERROR] [ERROR] Unknown packaging: bundle @ line 6, column 16: 1 problem was encountered while building the effective model for org.scala-lang.modules:scala-xml_2.12:1.0.6
[ERROR] [ERROR] Unknown packaging: bundle @ line 6, column 16

The real fix needs to happen in the scijava-maven-plugin. You aren't the only one having this problem—someone (me, or maybe @frauzufall or @turekg) will try to investigate and fix soon.

@kephale Now that pom-scijava 29.0.0-beta-1 is released, please let me know if there is anything further I can do to help get this PR resolved!

Not needed due to recent merges.


Reverse shell ?

Hi i know this isnt a issue but it would be nice with a reverse shell :)

Hey @cudden24 thanks for the suggestion i will surely add a reverse shell with it.

Thanks ! 👍


Verify whether we need to add clip masks to container

Not adding masks (currently 3 different ones) to the container caused interior shadows to disappear, so at least that portion of the render needs to be examined.


Retrieve where capabilities should have a limit

We need a way to enable/disable some capabilities on specific fields

Implemented in 0365b5ba7b3b4087071ab7e6654c5756580e2af3
Can be improved by specify the various filter like in, eq, gt, gte, ...


How can we add more translations.

Say I wish to add another version in json format. How would I go about that.

Create a new directory in the bibles, in the appropriate language section. For example, if the version you want to add is AMP and it's English (denoted by en), you'll create an amp directory in the bibles/en folder.

Then upload the bible books in that newly created folder as is here https://github.com/djunehor/laravel-bible/tree/master/bibles/en/kjv

Once all that is done, you should be able to access your newly added version via these steps: https://github.com/djunehor/laravel-bible#dynamically-setting-language-andor-version


Support multiple datatypes for all kernels

Right now, the code is not implemented in a templated manner, meaning we can only support double values and int64 coordinates in our sparse matrices. A large refactor should be done to templatize the code and dispatch to implementations of the right type.

This is now done. The remaining thing to track is the removal of all calls to require_float_64_dtypes in the codebase, and add the corresponding tests.


Atm_button AUTO conflicts with another library

Just a note that Atm_button's AUTO conflicts with the very popular MySensors library.
I end up manually changing Atm_button's AUTO to something else in order to compile my sketches. Which of course, I end up doing each time I update Automaton… :) Maybe there is a better solution on my end, but if so, I'm not familiar with it.
Thank you for your work! Even though I only use a small part of Automaton, it has made my code so much more concise and understandable!

I end up manually changing Atm_button's AUTO to something else in order to compile my sketches. Which of course, I end up doing each time I update Automaton… :) Maybe there is a better solution on my end, but if so, I'm not familiar with it.

It's nicely packed inside its own namespace (class) so it must be the other library that's misbehaving :-( Still, it's easy to fix since it's only used internally. I changed it in the last commit.

Thank you for your work! Even though I only use a small part of Automaton, it has made my code so much more concise and understandable!

Thanks, that's a great compliment!

Thanks for changing it despite another library being the one that is misbehaving. :)


Rerunning the same flutter test test on a target device causes a full rebuild every time

flutter test is taking almost the same amount of time on a second run as the first, when the app should already be built.
On iOS this causes every test run to take an additional ~15 seconds.
test is subverting flutter assemble caching logic by passing in a new temp directory target listener.dart path every run, even when running the same test.  This causes the build system to create a new build directory from the hash of the inputs including TargetFile.
https://github.com/flutter/flutter/blob/61a0add2865c51bfee33939c1820709d1115c77d/packages/flutter_tools/lib/src/build_system/build_system.dart#L351-L358
Every subsequent test run shows the assemble steps as needing a rerun due to InvalidatedReasonKind.inputChanged since each new build directory is missing the file store cache file from the last run:
            [  +31 ms] debug_unpack_ios: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: /Users/m/Projects/flutter/packages/flutter_tools/lib/src/build_system/targets/ios.dart,/Users/magder/Projects/flutter/bin/internal/engine.version}
            [+1026 ms] Skipping target: gen_localizations
            [   +5 ms] gen_dart_plugin_registrant: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: /Users/m/Projects/plugins/packages/google_maps_flutter/google_maps_flutter/example/.dart_tool/package_config_subset}
            [   +4 ms] debug_unpack_ios: Complete
...
            [   +6 ms] gen_dart_plugin_registrant: Complete

For example, in google_maps_flutter example project running the same command twice:
$ flutter --no-color test --machine --start-paused --plain-name testGetVisibleRegion  -v integration_test/google_maps_test.dart

calls identical assemble except for the different -dTargetFiles:

--verbose assemble --no-version-check --output=/Users/m/Projects/plugins/packages/google_maps_flutter/google_maps_flutter/example/build/ios/Debug-iphonesimulator/ -dTargetPlatform=ios -dTargetFile=/var/folders/bx/pyplw7v92lj58gm3_lztz5sc00mfq2/T/flutter_tools.5RYflD/flutter_test_listener.sO5mgy/listener.dart -dBuildMode=debug -dIosArchs=x86_64 -dSdkRoot=/Users/m/Applications/Xcode-14_beta3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.0.sdk -dSplitDebugInfo= -dTreeShakeIcons=false -dTrackWidgetCreation=true -dDartObfuscation=false -dEnableBitcode= --ExtraGenSnapshotOptions= --DartDefines=RkxVVFRFUl9XRUJfQVVUT19ERVRFQ1Q9dHJ1ZQ==,SU5URUdSQVRJT05fVEVTVF9TSE9VTERfUkVQT1JUX1JFU1VMVFNfVE9fTkFUSVZFPWZhbHNl --ExtraFrontEndOptions= -dCodesignIdentity=- debug_ios_bundle_flutter_assets

--verbose assemble --no-version-check --output=/Users/m/Projects/plugins/packages/google_maps_flutter/google_maps_flutter/example/build/ios/Debug-iphonesimulator/ -dTargetPlatform=ios -dTargetFile=/var/folders/bx/pyplw7v92lj58gm3_lztz5sc00mfq2/T/flutter_tools.r0Vvcj/flutter_test_listener.uguobQ/listener.dart -dBuildMode=debug -dIosArchs=x86_64 -dSdkRoot=/Users/m/Applications/Xcode-14_beta3.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator16.0.sdk -dSplitDebugInfo= -dTreeShakeIcons=false -dTrackWidgetCreation=true -dDartObfuscation=false -dEnableBitcode= --ExtraGenSnapshotOptions= --DartDefines=RkxVVFRFUl9XRUJfQVVUT19ERVRFQ1Q9dHJ1ZQ==,SU5URUdSQVRJT05fVEVTVF9TSE9VTERfUkVQT1JUX1JFU1VMVFNfVE9fTkFUSVZFPWZhbHNl --ExtraFrontEndOptions= -dCodesignIdentity=- debug_ios_bundle_flutter_assets

https://github.com/flutter/flutter/blob/db829c1e200823cd655a6e0ca326967ff89d9c4f/packages/flutter_tools/lib/src/test/flutter_platform.dart#L570-L578

Maybe the listener.dart can be created in a stable place in the build directory instead of a tmp directory.

Maybe the listener.dart can be created in a stable place in the build directory instead of a tmp directory.

this sounds smart

This is really limiting the speed when doing practical and real integration testing for production apps. These like to use large scale many device integration testing runs to validate before final release eg. Integration test suite run against 12 Simulators, 6 real iOS/iPadOS devices + 12 Emulators, 6 real Android devices.
So the complete test run across all devices means a much longer test run than it should given that we are testing the exact same Android and IOS builds of the app over many devices.

When is someone going to look at this PR?  Thanks!


Remove closures discussion from control flow document

The problem
The whole explanation for the difference between block and closure is LTA #3670
Solution provided
Removes reference to closures from this document. Blocks are closures, but it doesn't seem relevant in this context, and is a digression.
Adds some explanation of why you might use a block statement.
Also fixes link to Block type - which, perhaps, should have a reference to closures. Either a link to https://docs.raku.org/language/functions#index-entry-closures or a repeat of the information.

I've made this a draft to prevent it getting accidentally merged without some scrutiny, as my understanding may be flawed.

Rejecting this - JJ's comments were never addressed - Please feel free to re-submit when these items are addressed.


feat: add DevTools hook

Fixes #2003
This adds a DevTools hook to inspect DevTools middleware.
SWR has to expose the React instance to the DevTools to avoid a multiple React instance error in the DevTools middleware.
I've also worked on the DevTools side at https://github.com/koba04/swr-devtools/pull/55

Perfect, thank you!

Thank you!


"Routing table is updated" info log on every transaction

Hi,
Every time I execute a transaction the following information log gets printed:
info: MyService.Loggers.Neo4jLogger[0]
      Routing table is updated => RoutingTable{database=neo4j, routers=[neo4j://localhost:7687/], writers=[neo4j://localhost:7687/], readers=[neo4j://localhost:7687/], expiresAfter=300s}

Is this normal?
Neo4j Version: 5.1.0  Community
Neo4j Mode: Single instance
Driver version: .NET driver 5.1.0
Operating System: Linux 6.0.2-arch1-1 x86_64

If you are using a single instance you can specify the bolt scheme and this will avoid this issue.
Alternatively you need to specify which database you are attempting to connect to when opening a session.

Glad to hear it is resolved.
Going to close this issue out, If you need further assistance please re-open it.


Add additional types to dbmodel

While creating data for EIS Fire project (see https://github.com/NASA-IMPACT/veda-features-api/pull/10) Alexey noticed that the queryables endpoint for the fire perimeter data is returning strings for. many of the fields (see https://sbbj812m1j.execute-api.us-west-2.amazonaws.com/collections/public.eis_fire_perimeter/queryables).
I inspected the table schema and found the data is stored in the database correctly, i.e.:
from sqlalchemy import text
engine = create_engine(f"postgresql://{username}:{password}@{host}:5432/{database}")
sql = text("""
SELECT
   table_name,
   column_name,
   data_type
FROM
   information_schema.columns
WHERE
   table_name = 'eis_fire_perimeter';
""")
result = engine.execute(sql)
result.fetchall()

returns
[('eis_fire_perimeter', 'ogc_fid', 'integer'),
 ('eis_fire_perimeter', 'n_pixels', 'bigint'),
 ('eis_fire_perimeter', 'n_newpixels', 'bigint'),
 ('eis_fire_perimeter', 'farea', 'double precision'),
 ('eis_fire_perimeter', 'fperim', 'double precision'),
 ('eis_fire_perimeter', 'flinelen', 'double precision'),
 ('eis_fire_perimeter', 'duration', 'double precision'),
 ('eis_fire_perimeter', 'pixden', 'double precision'),
 ('eis_fire_perimeter', 'meanfrp', 'double precision'),
 ('eis_fire_perimeter', 't', 'character varying'),
 ('eis_fire_perimeter', 'fid', 'bigint'),
 ('eis_fire_perimeter', 'wkb_geometry', 'USER-DEFINED')]

so I looked at the tifeatures code and found that the types above are not included in dbmodel.py: https://github.com/developmentseed/tifeatures/blob/957ae94fbaa2ffabc8ceba9215227abb1e2406aa/tifeatures/dbmodel.py#L24-L31
Proposed solution:
Could we add to that conditional:
        if any(
            [
                pgtype.startswith("int"),
                pgtype.startswith("num"),
                pgtype.startswith("float"),
                pgtype.startswith("double"),
                pgtype.startswith("bigint"),
            ]
        ):
            return "number"

@vincentsarago @bitner let me know what you think of ⬆ - I understand y'all are working on https://github.com/developmentseed/tipg so not sure if this should distract from that.

This may require another issue for t - t is a datetime object and is stored as character varying in the DB table, so this may be an issue of converting / casting that to a datetime during insert. If you all have insight into that, that would be appreciated.

This may require another issue for t - t is a datetime object and is stored as character varying in the DB table, so this may be an issue of converting / casting that to a datetime during insert. If you all have insight into that, that would be appreciated.

There are 2 issues:

issue of converting / casting that to a datetime during insert
in https://docs.ogc.org/DRAFTS/19-079r1.html#filter-queryables type are defined to be only number, array boolean, object or string

As @vincentsarago said, the types that we are listing as the json type for queryables are limited to the basic json data types (number, array, boolean, object, string).
This means we always are dealing with three different typing systems which don't quite overlap perfectly. Python types, PostgreSQL types, and JSON types (which is what we report in Queryables).


Layer parameter input_shape not quite working where input_dim does.

When adding a first layer to Sequential model, it fails with an error if the layer was created with input_shape rather than input_dim.
from keras.models import Sequential
from keras.layers import Dense

# working
model = Sequential()
dl = Dense(32, input_dim=10)
model.add(dl)

# not working
model = Sequential()
dl = Dense(32, input_shape=(None, 10))
model.add(dl)

---------------------------------------------------------------------------
Exception                                 Traceback (most recent call last)
<ipython-input-1-2810ab20c54f> in <module>()
     10 model = Sequential()
     11 dl = Dense(32, input_shape=(None, 10))
---> 12 model.add(dl)

/home/jupyteruser/py35_env/lib/python3.5/site-packages/keras/models.py in add(self, layer)
    274                 else:
    275                     input_dtype = None
--> 276                 layer.create_input_layer(batch_input_shape, input_dtype)
    277
    278             if len(layer.inbound_nodes) != 1:

/home/jupyteruser/py35_env/lib/python3.5/site-packages/keras/engine/topology.py in create_input_layer(self, batch_input_shape,
input_dtype, name)
    368         # and create the node connecting the current layer
    369         # to the input layer we just created.
--> 370         self(x)
    371
    372     def assert_input_compatibility(self, input):

/home/jupyteruser/py35_env/lib/python3.5/site-packages/keras/engine/topology.py in __call__(self, x, mask)
    468             # raise exceptions in case the input is not compatible
    469             # with the input_spec specified in the layer constructor
--> 470             self.assert_input_compatibility(x)
    471
    472             # collect input shapes to build layer

/home/jupyteruser/py35_env/lib/python3.5/site-packages/keras/engine/topology.py in assert_input_compatibility(self, input)
    409                                         self.name + ': expected ndim=' +
    410                                         str(spec.ndim) + ', found ndim=' +
--> 411                                         str(K.ndim(x)))
    412             if spec.dtype is not None:
    413                 if K.dtype(x) != spec.dtype:

Exception: Input 0 is incompatible with layer dense_2: expected ndim=2, found ndim=3

[X] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[X] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

My confusion/mistake:
# working
model = Sequential()
dl = Dense(32, input_shape=(10, ))
model.add(dl)


The queue submit info count may be 0

Change the assertion condition to allow the "submission count == 0" case.

Author jyangsh not on autobuild list. Waiting for curator authorization before starting CI build.


Remove unused custom CSS files and Sphinx directives

No one was using the custom directives galleryitem and customgalleryitem. After removing this, it's safe to remove sphinx-gallery because it's not used. That allows removing gallery.css, which is meant to override sphinx-gallery's default styling.
This also removes two CSS files:

custom.css: There is no .toggle element anymore
style.css: its 3 rules are holdovers from the Read The Docs theme

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.259%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
9143

Relevant Lines:
10478

💛  - Coveralls


Add the GetData method for StreamLayerClient.

Create the GetData method for StreamLayerClient.
Add new Unit tests for GetData method for StreamLayerClient.
Add new integration tests for StreamLayerClient class.
Update test coverage.
Resolves: OLPEDGE-1524
Signed-off-by: Drapak Iryna Angelica<EMAIL_ADDRESS>

Codecov Report

Merging #190 into master will increase coverage by 0.1%.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           master    #190     +/-   ##
========================================
+ Coverage    67.5%   67.6%   +0.1%
========================================
  Files          55      55
  Lines        1470    1475      +5
  Branches      170     171      +1
========================================
+ Hits          993     998      +5
  Misses        436     436
  Partials       41      41

Impacted Files
Coverage Δ

...k-dataservice-read/lib/client/StreamLayerClient.ts
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


docs(module): kueezrtb adapter dev-docs

🏷 Type of documentation

[x] new bid adapter
[ ]

📋 Checklist

[x] Related pull requests in prebid.js or server are linked
[x] For new adapters check submitting your adapter docs

KueezRTB Prebid.js adapter Pull Request:
https://github.com/prebid/Prebid.js/pull/9065

@bretg Thanks. updated the flags.

released with 7.24


IncrementalOperation NullPointerException when dealing with large datasets

When dealing with large datasets, IncrementalOperation randomly throws a NullPointerException.
For some reason, the state obtained from the stateValues variable is null.
ValueState<Map<String, OUT>> state = getRuntimeContext().getState(stateDescriptor);
Map<String, OUT> stateValues = state.value(); //Null sometimes

It seems to be a problem when dealing with more than one key.


ouster: 0.1.3-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository ouster to 0.1.3-1:

upstream repository: https://github.com/CPFL/ouster.git
release repository: https://github.com/CPFL/ouster-release.git
distro file: melodic/distribution.yaml
bloom version: 0.7.2
previous version for package: null

ouster_ros
* Updated LICENSE

Replaced by #20554


Refactors reactor-netty and shows doOnRequestError propagation break

This shows how a span started in reactor-netty's HttpClient cannot
be closed, if an error occurs in doOnRequestError().

@violetagg if you have some time today to dig into this, much appreciated. I'd like to wrap up the reactor-netty client work soon.

fingers crossed..


AttributeError: module 'xdc' has no attribute 'DotDevice'

hello， adamkewley
I am also using Xsens Dot. I tried to script Xsens Dot using the official way of Xsens Dot but failed. Then I happened to see your work，What a lifesaver.
But when I used your code, a little error occurred:
  File "<stdin>", line 1, in <module>
  File "E:\program\Anaconda3\envs\xsensdotConnector\lib\asyncio\base_events.py", line 642, in run_until_complete
    return future.result()
  File "<stdin>", line 4, in run
  AttributeError: module 'xdc' has no attribute 'DotDevice'

I used Anaconda to create a new virtual environment with version 3.9.1 and successfully installed dependencies
My computer system is Windows, and when I run the code, it turns on Bluetooth and Xsens Dot
I was able to execute the following code successfully
>>> import xdc
>>> import asyncio
>>> async def run():
...     dot_bles = await xdc.scan_for_DOT_BLEDevices()
...     for dot_ble in dot_bles:
...         async with xdc.DotDevice(dot_ble) as dot:
...             info = await d.device_info()
...             print(info)
...
>>> loop = asyncio.get_event_loop()

If you have time, I hope you can get your help, and maybe we can work together to make XDC code more robust and help more people
Thank You

@Allwillcome ah, sorry about this, I think the issue here is that the code example in the README uses DotDevice:
# WRONG
import xdc
import asyncio

async def run():
    dot_bles = await xdc.scan_for_DOT_BLEDevices()
    for dot_ble in dot_bles:
        async with xdc.DotDevice(dot_ble) as dot:
            info = await d.device_info()
            print(info)

loop = asyncio.get_event_loop()
loop.run_until_complete(run())

But the implementation file renames it to Dot (here):

async def async_run():
    dots = await scan_for_DOT_BLEDevices()
    for dot in dots:
        async with Dot(dot) as d:
            await d.enable_measurement_action()
            h = ResponseHandler()
            await d.start_notify_medium_payload(h)
            await asyncio.sleep(5.0)

def run():
    loop = asyncio.get_event_loop()
    loop.run_until_complete(async_run())

So, in principle, running xdc.run() should work - I'll look into updating the README accordingly.

Thank you for your reply. I have successfully collected 290 numbers of the four sensors. After collecting 290 numbers, the program stopped automatically again
i=289 t=672898335 x=(0.5923872590065002,), y=(0.3496272563934326,), z=(-0.5528647899627686,)
Traceback (most recent call last):
  File "E:\program\Anaconda3\envs\xsensdotConnector\lib\asyncio\locks.py", line 226, in wait
    await fut
asyncio.exceptions.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "E:\program\Anaconda3\envs\xsensdotConnector\lib\asyncio\tasks.py", line 489, in wait_for
    fut.result()
asyncio.exceptions.CancelledError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "E:\Workspace\xdc\xdc.py", line 347, in run
    loop.run_until_complete(async_run())
  File "E:\program\Anaconda3\envs\xsensdotConnector\lib\asyncio\base_events.py", line 642, in run_until_complete
    return future.result()
  File "E:\Workspace\xdc\xdc.py", line 343, in async_run
    await asyncio.sleep(5.0)
  File "E:\Workspace\xdc\xdc.py", line 299, in __aexit__
    await self.client.__aexit__(exc_type, value, traceback)
  File "E:\program\Anaconda3\envs\xsensdotConnector\lib\site-packages\bleak\backends\client.py", line 65, in __aexit__
    await self.disconnect()
  File "E:\program\Anaconda3\envs\xsensdotConnector\lib\site-packages\bleak\backends\winrt\client.py", line 262, in disconnect
    await asyncio.wait_for(event.wait(), timeout=10)
  File "E:\program\Anaconda3\envs\xsensdotConnector\lib\asyncio\tasks.py", line 491, in wait_for
    raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

Hi @Kris5GJ
This codebase is extremely experimental, so it's no surprise that you are running into problems.
I have updated the README with more example code and added a Q&A section to clarify the design etc., but I don't have much time to develop the codebase robustly - this isn't my main project, at all.
I can't help much with your specific example because you have no error. I'm assuming that the reason you have no error is because you didn't run any actual code? Your example code only contains function definitions, which won't automatically run until you call them, e.g. with:
run()

If there is a specific issue that you'd like me to look into then please open a separate issue ticket, just so that I can clearly see there's something new hanging around. I saw this one only because I'm tagged in it and received an automatic email from GitHub :<


[WARN]agent check service is now critical

I created the simple web api service as below
var options = new ConsulOptions();
options.Host = "198.160.161.XXX";
options.Port = 8500;
options.NameResolution = ConsulNameResolution.HttpApi;
options.NameResolution = ConsulNameResolution.EbayFabio
         var loggerFactory = new LoggerFactory();
        var logger = loggerFactory.CreateLogger("logger");
        var provider = new ConsulProvider(loggerFactory, Options.Create(options));
        Cluster.RegisterService(new Uri($"http://localhost"), provider, "WebApi", "v1", logger);

When i ran the service I am getting following warning in consul
2016/12/07 12:56:05 [INFO] agent: Synced service 'WebApi_localhost_80'
2016/12/07 12:56:05 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:06 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:07 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:08 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:09 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:10 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:11 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:12 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
2016/12/07 12:56:13 [WARN] agent: check 'service:WebApi_localhost_80' is now critical
can someone please guide me on how can i make fix
Thanks,
Vijay

I don't think Consul is dropping the service from the registry automatically like it used to. Should there be a DeRegister method in Microphone too?

Things have changed in Consul. it is now possible to pass a "DeregisterCriticalAfter" parameter when registering Services.
This means that Consul itself will deregister services that have been failing for too long.
Previously, we had such a feature in Microphone, we later removed it as it is not really the responsibility of Microphone itself to remove dead services.
I will add support to pass the auto deregister argument when registering

Hi Rogeralsing
Great library! Thanks you for creating it. Quick question:
Did you add support for DeregisterCriticalAfter? Also is there a way to Deregister the service with you library?
Thanks you again,


Integrating OAuth using Auth0

Hello,
Can you please guide me in integrating ng2-admin app to use OAuth using Auth0?
I am not interested in using the default login page that ships with ng2-admin and instead I would like to use OAuth.
User must login to access any of the pages. I am using a RESTful service that expects a Bearer token.
Can you please guide?
Thanks

Hi,
Most of the authentication is done at backend side (where your REST service stands) and you can use 'passport': http://passportjs.org/
In the front end, you can use a client like 'angular2-jwt' to pass the auth token to the back-end and store it in the local storage in addition to protect your app's route.
Hope this'll help.
Cheers,
Serge.

I forgot to mention that my RESTful services already have authentication built-in using the Authorization header bearer JWT token.
All I need is the following.

Display a login page and allow users to login using OAuth.
Protect all pages and redirect users back to login page if not logged in.

Thanks

This isn't really a project centric issue... but never the less. You need to implement a guard, and attach it to your pages.routing file like so...
  {     path: 'pages',     component: Pages,     canActivate: [AuthGuard],     children: [
Then in your authGuard, you'd have your logic about whether you've actually authenticated or not using Auth0.
Then you should just follow the guide that Auth0 has out for this behavior on logging in / out.
https://auth0.com/docs/libraries/lock/v10
Also, you'll keep the login / register components, you'll just no longer need the ng2-admin html for either of them really.

@Bengejd You are right. I am suggesting that an OAuth integration would be a good feature for the ng2-admin application.
Before posting the question I tried integrating but no luck hence reaching out to see anybody can help me.
Thanks

I doubt the dev team would implement an OAuth integration, it limits the scope of the project, and really forces the user base to stick to "one" authentication implementation.
What do you have against using the default login / registration pages that ng2-admin provides? It fits with the theme, is there, and it's super easy to hook up OAuth to it.

I moved on to ngx-admin and have successfully integrated with Auth0.

@nsankaranarayanan quick question - where did you find the resources to figure out the Auth0 piece?

I moved on to ngx-admin and have successfully integrated with Auth0.

Hi, could you provide us some details about the integration of Auth0 into ngx-admin? Many thanks in  advance.


Change User

I started to play around with this project, everything went smoothly 👍
I then noticed that the Terminal showed "root" as user which I don't really like cause I was deploying it on my own server, not some kind of DigitalOcean server. So I created its own user "coder", defined it in the service file and restarted the service.
I then ran into permission issues (as expected), so I changed the ownership of the "user-data-dir" and of the "code-server" folder itself which solved the main problem (HTTP Response Code 500). I then wanted to check the Console and noticed that "/bin/bash" exits with exit code 1.
In the logs I see that "scandir" also has permission issues of path "/root".
How can I fix this issue, or how can I reconfigure code-server to use the newly created user?
I am running on Ubuntu Server and followed this tutorial but adopted it for my particular installation as I am not using DigitalOcean.

I decided to use Docker instead of installing it to my production server so I have encapsulated it from from my main processes.


txn: remove unnecessary length check in SnapshotStore::batch_get

Signed-off-by: SpadeA-Tang<EMAIL_ADDRESS>
What is changed and how it works?

Issue Number: Close #xxx
What's Changed:

Checking batch length == 1 is what we did when `multi` field of `PointGetter`was not removed and we set 'multi` be false in that case. Now, as `multi` field is removed, it is unnecessary for us to check the length.

Related changes

PR to update pingcap/docs/pingcap/docs-cn:
Need to cherry-pick to the release branch

Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Please add a release note.
If you don't think this PR needs a release note then fill it with None.
If this PR will be picked to release branch, then a release note is probably required.

cc @youjiali1995 @sticnarf

/merge


Add .share to tensor in introduction.ipynb

Description
Update examples/introduction.ipynb to call .share method directly from Torch.tensor.
Closes #71
Affected Dependencies
None
How has this been tested?
Run the whole notebook without errors.
Checklist

[x] I have followed the Contribution Guidelines and Code of Conduct
[ ] I have commented my code following the OpenMined Styleguide
[ ] I have labeled this PR with the relevant Type labels
[ ] My changes are covered by tests

Ahhh -- could you also remove the Session and only pass the parties?
Also, what do you think of having another cell where we showcase the MPCTensor and one cell with the share directly?

Ahhh -- could you also remove the Session and only pass the parties?
Also, what do you think of having another cell where we showcase the MPCTensor and one cell with the share directly?

Sure! I will take a look later

Pushed the branch to be up-to-date with main.

@gmuraru I have included three ways of share a secret:

tensor.share(clients)
tensor.share(session).
MPCTensor(secret, session)

Merging this! I do not know why there are hanging tests on python-tests3.8, but will fix it in the main branch if this is still happening.


[Feature Request] Add entire folder and subfolders

[Note: this is low priority]
Current behavior
To add all the files from a folder, you must open the folder and select them.  For subfolders, you must select all items in their respective subfolders.  This can be very time-consuming.
Requested behavior

Drag-and-drop a folder with multiple files and subfolders
All compatible files appear in the interface where the author can password protect them

Workaround
Use a program like Everything and enter in the directory and extention (e.g. c:\test .xlsx) . Drag-and-drop all found items into the ExcelPass interface.
Potential issues

Users may password-protect a file or folder they didn't mean to
It may make more sense to create a single zip file and then use ExcelPass to create a password for it

I made it possible in version <IP_ADDRESS>

Confirmed.  Tested to a depth of 3 folders with all compatible file types and it worked fine.
Thanks for adding that :)


librife.dylib is Arm64 only

Trying to run this on an Intel mac. I get:
Failed to load /Library/Frameworks/VapourSynth.Framework/lib/vapoursynth/librife.dylib. Error given: dlopen(/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/librife.dylib, 0x0001): tried: '/Library/Frameworks/VapourSynth.framework/lib/vapoursynth/librife.dylib' (mach-o file, but is an incompatible architecture (have 'arm64', need 'x86_64h' or 'x86_64'))
Looks like it's Apple Silicon only. Is there any Intel binary? Or any tip on how to compile for Intel?

Don't have an Intel Mac anymore. You'd have to compile that yourself. Look at how the github workflow does it.

New release.


docs: update usage for crn parser

Description
I was able to publish this to hashicorp: https://registry.terraform.io/modules/terraform-ibm-modules/common-utilities/ibm/latest/submodules/crn-parser
So update the usage to show how to use from hashicorp
Release required?

[x] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

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


CSS problem when deployment

Now I'm trying to deploy my personal website via Vercel. However, there's some deployment issues related to the font style:
Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/style.scss':
17:43:52.997 | Invalid US-ASCII character "\xE2" on line 5
17:43:52.997 | jekyll 3.9.5 | Error:  Invalid US-ASCII character "\xE2" on line 5
Is there some font not support by Vercel or what's the problem for that? Thanks

Can you link to build log that you got the error in?

Closing due to lack of updates.


Networking: prevent a 4.1 instance from being in the same server as a 4.0 instance

4.0 and 4.1 are not compatible for playing.
Don't allow a 4.0 instance to enter a 4.1 server, and don't allow a 4.1 instance to join a 4.0 server.

I found a solution: change the port. Will do right before releasing 4.1


canvas indexing

as seen in https://github.com/blacksmithgu/obsidian-dataview/pull/1803 :)
please let me know what i can add or improve!

I've done some formatting (via yarn run format) and a small amount of code inlining, but otherwise this was great!


Remove unsafe from Buffer::typed_data

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
As pointed out by @jhorstmann  on #921 at https://github.com/apache/arrow-rs/pull/921#discussion_r760086317,
Buffer::typed_data does not actually need to be marked unsafe since it checks the alignment requirements. The very similarly implemented MutableBuffer::typed_data_mut is not marked as unsafe. The safety notes mention bool as a special case, but that is no longer an ArrowNativeType since a while.
https://github.com/apache/arrow-rs/blob/6a6e7f7/arrow/src/buffer/immutable.rs#L160-L181
Describe the solution you'd like

Remove unsafe from Buffer::typed_data
Remove note about bool in docstrings

I reviewed the code a bit more, and the comments make a great point:
    /// `ArrowNativeType` is public so that it can be used as a trait bound for other public
    /// components, such as the `ToByteSlice` trait.  However, this means that it can be
    /// implemented by user defined types, which it is not intended for.

Meaning that if a user implements ArrowNativeType for their types, this will result in undefined behavior.
I also looked more carefully at Buffer and it effectively allows reinterpreting arbitrary bytes as different types, so I am not sure that behavior is safe...
What probably should be done is make MutableBuffer::typed_data unsafe instead as the docs there say very specifically
    /// # Safety
    /// This function must only be used when this buffer was extended with items of type `T`.
    /// Failure to do so results in undefined behavior.

Closing this one as I don't think it is actionable upon further review. FYI @jhorstmann

Ok, I wasn't aware that implementing ArrowNativeType for arbitrary types by a user is a supported usecase. Maybe making that into a sealed trait would also be an option. Anyway, my comment was more about the inconsistency between MutableBuffer::typed_data and Buffer::typed_data, so marking both unsafe is also fine.

Sounds good -- I'll file some follow on tickets.
On Sat, Dec 4, 2021 at 10:35 AM Jörn Horstmann @.***>
wrote:

Ok, I wasn't aware that implementing ArrowNativeType for arbitrary types
by a user is a supported usecase. Maybe making that into a sealed trait
would also be an option. Anyway, my comment was more about the
inconsistency between MutableBuffer::typed_data and Buffer::typed_data,
so marking both unsafe is also fine.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/apache/arrow-rs/issues/996#issuecomment-986046297,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADXZMIHSUGILKQBP7XUE7DUPIYMPANCNFSM5JJ6HAWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Follow on tickets:

https://github.com/apache/arrow-rs/issues/1027
https://github.com/apache/arrow-rs/issues/1028


Payment - handle errors from payment provider better

Description of the bug
If you send some invalid data to the payment provider, it seems that the payment GUI gets stuck instead of showing that something failed, and allowing for retry or clicking "Tilbake".

It would also be good if we allowed TE to inspect any error received from a payment processor and act on it in C# code. Look into returning a result from payment processor that contains some error information.
Acceptance criteria:

[ ] Display that something failed.
[ ] Show the "Betal" button so that retries are possible.
[ ] Show "Tilbake" button if reject is configured.

Steps To Reproduce

Use an app that has payment with Nets Easy configured. For instance: https://ttd.apps.tt02.altinn.no/ttd/payment-test-nets.
Enter an invalid zip code as part of "Søkeren"'s address. For instance 0011.
Enter some goods and services.
Proceed to payment step.
See in the developer console that the API call to pay-action fails, and that GUI gets stuck.

Additional Information
No response

Reported by @caroliss


Add Vue support

I expected to see 'plotAverage' function but extensions says 'Global Scope'

Hey @DTX-92, What extension of Vue do you use?
I tried on Vetur, it seems work.
This extension doesn't provide any symbols provider, you should assume that you have extensions can provide language feature.

@amos402, I didnt use i could use methods like this:
methods: {
  foo() {

  }
}

It helped, thank you!
The problem was with anonymous functions.


Doesnt Work

Hi, im very Interested in This Addon, but it doesnt work for me. On the Server, it doesnt show up.
Do i need an Extra Workshop Addon or Something?

Hi, could you be a little more specific when you say it doesn't work? Since the vendor sells attachments, it requires that the player using it have at least 1 compatible weapon on them.

Yes im sorry,
I Downloaded the Addon and put it in the Addons Folder of the Server. After That i restarted the Server and Tried to find it. I looked at the Entities and pur vendor in the searchbar nur i couldnt find it. So i wenn in the Gun Dealer Job but there i couldnt find ist either. My Problem is, That i Cant find it.
I hope

That's odd. This issue was actually brought to my attention a few months back but I was unable to reproduce it on my end so I just assumed it was a server configuration issue. Would you mind adding me on steam so I can try to diagnose the issue further on your server?

The issue is that the folder name is uppercase. This won't work on Unix systems.
To resolve the issue, you just need to rename the addons folder to be lowercase.

Thank you both for helping me solve this issue. I'll push a fix for it shortly.

I have renamed the repository in lower-case, hopefully this fixes it.


"Request to Add Space Repetitions (SRS) for Phone App - Fleeting Notes"

Feedback: Request to add "space repetitions (SRS)" feature to memorize notes in the Fleeting Notes app on the phone. Emphasizes preference for using the app on the phone.

Summarized feedback from<EMAIL_ADDRESS>
Feedback: Request to add "space repetitions (SRS)" feature to memorize notes in the Fleeting Notes app on the phone. Emphasizes preference for using the app on the phone.

Summarized feedback from<EMAIL_ADDRESS>
The user suggests adding a spaced repetition (SRS) feature to Fleeting Notes for memorizing notes.


fixed typo

Just trying out the pull request functionality of github. fixing something :)

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


all: drop support for macOS 10.10 at some point

Eventually we'll drop support for macOS 10.10.
This bug collects TODO items for when we do so.
/cc @aclements

https://go-review.googlesource.com/c/go/+/125304/3/misc/cgo/test/issue24161_darwin_test.go for #26475


OpenSSL Not Detected

Debian Testing (11), openssl 1.1.1i-1 is installed (normal and dev packages)
The makefile says that it can't find any suitable SSL library, it doesn't give any helpful info beyond that (is there a way to get the makefile to be noisier?)
Building with cmake includes a fio_tls_openssl.o file in the archive, so I assume that it works correctly there.

Hi @tekktonic ,
Thank you for opening this issue and for your interest win facil.io.
The TLS/SSL verification tests attempts to compile and run a small piece of C code in the make file. If you have OpenSSL 1.1.x and this fails that the most likely explanation is that OpenSSL is missing from either LIBRARY_PATH (library files) or CPATH (header / include files).
If you use pkg-config, these locations *should be added automatically by the makefile - but I don't have pkg-config, so I don't remember testing this codepath (it's there for my linux machine, but I think OpenSSL is in the LIBRARY_PATH on that one)...
... You can review the final CFLAGS and LINKER_FLAGS values using make vars.
If this doesn't help, you can  get a more detailed error message by erasing the error print redirection in the makefile's test functions by deleting the 2> /dev/null on lines 199-200 of the makefile.
Good luck! And if you discover anything that would be fun to incorporate, please let me know.
Kindly,
Boaz.

Well that was a pretty quick find. gcc can be picky about the order of ldflags. This diff fixes it:
diff --git a/makefile b/makefile
index 3fbcfcf4..5913c00d 100644
--- a/makefile
+++ b/makefile
@@ -196,7 +196,7 @@ OBJS_DEPENDENCY:=$(LIB_OBJS:.o=.d) $(MAIN_OBJS:.o=.d)
 # TRY_COMPILE_AND_RUN returns the program's shell code as string.
 #############################################################################

-TRY_COMPILE=$(shell printf $(1) | $(CC) $(INCLUDE_STR) $(LDFLAGS) $(2) -xc -o /dev/null - >> /dev/null 2> /dev/null ; echo $$? 2> /dev/null)
+TRY_COMPILE=$(shell printf $(1) | $(CC) $(INCLUDE_STR) -xc -o /dev/null - $(2) $(LDFLAGS) >> /dev/null 2> /dev/null ; echo $$? 2> /dev/null)
 TRY_COMPILE_AND_RUN=$(shell printf $(1) | $(CC) $(2) -xc -o ./___fio_tmp_test_ - 2> /dev/null ; ./___fio_tmp_test_ >> /dev/null 2> /dev/null; echo $$?; rm ./___fio_tmp_test_ 2> /dev/null)
 EMPTY:=

I can open it as a pr if you prefer, I just didn't want to go through the trouble of forking, applying the change on my fork, and opening it when the diff is trivial.

Thanks! I'll add this in :)

Sure thing! I realized after I commented that I missed the line below, so make sure you grab the version now (2 lines changed) :)


Support ARM/Aarch64 TLS register fastpath

Tested with Ubuntu Linux 18.04 LTS running on Marvell/Cavium ThunderX,
which consists of Armv8 based processors.

Thanks so much! I will merge it in

btw. should "asm volatile" be "asm" as on the other platforms?


Beta 2.026 released

https://orteil.dashnet.org/cookieclicker/beta/
The CM beta script looks for version 2.016.

Thanks for the heads up.  I will need to make time for the eventual release to non beta.  I don't usually update the beta script until it's been stuck in beta for a while, since any changes I make can be changed again by Orteil.  So I usually wait.

Would it still work in beta just not do anything for new stuff or would it completely break

Since I never got around to updating the beta to current, I'm pretty sure it will break.  A better option is the current live script, but no guarantee it will not break since I don't know what changes have been made.  Bottom line, try any at your own risk, but I'm pretty sure both won't affect your save file.

So far, using the release version script seems to work with the latest beta.
// ==UserScript==
// @name Cookie Monster Beta
// @namespace Cookie
// @include http://orteil.dashnet.org/cookieclicker/beta/
// @include https://orteil.dashnet.org/cookieclicker/beta/
// @version 1
// @grant none
// ==/UserScript==

var code = "(" + (function() {
    var checkReady = setInterval(function() {
        if (typeof Game.ready !== 'undefined' && Game.ready) {
            Game.LoadMod('https://aktanusa.github.io/CookieMonster/CookieMonster.js');
            clearInterval(checkReady);
        }
    }, 1000);
}).toString() + ")()";

window.eval(code);

Thanks for the heads up!


PyPI release pulls numpy 2.0.0rc1 for python 3.12

Hi folks,
I'm seeing something a bit strange on geocat-comp logs. For python 3.12 only, cftime seems to be pulling the numpy release candidate by default.
From https://github.com/NCAR/geocat-comp/issues/598:

For python 3.11, cftime pulls numpy>1.13.3 (log)
Collecting numpy>1.13.3 (from cftime->geocat-comp)
Downloading numpy-1.26.4-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (61 kB)

For python 3.12, though (log):
Collecting numpy>=1.26.0b1 (from cftime->geocat-comp)
Downloading numpy-2.0.0rc1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (60 kB)

Pip should not install a pre-release candidate without explicitly asked to. Maybe you are hitting this issue: https://github.com/pypa/pip/issues/7579

Right, but the workflow of our actions haven't changed.
Locally (mac-os) on a fresh environment, here's what I see.
(base) ➜  ~ conda create -n temp-cftime python=3.12
Retrieving notices: ...working... done
Channels:
 - conda-forge
 - defaults
Platform: osx-arm64
Collecting package metadata (repodata.json): done
Solving environment: done

==> WARNING: A newer version of conda exists. <==
    current version: 24.1.1
    latest version: 24.3.0

Please update conda by running

    $ conda update -n base -c conda-forge conda

## Package Plan ##

  environment location: /Users/anissaz/miniconda3/envs/temp-cftime

  added / updated specs:
    - python=3.12

The following packages will be downloaded:

    package                    |            build
    ---------------------------|-----------------
    libsqlite-3.45.3           |       h091b4b1_0         805 KB  conda-forge
    ------------------------------------------------------------
                                           Total:         805 KB

The following NEW packages will be INSTALLED:

  bzip2              conda-forge/osx-arm64::bzip2-1.0.8-h93a5062_5
  ca-certificates    conda-forge/osx-arm64::ca-certificates-2024.2.2-hf0a4a13_0
  libexpat           conda-forge/osx-arm64::libexpat-2.6.2-hebf3989_0
  libffi             conda-forge/osx-arm64::libffi-3.4.2-h3422bc3_5
  libsqlite          conda-forge/osx-arm64::libsqlite-3.45.3-h091b4b1_0
  libzlib            conda-forge/osx-arm64::libzlib-1.2.13-h53f4e23_5
  ncurses            conda-forge/osx-arm64::ncurses-6.4.20240210-h078ce10_0
  openssl            conda-forge/osx-arm64::openssl-3.2.1-h0d3ecfb_1
  pip                conda-forge/noarch::pip-24.0-pyhd8ed1ab_0
  python             conda-forge/osx-arm64::python-3.12.3-h4a7b5fc_0_cpython
  readline           conda-forge/osx-arm64::readline-8.2-h92ec313_1
  setuptools         conda-forge/noarch::setuptools-69.5.1-pyhd8ed1ab_0
  tk                 conda-forge/osx-arm64::tk-8.6.13-h5083fa2_1
  tzdata             conda-forge/noarch::tzdata-2024a-h0c530f3_0
  wheel              conda-forge/noarch::wheel-0.43.0-pyhd8ed1ab_1
  xz                 conda-forge/osx-arm64::xz-5.2.6-h57fd34a_0

Proceed ([y]/n)?

Downloading and Extracting Packages:

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
#     $ conda activate temp-cftime
#
# To deactivate an active environment, use
#
#     $ conda deactivate

(base) ➜  ~ conda activate temp-cftime
(temp-cftime) ➜  ~ pip install cftime
Collecting cftime
  Using cached cftime-1.6.3-cp312-cp312-macosx_11_0_arm64.whl.metadata (8.6 kB)
Collecting numpy>=1.26.0b1 (from cftime)
  Downloading numpy-2.0.0rc1-cp312-cp312-macosx_14_0_arm64.whl.metadata (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.9/60.9 kB 580.7 kB/s eta 0:00:00
Using cached cftime-1.6.3-cp312-cp312-macosx_11_0_arm64.whl (221 kB)
Downloading numpy-2.0.0rc1-cp312-cp312-macosx_14_0_arm64.whl (5.0 MB)
   ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5.0/5.0 MB 457.8 kB/s eta 0:00:00
Installing collected packages: numpy, cftime
Successfully installed cftime-1.6.3 numpy-2.0.0rc1

Right, but the workflow of our actions haven't changed.

Yep. That is why I believe you are hitting that bug I mentioned above.


Fix table ref warn

What Was Changed

Finally fixing some console pollution I introduced back when we added sticky columns to <TableModule />
We now only show the 'Table doesn't have a ref...' warning if some sticky columns are set

This will also prevent unnecessary spacing calculations being run when there are no sticky cols

We also now only show this warning in Dev

Screenshots
Before
This warning appeared for every table on every page that did not have a ref, regardless of whether it needed sticky cols

After
Now nothing should appear for non-sticky tables, or in Prod

Finally fixing some console pollution I introduced back when we added sticky columns to

So you're the celebrity that introduced sticky columns! I've been enjoying that feature in our Patient ML Runs table.

Finally fixing some console pollution I introduced back when we added sticky columns to

So you're the celebrity that introduced sticky columns! I've been enjoying that feature in our Patient ML Runs table.

Yay! Glad to hear it's been helpful! ✨✨✨


add arabic translation

This needs to be compiled to a mo file

This needs to be compiled to a mo file

Just added that. Thanks


improved GitHub diff link against main instead of master

Do not merge. See https://github.com/dry-rb/dry-auto_inject/pull/87


Update README.md

Removed wrong words and prepositions leading to non-clarity of the readme.

Thanks you sir to your feedback. According to brainchop contribution rules, contributions are allowed to code only with new functionalities or enhancements.  Please refer the section typos here in discussion board  for any typos correction: https://github.com/neuroneural/brainchop/discussions/categories/typos.


Update to 5.9.3

https://github.com/TryGhost/Ghost/releases/tag/v5.9.2
https://github.com/TryGhost/Ghost/releases/tag/v5.9.3

Done by docker-library-bot :)


Support ARM on MacOS

Hi, love the package!
Julia recently started supporting the ARM architecture on MacOS, which is used by the M1 chippie. It would be great if this package could be used on that architecture!
Thank you!
-fons

You're welcome!
Ah looks like micromamba is already built for ARM I just missed it off the list.
You should be able to use it by doing
import MicroMamba
MicroMamba.STATE.platform="osx-arm64"

Can you verify that works? Also what is Sys.ARCH on an ARM?

Pretty sure Sys.ARCH == :aarch64?

I have no idea why, but it's already working...
➜  ~ julia
               _
   _       _ _(_)_     |  Documentation: https://docs.julialang.org
  (_)     | (_) (_)    |
   _ _   _| |_  __ _   |  Type "?" for help, "]?" for Pkg help.
  | | | | | | |/ _` |  |
  | | |_| | | | (_| |  |  Version 1.7.1 (2021-12-22)
 _/ |\__'_|_|_|\__'_|  |  Official https://julialang.org/ release
|__/                   |

(@v1.7) pkg> activate --temp
  Activating new project at `/var/folders/v_/fhpj9jn151d4p9c2fdw2gv780000gn/T/jl_C1lDWS`

(jl_C1lDWS) pkg> add MicroMamba
    Updating registry at `~/.julia/registries/General.toml`
   Resolving package versions...
    Updating `/private/var/folders/v_/fhpj9jn151d4p9c2fdw2gv780000gn/T/jl_C1lDWS/Project.toml`
  [0b3b1443] + MicroMamba v0.1.3
    Updating `/private/var/folders/v_/fhpj9jn151d4p9c2fdw2gv780000gn/T/jl_C1lDWS/Manifest.toml`
  [523fee87] + CodecBzip2 v0.7.2
  [692b3bcd] + JLLWrappers v1.4.0
  [0b3b1443] + MicroMamba v0.1.3
  [21216c6a] + Preferences v1.2.3
  [6c6a2e73] + Scratch v1.1.0
  [3bb67fe8] + TranscodingStreams v0.9.6
  [6e34b625] + Bzip2_jll v1.0.8+0
  [0dad84c5] + ArgTools
  [56f22d72] + Artifacts
  [2a0f44e3] + Base64
  [ade2ca70] + Dates
  [f43a241f] + Downloads
  [b77e0a4c] + InteractiveUtils
  [b27032c2] + LibCURL
  [76f85450] + LibGit2
  [8f399da3] + Libdl
  [56ddb016] + Logging
  [d6f4376e] + Markdown
  [ca575930] + NetworkOptions
  [44cfe95a] + Pkg
  [de0858da] + Printf
  [3fa0cd96] + REPL
  [9a3f8284] + Random
  [ea8e919c] + SHA
  [9e88b42a] + Serialization
  [6462fe0b] + Sockets
  [fa267f1f] + TOML
  [a4e569a6] + Tar
  [8dfed614] + Test
  [cf7118a7] + UUIDs
  [4ec0a83e] + Unicode
  [deac9b47] + LibCURL_jll
  [29816b5a] + LibSSH2_jll
  [c8ffd9c3] + MbedTLS_jll
  [14a3606d] + MozillaCACerts_jll
  [83775a58] + Zlib_jll
  [8e850ede] + nghttp2_jll
  [3f19e933] + p7zip_jll

julia> import MicroMamba

julia> run(MicroMamba.cmd(`--version`))
micromamba: 0.19.1
libmamba: 0.19.1
Process(`/Users/fons/.julia/scratchspaces/0b3b1443-0f03-428d-bdfb-f27f9c1191ea/install/micromamba -r /Users/fons/.julia/scratchspaces/0b3b1443-0f03-428d-bdfb-f27f9c1191ea/root --version`, ProcessExited(0))

julia> Sys.ARCH
:aarch64

Looks like MicroMamba was already installed. Did you already do the trick above? Or maybe you already got the x86 version?
Anyway that's enough info to implement the osx-arm64 case thanks.

The main branch now uses artifacts, and I included osx-arm64 so it should work there now. I'm about to make a release.


Coloring ignored files feature request

I use .gitignore and .dockerignore file in the same project.
The file names defined in both files are colored gray on the project window view,
however, I would like the only files in .gitignore to be colored because I cannot determine that a gray file is ignored by git or docker.
So I would appreciate it if we are able to enable/disable the coloring feature for each .XXXXignore file.

@otsuka This feature is already implemented.
Please go to the Settings > Version Control > Ignore Files Support and uncheck the specific file type (Docker in your case) in Enable ignoring column.

@hsz
Thank you for your support! 👍


Models for database

Fixes Issue
fixes #105

Created Models for database
Changed prisma.js to typescript and improvements

Changes proposed

Note to reviewers

Screenshots

I think we can merge it as the schema model is looking good right now. we will wait till one more review then merge it great job @leewan-09 🚀🚀


Removal of test coverage badge from README.md

When faster builds with ESBuild was introduced in #797, this also removed test coverage reporting instrumentation, causing code coverage to be reported as 100% (#795). While it may be possible to reintroduce that functionality, it would negate much of the performance benefits of the build tooling change. And while test coverage itself is great, these metrics are not always very useful in determining the quality of coverage, or the level of risk where coverage is low.
The root cause was discovered in the course of work on #798, wherein upgrades also caused generating the badge itself to fail. In discussion with @lognaturel we concluded that the badge likely doesn't provide enough value to justify blocking other important changes. A similar change is pending in enketo/enketo-express#298, and a similar issue will be opened there. I'm opening this issue to make this change known more visibly and to get an idea whether there's a major objection to the change.

It's been gone for a while and no one seems to mind. We can run with coverage locally and we carefully review tests as part of code review.


Upgrading ember-cli and removing bower

Also added the command to run node-tests in CI which was not running all along.
@rwjblue

@Turbo87 Yes am aware of that. Most of it comes from updating ember-cli. Do you suggest doing these changes differently?

I personally always feel very uncomfortable merging PRs with many independent changes as it makes finding bugs infinitely harder when using something like git bisect.
IMHO splitting up the PR would be best, possibly in the steps that you mentioned in the PR description. I'd start with the CI change, then drop Node 4 and then continue from there.

The first one landed in @turbo87’s recent PR merging. Next up is bower support...

Sounds Good! Created a separate PR to remove bower and to run node-tests in CI. Had to club these 2 in a single PR since running node-tests in CI was dependent on removing bower. Also running node-tests while removing bower will make sure that things work fine.
I will use this PR to upgrade ember-cli alone.


reasons why my dementia hasn’t affected me as a person

fire

fire

Ok now I’m actually curious what would that even affect


"Reopen in WSL" option missing

Type: Bug

Click the >< arrows in the bottom left.
The option to "Reopen in WSL" is missing, but when running in WSL "Reopen in Windows" does appear. Only "Connect to WSL" is there, but that doesn't open the same workspace you're in already.

It's inconvenient to then have to then go and find and open the workspace once in WSL.
 You can still find Reopen Folder in WSL in the command palette

duplicate of https://github.com/microsoft/vscode/issues/176073

It's the only WSL option from all of those that's of any use to me. This is a really confusing decision.

To me too. This really does not make any sense because if we are on WSL remote and we click on it, it's show Reopen Folder on Windows. So, if we are on Windows why it not show Reopen Folder on WSL.

Yes, we decided to slim down the remote menu. You can still find Reopen Folder in WSL in the command palette

It's inconsistent then, If the intention was to sim down the remote menu, the Reopen Folder on Windows option should be removed too. But the WSL: Reopen Folder in WSL is an option I use a lot but I would prefer it in the remote menu, if possible of course. Thanks.


error on backend (net/http: timeout awaiting response headers)

Report
I am using http-add-on and creating a HTTPScaledObject successfully. The scaled deployment scales down to 0 at first. And once I curl the http-interceptor-proxy via ingress, it reported an error:
error on backend (net/http: timeout awaiting response headers)
but the container is scaled up to 1 successfully.
The weird thing is that, only the first curl will report this error, and other tries after the first curl can work well.
I tried several times, and every first curl (when the pod needs to activate from 0 to 1) will fail, while other curls after that can success.
Expected Behavior
STATUS 200 and obtain http content from the deployment
Actual Behavior
every first curl (when the pod needs to activate from 0 to 1) will fail, while other curls after that can success.
Steps to Reproduce the Problem

helm install http-add-on kedacore/keda-add-ons-http
kubectl apply -f httpscaledobject.yaml (depolyment image is "tomcat:8.0.18-jre8")
helm install ingress-nginx ingress-nginx/ingress-nginx
create an ingress and point to keda-add-ons-http-interceptor-proxy service
curl -H "Host: myhost.com"

NOTE: this error appears every time when the pod needs to activate from 0 to 1. It won't appear if the pod already has 1 replica.
Logs from KEDA HTTP operator
example

What version of the KEDA HTTP Addon are you running?
0.3.0
Kubernetes Version
No response
Platform
No response
Anything else?
No response

It commonly takes a long time for a workload to start up for the first time (i.e., from 0 to 1 replica), a process called cold start. This is probably the issue you are facing.
Perhaps you can try to solve this problem by adjusting the timeout-related parameters. Such as this parameter: https://github.com/kedacore/http-add-on/blob/v0.3.0/interceptor/config/timeouts.go#L18

Perhaps you can try to solve this problem by adjusting the timeout-related parameters. Such as this parameter: https://github.com/kedacore/http-add-on/blob/v0.3.0/interceptor/config/timeouts.go#L18

@tpiperatgod thx for your reply.
I tried to set the responseHeaderTimeout when I installed the keda-http-on :
helm install http-add-on kedacore/keda-add-ons-http --set responseHeaderTimeout=5s
Then I re-start the whole process again. This time when I curl the ingress controller for the first time, it errored again:
error on backend (net/http: timeout awaiting response headers)
And it absolutely didn't wait for 5 seconds. It just directly return this error within like 100ms.
Did I set the timeout right? or I have to set it in codes and re-build the interceptor?

Hi, @JieDing You can find these parameters in the deployment's configuration:
$ kubectl get deployments.apps -n ${NAMESPACE} keda-add-ons-http-interceptor -oyaml
...
    spec:
      containers:
      - env:
        - name: KEDA_HTTP_ROUTING_TABLE_UPDATE_DURATION_MS
          value: "500"
        - name: KEDA_HTTP_CURRENT_NAMESPACE
          value: keda
        - name: KEDA_HTTP_PROXY_PORT
          value: "8080"
        - name: KEDA_HTTP_ADMIN_PORT
          value: "9090"
        - name: KEDA_HTTP_CONNECT_TIMEOUT
          value: 500ms
        - name: KEDA_HTTP_KEEP_ALIVE
          value: 1s
        - name: KEDA_RESPONSE_HEADER_TIMEOUT
          value: 500ms
        - name: KEDA_CONDITION_WAIT_TIMEOUT
          value: 20s
        - name: KEDA_HTTP_DEPLOYMENT_CACHE_POLLING_INTERVAL_MS
          value: "250"
        - name: KEDA_HTTP_FORCE_HTTP2
          value: "false"
        - name: KEDA_HTTP_MAX_IDLE_CONNS
          value: "100"
        - name: KEDA_HTTP_IDLE_CONN_TIMEOUT
          value: 90s
        - name: KEDA_HTTP_TLS_HANDSHAKE_TIMEOUT
          value: 10s
        - name: KEDA_HTTP_EXPECT_CONTINUE_TIMEOUT
          value: 1s
...

Use the kubectl edit command to modify them directly to take effect.
But I didn't reproduce the problem...🥲 So I'm not really sure if these parameters are relevant to the problem you are facing.
Perhaps you could post the configuration of all the deployments of keda-add-ons-http-*

@tpiperatgod That does work dude! Thx so much for your patient help.

thanks @tpiperatgod !