Strange hard wrapping in base scope document

Why do you use hard wrapping in markdown documents at all?
If hardwrapping is used, shouldn't it wrap at something common like 80 chars rather than 40?

See https://github.com/SublimeText/ScopeNamingGuidelines/blob/9f8837af966e47cc39f2da25c177d634cf221341/CONTRIBUTING.md#style. I use this style in all my text-based projects, notably for documentation, and it makes version control much simpler when sentences are broken at semantic break points rather than arbitrary column widths.

See https://github.com/SublimeText/ScopeNamingGuidelines/blob/9f8837af966e47cc39f2da25c177d634cf221341/CONTRIBUTING.md#style. I use this style in all my text-based projects, notably for documentation, and it makes version control much simpler when sentences are broken at semantic break points rather than arbitrary column widths.

I can remember heavy critics when I used to hard wrap markdown files in GitGutter's documentation several years ago about that not being a good style.

I can remember heavy critics when I used to hard wrap markdown files in GitGutter's documentation several years ago about that not being a good style.

Opinions may differ on this, although I haven't come to see any strong arguments for not using semantic linefeeds. I can only think of text being slightly easier to read if the lines are longer and justified, but that is arguably subjective since people probably consider sentences to have pauses at slightly different places and some may prefer shorter lines in general.
Since I initiated this repository, I get to choose the style. 🙂 I'm open for debates on this, but so far I haven't had much of an opposition. It might also just be something that you need to try out first before you can judge properly.

Opinions may differ on this, although I haven't come to see any strong arguments for not using semantic linefeeds. I can only think of text being slightly easier to read if the lines are longer and justified, but that is arguably subjective since people probably consider sentences to have pauses at slightly different places and some may prefer shorter lines in general.
Since I initiated this repository, I get to choose the style. 🙂 I'm open for debates on this, but so far I haven't had much of an opposition. It might also just be something that you need to try out first before you can judge properly.

It's indeed the first time I ever have seen such a style in markdown files. The arguments for it sound more logical to use than hard wrapped lines at a certain column, with regards to reworking/updateing texts. It looks a bit like poetry this way.

It's indeed the first time I ever have seen such a style in markdown files. The arguments for it sound more logical to use than hard wrapped lines at a certain column, with regards to reworking/updateing texts. It looks a bit like poetry this way.


feat: add takumin/gjson

takumin/gjson: Golang JSON Tool
$ aqua g -i takumin/gjson

Thank you always!

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.66.0


How to install IF# kernel for Jupyter Notebook?

Does IF# work with Jupyter Notebook? And how to install?
I use Linux, by the way.

Currently, this branch works very nicely on Linux and Jupyter 4.0
https://github.com/BayardRock/IfSharp/pull/47
Once you have compiled it, run the ifsharp.exe once to set up the config files.
Then to use it run "jupyter notebook --config ~/.local/share/jupyter/kernels/ifsharp/ipython_config.py"
The paths are probably not set up properly so you have to add lines like
#I "/usr/lib/cli/FSharp.Data.TypeProviders-4.3/"
#I "/path/to/ifsharp/IfSharp/bin"
#r "IfSharp.Kernel.dll"
to each notebook or fsx file.
The built in plotting doesn't work, you have to use a more uptodate version of FSLab.

@npmurphy added documentation on the Jupyter branch here: https://github.com/fsprojects/IfSharp/tree/jupyter
I'm going to go ahead and close this, please do raise any issues you have with this or improvements to the documentation.


unitless properties

like react, the following should both 'work' without 'px -
let cls = css` font-size: 20 `
let cls = css` font-size: ${myVar} `

as a counter argument - maybe it's good not to rely on the magic addition of px? at least it would be in line with how css works.
also in react px is only appended for numbers. if you pass in a string it doesn't get added.

I definitely prefer the addition, I'm not particularly interested in purity.
Aware of the second issue, have an idea to solve it.

some further detail - because we use css vars, you can't directly concatenate 'px' when interpolating, like -
let cls = css` font-size: ${myVar}px `

the react-ish way is really nice, and backs glamor as well.


Append -buildkite to build ids from buildkite builds (for now.)

We're clobbering the old build/test builds, which has caused confusion when diagnosing a bad build-related issue.

Build has succeeded (tests will fail), and I've visually confirmed that the build files all had -buildkite appended to them.


[Request]

Update to 1.10.2 or if it's already fully compatible, let it show on curse for compatible versions.

It works in 1.10 as long as you don't actuallyt try to use the items, cause then you crash XD

This mod is not currently compatible for 1.10, loads but I get some opengl errors in chat window, all black and very glitchy.  Please update!

I apologize for being so lazy for so long. I've finally ported to 1.10.2.


Incldue  serial numbers in Open Bible Stories as in the website.

In the website, there are numbers for the Bible Stories.
Also when you select a story, the number is in the content page  also.

Serial numbers are now included as in the website for Bible stories.


Could you release a new one for Ruby 2.4?

Yes. I'm going to cut 1.7.1 security release this weekend first; and then
we have a lot of great stuff that will go into a 1.8.0 release, including
ruby 2.4 support.

Could you release a new one for Ruby 2.4?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1618, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAAgDzlRbsGahLr-uPDp5TzW1HkUJ9WUks5rm8k0gaJpZM4MhZSl
.

👍

At the moment, we have inconsistent dependency definitions across the different nokogiri 1.7.1 flavors. The standard version supports ruby 2.4+ while version 1.7.1-x64-mingw32 states that it does not support it.

@obfuscoder We obviously know this. :-) Are you offering to help out?

I suppose just rebuilding and publishing 1.7.1-x64-mingw32 with the restriction removed is not an option? What is to be done apart from removing the restriction for the next version? Any compile issues?

Everything is prepared on the master branch for ruby(installer)-2.4. The ruby version restrictions are correct how they are. @flavorjones can find some time to release nokogiri-1.8.0 ?

Yup, will release 1.8.0 hopefully this weekend. I wanted to address the other issues in the 1.8.0 milestone, but I may just push them out if I can't get to them.

This is indirectly related to the issue, but to hopefully save someone else the struggle - this seems to affect Chef 13 on Windows, likely because Chef 13 [client] omnibus installs Ruby 2.4.1. (Chef 12 is fine.)
Unfortunately, the failure is buried a few layers deep. A recipe has a run-time failure that it can't process a nil value. The value was supposed to have been provided by a custom ohai plugin that depends on nokogiri. By executing the ohai plugin directly on the test system with debug level logging, you can see that the nokogiri gem isn't being loaded. (This is only visible by running ohai with debug logging on.) From there, it's only when you tell a recipe to explicitly install the nokogiri gem that you see the underlying issue:
Error executing action `install` on resource 'chef_gem[nokogiri]'

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of C:/opscode/chef/embedded/bin/gem install nokogiri -q --no-rdoc --no-ri -v "1.7.2" --source=https://www.rubygems.org ----
STDOUT:
STDERR: ERROR:  Error installing nokogiri:
nokogiri requires Ruby version < 2.4, >= 1.9.2.

@rjhornsby The Chef maintainers are working on this in our installers, stay tuned.

@rjhornsby that isn't indirectly related to this issue, that is precisely this issue.
Since nokogiri is an optional add-on to the chef client (it isn't necessary for anything at all inside chef client itself) in order to ship 13.0 I removed nokogiri from the windows builds.  That unblocked us from shipping ruby-2.4.1 which was a business requirement to ship Chef 13.0 on.
For ChefDK 2.0 we need nokogiri for the bundled software, so I've created an omnibus definition for nokogiri which checks it out from git and builds it against our own mingw2 windows build environment (with our libxml2 and libxslt) so that we can ship nokogiri 1.7.x on ruby 2.4.1 on windows.  But that development effort happened after Chef 13.0 shipped.  Likely ChefDK 2.0 will land with nokogiri in windows and that'll have Chef 13.1 but which will still not ship with nokogiri.  Eventually we'll ship Chef 13.2 which will have nokogiri baked into it one way or another (either this issue gets closed and we just pick up the released fat gem, or we'll backport the ChefDK 2.0 software definition to Chef 13.2 to get it in there).
TL;DR:  If you need nokogiri on Chef 13 on windows this issue is a hard blocker.  If Chef 13.2 gets released first, then that will also unblock you.

@flavorjones Has this been resolved with the release of 1.7.2? I installed 1.7.2 on Windows with gem 'nokogiri', '~>1.7.2' and get the following error:
Gem::InstallError: nokogiri requires Ruby version < 2.4, >= 2.1.0

I have Ruby 2.4.1p111 (2017-03-22 revision 58053) [x64-mingw32] and the version of nokogiri fetched was etching nokogiri 1.7.2 (x64-mingw32).

@djam90 The fix/update is anticipated with the release of 1.8.0

Good day everyone. I am new to Rails.. i tried to create a new rails app via the command line and it get the error below
Gem::InstallError: nokogiri requires Ruby version < 2.4, >= 2.1.0.
An error occurred while installing nokogiri (1.7.2), and Bundler cannot
continue.
Make sure that gem install nokogiri -v '1.7.2' succeeds before bundling.
Below is my environment
C:\Windows\System32>ruby -v
ruby 2.4.1p111 (2017-03-22 revision 58053) [x64-mingw32]
C:\Windows\System32>rails -v
Rails 5.1.1
Thank you in advance

When nokogiri 1.8.0 is relaesed?
If it still takes time, can I release 1.7.3 to support 2.4.1 fat gem?
I have a commit bit to GitHub repo but don't have rubygems push privilege.

1.7.3 that was simply 1.7.2 with fat gem support for windows on ruby-2.4 would be lovely

Hi , When will a version of nokogiri that supports ruby 2.4 on windows be released ? Another question , I'm new to ruby development. I would like to learn how to modify nokogiri code so as to make it compatible with ruby 2.4 for instance. How should I go to do it ?

Done. Shipped in Nokogiri 1.8.0.

thanks!

thanks. was installing twitter bootstrap website on local machine. nokogiri 1.8.0 worked


Survey Listview UI Update

Hi everyone , its almost been a week since I started working on Survey app for the issue https://github.com/odk-x/tool-suite-X/issues/154  and I'm enjoying working on it , It's just my proposal idea about the listview that contains forms :

It can be modified a bit by adding padding and backgrounds , this is just something I just worked upon , its totally my own interest.

The textsize of  textview containing the "last update date and time" can be made little smaller as compared to others as its less important than Title and TableID

The TextView containing "Select the form to open" can be removed and in place of that Arrows indicating "open forms" can be placed

Arrow  will also prevent mistakes likes : accidental opening of form, So Instead of opening from by clicking on it , It can be opened by an "Arrow" .
Please let me know if any of these changes can be made .

The PMC/TSC would need to discuss at our next meeting. We met before you submitted this issue (April 27(. The next meeting is May 11.

Yeah , Sure , Thankyou for the review.


As a member, I should be able to see other member's public feedback

Pending review of consultation feedback.
When viewing another member's profile, any feedback that is public should be visible.
There should be an option of disabling public feedback entirely.  It should not be possible to select feedback to display.

We have decided not to implement public feedback due the the possibility of it being abused. If this is requested by members or DSG later on, we can look at an appropriate implementation


Apply genrule-setup.sh to Starlark shell actions

This is a proposal to have the custom initialization hook for genrules also apply to Starlark shell actions.
Initial PR for draft.

Comments copied from pre-markdown version:

laurentlb@: What about changing the shell?
We keep the command "shell -c ‘<cmd>’", but shell is free to execute its argument the way it wants?
brandjon@: Then we'd need a wrapper script around the shell -- an alternative shell toolchain, no? Not sure what the benefit is.
laurentlb@: This means that Bazel doesn't need to know/care about it.

Also:

laurentlb@: This assumes that the shell knows about "source". I'm not sure what happens on Windows, but it's better to reduce the number of assumptions about the shell behavior.

Can you take the bit of functionality you are working towards and make it apply in a sh-less environment on Windows? Perhaps failfast is a setting on the genrule (with a default in the global workspace config). The executor then can add the right flags for bash or cmd.exe.

This assumes that the shell knows about "source". I'm not sure what happens on Windows, but it's better to reduce the number of assumptions about the shell behavior.

It seems that we do assume the shell is Bash or Bash-compatible, so hopefully set/source will work even on Windows.

What about changing the shell?

If we make the existing shell strict, that'll affect all genrules and Starlark shell actions (and maybe other things too). If we add an alternative shell tool, and allow genrules and Starlark shell actions to choose the tool via an attribute/param, then we still are making Bazel know about shell strictness, so we may as well implement it using a single underlying tool. If we do an incompatible change to make all Starlark shell actions use the strict tool, then maybe you can argue it's cleaner to not have SkylarkActionFactory know about set/source, but I think you pay the extra cost of having a wrapper script.

make it apply in a sh-less environment on Windows

Is Windows now, or will it be, sh-less? If so, what are genrule and run_shell() going to do?

Separate from how we factor strictness between run_shell() and the toolchain, there's the issue of whether or not expanding the hook for customizing shell initialization is the Right Thing To Do. Maybe we don't want to let repo owners declare arbitrary custom semantics for run_shell() -- i.e., maybe genrules-setup.sh was a mistake.
We could still get sandboxing support for remote execution platforms without genrule-setup.sh, by having those platforms provide their own shell toolchain, which would be selected in place of the default.

cc @laszlocsomor @meteorcloudy

also, cc @philwo

The plan on Windows is to make Bazel sh-less. For genrule, people can choose to use bash, cmd or even powershell. How complicated is genrule-setup.sh going to be? Maybe we can later implement a genrule-setup.bat for cmd.exe and genrule-setup.ps1 for powershell?
Currently, genrule and run_shell on Windows still require bash, so genrule-steup.sh should also work.

For genrule, people can choose to use bash, cmd or even powershell.

I suppose we'll have to do the same for run_shell(), but at that point, wouldn't it just be run()?

How complicated is genrule-setup.sh going to be?

Currently it just makes shells strict via set -euo pipefail, but it could also be used for custom sandboxing logic on remote execution platforms.
But we may be able to get away with not using this file at all. For strictness, as an alternative to sourcing the file, we can instead bake the set command into either the shell toolchain (possibly at the cost of a wrapper process) or the run_shell() implementation (which adds shell assumptions to Bazel, just like genrule currently has). For sandboxing, we can bake whatever setup logic is required into a separate shell toolchain, and use the execution platform to select the sandboxing toolchain over the standard one.

If we want to make Bazel sh-less on Windows, I question the value of run_shell(). It seems to add some convenience at the expense of the portability.
Is it possible to write a function like run_shell() in a bzl file (using actions.run())? If so, it might be simpler to do so and keep Starlark shell-agnostic.

That seems appropriate and necessary if shell as a builtin concept is disappearing. +@tomlu for thoughts on reducing run_shell() to run().

Adding to @laurentlb 's comment:

If we want to make Bazel sh-less on Windows, I question the value of run_shell(). It seems to add some convenience at the expense of the portability.

run_shell()'s other hindrance to portability is its inability to declare what shell (Bash, Zsh, Sh, cmd.exe, PowerShell) and toolset it requires. See https://github.com/bazelbuild/bazel/issues/5265

I don't think I'm going to pursue this at the moment, but the doc's there if someone else wants to pick it up. I think the main issues are:

Ensuring that run_shell() does, or can be made to, use an alternative shell toolchain that can inject sandboxing setup for remote execution platforms

Deciding whether to do set -euo pipefail for run_shell() (is that our role?) and how it should be implemented (toolchain or hard-coded?)

Deciding how this interacts with the larger trajectory of shell support across multiple platforms and for run_shell() and genrule

Out of curiosity, why does genrule-setup.sh need to be a separate script? Flags passed to set can also be provided as arguments to the shell.
bash -c 'set -e; set -u; set -o pipefail; ...'
``

Is the same as:

bash -e -u -o pipefail -c '...'

The notion is that genrule-setup can apply workspace-wide common definitions, sandboxing, and (for builds with only one execution platform) execution environment setup. The counterargument is that these features do not belong in a workspace-scoped file that alters the semantics of all genrule / run_shell actions.

@brandjon What is the status of this?

The status is that I've pretty much forgotten everything not written down in this thread or the design doc.
Since this issue clearly doesn't affect the core interpreter, we should probably Transfer it to the bazelbuild/bazel repository (and mark it P4).


[T3A3][T15-A4]Bartłomiej Woźniak

Ready for review

@bartekwozniak93 great work.

Try regression testing before committing. This will help avoid some of the issues between your commits.
As mentioned in tutorial, use a new branch for each activity.

Some other comments are added. Please close the PR after reading them.


[DOCS] Add a button to take the user to the dashboard

Adds a button to the dashboard so it can be accessed anywhere.

Added a css hack to style a div.
Use the Nextra Project to link and open in new tab.

Looks like build is mad about key order:

Ah I did not realize this would conflict with #63 😓.
Would you mind porting this over to use _meta.json?

Sure <3

Hey @markflorkowski
Which do you want? Both are possible, the one on the left uses the pages so it ends up in the menu on mobile but can't be styled.
The other one is using the extraContent options. Either way is fine with me but can push whatever.


Main scene is cached when checking out git branch

Godot version:

OS/device including version:

Issue description:
I git reset --hard {some_commit_hash} where I had changed my main scene file. Godot seems to have cached the main scene file internally, and when opening, I noticed a change in my git history, as well as Godot complaining that the main scene file no longer existed.
Steps to reproduce:

Set main as MainScene.tscn (not important what, this is initial commit)
git commit
Create new scene DidNotExistBefore.tscn
Change main scene to the new scene (project-settings -> run -> main scene)
git commit
git reset --hard {initial_commit}
Restart godot and select the project

Godot will complain that the main scene file DidNotExistBefore.tscn is missing, even though the project.godot should be read at startup, and should select MainScene.tscn.
From my perspective it seems like Godot is using a cached version of the project.godot rather than loading it from the filesystem. Indeed, it seems to make changes to the project.godot as in my git tree, changes are present after re-opening the project in Godot.
This also happens when quitting Godot entirely, rather than simply to the project selector.

It is cached in ~/.config/godot/projects/ on Linux and probably similar folder on MacOS.

That's a pain, as it makes git bisect very difficult when searching for performance regression.

@tavurth You could remove that folder every time you start the engine during a bisection. It should take less than a second to do :slightly_smiling_face:

Yep that seems to work, although my files were stored under:
~/Library/Application Support/Godot/projects
Seems like there is some variance with this bug as well, as when trying a bisection just now the editor would only sometimes cause changes to the git tree after I deleted the projects folder only the first time.

Unfortunately removing the ~/Library/Application Support/Godot/projects no longer fixes this bug on OSX.
I have a project where I loaded an older version of the project.godot and the editor will not open the project from that state. Have tried:

cleaning ~/Library/Application Support/Godot/projects
cleaning ~/.config/godot/projects/

Without luck

Unfortunately removing the ~/Library/Application Support/Godot/projects no longer fixes this bug on OSX.
I have a project where I loaded an older version of the project.godot and the editor will not open the project from that state. Have tried:

cleaning ~/Library/Application Support/Godot/projects
cleaning ~/.config/godot/projects/

Without luck

@Calinou this is fixed in 3.4.2, now the scene asks to reload 👍


geospark geomesa interoperation

As a data scientist I want to be able to mix and match spatial libraries for spark. Currently, it is rather XOR as they do not integrate with each other and have overlapping classes and UDF function names.
In particular I would want to be able to easily integrate geospark and geomesa
One possibility could be to write my own udf registrator: https://github.com/DataSystemsLab/GeoSpark/blob/master/sql/src/main/scala/org/datasyslab/geosparksql/UDF/UdfRegistrator.scala
def registerAll(sparkSession: SparkSession): Unit = {
Catalog.expressions.foreach(f=>FunctionRegistry.builtin.registerFunction("geospark_"+f.getClass.getSimpleName.dropRight(1),f))
    Catalog.aggregateExpressions.foreach(f=>sparkSession.udf.register("geospark_"+f.getClass.getSimpleName,f))
  }

However this is still not handling overlapping classes (JTS, geotools)

I can confirm that the suggested workaround seems to work fine in initial tests!

An reproducible example can be found at https://github.com/geoHeil/geomesa-geospark

I get the following problems:
clash of classes
18-07-17 21:36:03 WARN UDTRegistration: Cannot register UDT for com.vividsolutions.jts.geom.Geometry, which is already registered.

@geoHeil This is probably because GeoMesa also has its own customize Geometry kryo serializer which is same as GeoSpark. GeoSpark wrote a bunch of code to put spatial indexes and geometries into an array. Since we both utilize JTS geometry, this could be a conflict.

See the latest updates to https://github.com/geoHeil/geomesa-geospark

with the help of https://github.com/geoHeil/geomesa-geospark/pull/1/files I dentified that the wrong registrator was used and ordering of registrations is important

one problems remains:

`18/07/18 21:13:33 WARN UDTRegistration: Cannot register UDT for com.vividsolutions.jts.geom.Geometry, which is already registered. How to fix this easily? Shading JTS & registrator does not seem to be a maintainble idea
understand why ordering is imortant and why if geomesa first and geospark second the error is:

Exception in thread "main" java.lang.ClassCastException: org.apache.spark.sql.catalyst.expressions.UnsafeArrayData cannot be cast to org.apache.spark.sql.catalyst.InternalRow

query plans are impacted. Geospark optimizations are only used when not using it in conjunction with geomesa

make runGeosparkSolo

geospark & geomesa
regular join
== Physical Plan ==
*HashAggregate(keys=[], functions=[count(1)], output=[count#120L])
+- Exchange SinglePartition
   +- *HashAggregate(keys=[], functions=[partial_count(1)], output=[count#124L])
      +- *Project
         +- BroadcastNestedLoopJoin BuildRight, Inner,  **org.apache.spark.sql.geosparksql.expressions.ST_Contains$**
            :- LocalTableScan [geom_polygons#72]
            +- BroadcastExchange IdentityBroadcastMode
               +- LocalTableScan [geom_points#60]

geospark solo
optimized range join
== Physical Plan ==
*HashAggregate(keys=[], functions=[count(1)], output=[count#81L])
+- Exchange SinglePartition
   +- *HashAggregate(keys=[], functions=[partial_count(1)], output=[count#85L])
      +- *Project
         +- RangeJoin geom_polygons#43: geometry, geom_points#31: geometry, false
            :- LocalTableScan [geom_polygons#43]
            +- LocalTableScan [geom_points#31]

@jiayuasu do you believe this conflict is causing the problem that spark resorts to regular, i.e. no longer optimized joins?

@geoHeil You probably can try to register GeoSpark join strategy manually: https://github.com/DataSystemsLab/GeoSpark/blob/master/sql/src/main/scala/org/datasyslab/geosparksql/utils/GeoSparkSQLRegistrator.scala
In other words, add the following line:
sparkSession.experimental.extraStrategies = JoinQueryDetector :: Nil

@jiayuasu thanks a lot. This is correct / was lacking from my registration. Now optimized range joins are used as well.
Do you have an opinion regarding UDT registration / clashing class names? Or a better Idea than my own above with shading?
geospark
import com.vividsolutions.jts.geom.Geometry
import com.vividsolutions.jts.index.SpatialIndex
UDTRegistration.register(classOf[Geometry].getName, classOf[GeometryUDT].getName)
UDTRegistration.register(classOf[SpatialIndex].getName, classOf[IndexUDT].getName)

geomesa
import com.vividsolutions.jts.geom._
val typeMap: Map[Class[_], Class[_ <: UserDefinedType[_]]] = Map(
    classOf[Geometry]            -> classOf[GeometryUDT],
    classOf[Point]               -> classOf[PointUDT],
    classOf[LineString]          -> classOf[LineStringUDT],
    classOf[Polygon]             -> classOf[PolygonUDT],
    classOf[MultiPoint]          -> classOf[MultiPointUDT],
    classOf[MultiLineString]     -> classOf[MultiLineStringUDT],
    classOf[MultiPolygon]        -> classOf[MultiPolygonUDT],
    classOf[GeometryCollection]  -> classOf[GeometryCollectionUDT]
  )

is there a good way to merge the registrations (prevent double registrations (or can these simply be ignored?
is geospark adding some custom (https://github.com/jiayuasu/JTSplus) code under the namespace of com.vividsolutions.jts.* i.e. when the order is

geospark
geomesa
no functionality is lost, any warning regarding double registration of the types could be ignored

Geomesa will serialize using JTS
override def serialize(obj: T): InternalRow = {
    new GenericInternalRow(Array[Any](WKBUtils.write(obj)))
  }

  override def sqlType: DataType = StructType(Seq(
    StructField("wkb", DataTypes.BinaryType)
  ))
  override def deserialize(datum: Any): T = {
    val ir = datum.asInstanceOf[InternalRow]
    WKBUtils.read(ir.getBinary(0)).asInstanceOf[T]
  }

geospark using
def serialize(geometry: Geometry): Array[Byte] = {
    val out = new ByteArrayOutputStream()
    val kryo = new Kryo()
    val geometrySerde = new GeometrySerde()
    val output = new Output(out)
    geometrySerde.write(kryo, output, geometry)
    output.close()
    return out.toByteArray
  }

  def deserialize(values: ArrayData): Geometry = {
    val in = new ByteArrayInputStream(values.toByteArray())
    val kryo = new Kryo()
    val geometrySerde = new GeometrySerde()
    val input = new Input(in)
    val geometry = geometrySerde.read(kryo, input, classOf[Geometry])
    input.close()
    return geometry.asInstanceOf[Geometry]
  }

is there any problem if JTS code (from geomesa) is serialized via the geospark serializer? Any problems regarding efficiency?

According to James (from geomesa gitter chat)

One strategy that might work would be for GeoSpark and GeoMesa to agree on the classnames for UDT registrations
and then for end users to register ONE AND ONLY ONE set of the UDTs...
the UDFs could be based on those classnames, and there's a fight chance that'd let someone 'mix and match' (as well as combine UDFs between packages)

is there some interest from both projects to collaborate here?

cannot resolve 'CAST(`hw_aggreagtion_area` AS ARRAY<TINYINT>)' due to data type mismatch: cannot cast org.apache.spark.sql.jts.PointUDT@449554e8 to org.apache.spark.sql.geosparksql.UDT.GeometryUDT@3f2c1eb5;

this is then the problem of clashing UDT. How could this be resolved (quickly)?

@geoHeil your blog post about this work is great!
@jiayuasu any thoughts integration points?


Ready to use tx

closes #41
however, this is still block by #28 where we need to be able to generate the address for the change.

regarding #28 I just pushed something that may not be correct and will need reviewed.


make mask type order distinct from saved values

did this to future proof MaskType values, so we shouldn't need to make databases broken if we add/change mask types.
this PR does break current DLETHAL  masks, but I also made this bitmaskable  because in the future I'd like to kill DLETHAL in favour of SETMASK 1 lethal delayed which would end up being MaskType.LETHAL|MaskType.DELAYED

I've pre-emptively added MaskType.DELAYED and made MaskType.DLETHAL a bitwise OR of LETHAL and DELAYED. work will come later to get rid of SETMASK 1 DLETHAL


Could not build wheels for amuse-framework, which is required to install pyproject.toml-based projects

Hello,
I am trying to install AMUSE on my macOS Ventura 13.4. I used MacPorts to install all of the prerequisites. I believe everything is installed properly. However, running pip install amuse-framework yields the following error:

ERROR: Could not build wheels for amuse-framework, which is required to install pyproject.toml-based projects

I tried to follow the suggestions listed in 911, but that didn't help. I would appreciate any suggestions from your side.
Thanks in advance!

Hi Mohammad,
Just to check, you're installing into a virtualenv, not a Conda environment?
Unfortunately, it's not easy to get the build log when doing a pip install (see #449), so it's difficult to see what's going wrong. The best thing to do is probably to try a development install.
Do make sure that you remove any already installed amuse-* packages from the environment before doing the development install, as they will clash with the development install and cause errors. After that,
git clone https://github.com/amusecode/amuse.git
cd amuse
. /path/to/venv/bin/activate     # if not already active
pip install -e .
python setup.py develop_build

will probably give an error somewhere, given that it's not working, but it should produce a build.log file that you can attach here that will hopefully show us what's going wrong.

Hi Lourens,
Thank you for your willingness to help. I got an error as below, however, I already tried to compile a simple "hello world" program and that worked smoothly.

  checking for Fortran 77 libraries of g77...
  checking for dummy main to link with Fortran 77 libraries... none
  checking for Fortran 77 name-mangling scheme... configure: error: in `/Users/mohammad/Documents/GitHub/amuse':
  configure: error: cannot compile a simple Fortran program
  See `config.log' for more details

Could you please attach the build.log file and the config.log file here, and I think we'll need config.mk as well? I know it looks like spam (and please post them as an attachment, not inline), but it's actually the information we need to figure out what the problem is :smile:.

Here they are, however, I couldn't find the build.log.
config.log
config.mk.txt

Thanks! It seems to be finding a Fortran compiler at /usr/local/bin/g77 which won't run because it's for the wrong CPU type. Is it possible that you installed a Fortran compiler without MacPorts at some point, and that it was a Fortran compiler for an Intel Mac? Maybe something that was backed up from a previous machine and then restored on this one?
If you cannot easily remove that g77compiler, perhaps you could remove /usr/local/bin from your PATH when you try again? That should keep it from being found at least. I'm actually not entirely sure why we're first detecting gfortran and then also need to detect g77, but with a bit of luck getting the broken g77 out of the way things will work.
There's another problem in that it cannot find Cython, which I think is needed for compiling the workers. I cannot see from this where your Python comes from, but ideally it would be the one from MacPorts rather than the system Python. MacPorts has a py-cython package that you can install to make Cython available, but we'll probably get in trouble if we mix that with the system Python.
If you run ls -l /Users/mohammad/Amuse-env/bin/python* then you should see a link to /opt/local/bin/python, or something similar if you've got the MacPorts Python (I don't have a Mac, so I'm guessing a little bit). Could you try that and see what it says?

I'm afraid that I didn't fully understand what do you mean by saying your PATH. Do you mean my .zshrc file? I don't have any thing that points to g77 in .zshrc file.
I got the following

lrwxr-xr-x  1 mohammad  staff   7 Oct  8 11:48 /Users/mohammad/Amuse-env/bin/python -> python3
lrwxr-xr-x  1 mohammad  staff  37 Oct  8 11:48 /Users/mohammad/Amuse-env/bin/python3 -> /Users/mohammad/anaconda3/bin/python3
lrwxr-xr-x  1 mohammad  staff   7 Oct  8 11:48 /Users/mohammad/Amuse-env/bin/python3.10 -> python3

g77
Sorry, I should have been clearer.
PATH is an environment variable that lists all the directories where the system should search for programs if you run a command. The configure script here tries to run the command g77, and when it does so the system will go through the list in PATH to try to find a corresponding program. You can type echo ${PATH} to see the current value of PATH. This will print a list of directories, separated by colons. One of those directories is /usr/local/bin, which is a standard directory to look into on UNIX systems like macOS. It's probably set in some system configuration file rather than in your .zshrc.
So what we want to do is to set the value of PATH to exactly that list, except that we omit the /usr/local/bin part, so that that directory won't be searched. You can set the value of an environment variable using the export command: export PATH="dir1:dir2:dir3" where the list of directories is the one printed by the echo command above, except that you don't put the /usr/local/bin part in.
Note that this will change the value of PATH only for your currently running terminal, so don't close the window, or if you do then you'll have to do this again.
Python
Ah, it seems that the Python you're using comes from Anaconda. Somehow, you must have had a conda environment active when you made the Amuse-env. We've had no end of problems with mixed MacPorts/Anaconda (or Homebrew/Anaconda) environments, so this is probably a bad idea.
To fix this, you'll need to recreate the Amuse-env environment without an Anaconda environment active. If you have Python 3.9 installed via MacPorts as instructed, then hopefully that will create a virtualenv with the right Python and Cython available.

Thank you for your explanation! I have removed the cracked g77 file by running sudo rm -r and that helped to overcome the original issue. Then I created a new environment and made sure that my Anaconda was deactivated. Now I'm running python setup.py develop_build which seems to take ages. Is this normal? given that I have a monster MacBook with 64GB of RAM.
Also, I noticed an error regarding CUDA as below. Is that something that I can ignore?

make[1]: *** [dist/distributed-amuse.jar] Error 1
make: *** [src/dist/distributed-amuse.jar] Error 2
[03:22:11] building etics
error in call, tail output:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Etics code
CUDA_TK variable is not set to a valid path,
please set the CUDA_TK variable to the directory
where you installed CUDA
the CUDA_TK directory must contain a bin directory with the  executable
make[1]: *** No rule to make target `raise_error'.  Stop.
make: *** [/NOCUDACONFIGURED] Error 2

It can take quite a while to compile AMUSE, the build system doesn't parallelise things well, so it will only use one core. Hopefully we can improve on that in the future.
It looks like CUDA wasn't detected, do you have an nVidia GPU in your laptop? If not, then that makes sense. Any community codes that require CUDA will not be built, but the rest should still work in this case.

Unfortunately, I have an intel graphics card. Also, the code currently is building mesa_r15140 so I think we can close this issue soon . Thank you so much for your time and prompt responses.

Ah yes, mesa takes forever. Alright, let's hope it will all work now, if not just let me know and we'll debug some more.


socketTimeout trigger on empty lines

const { Client } = require('./')
const stream = require('stream')

// CouchDB server
const client = new Client('http://localhost:5984', {
  socketTimeout: 15e3,
  headersTimeout: 15e3
})

client.stream({
  method: 'GET',
  path: '/nxt/_changes?feed=continuous&heartbeat=5000'
}, () => new stream.Writable({
  write (chunk, encoding, callback) {
    console.error(String(chunk))
    callback()
  }
}))

let x = 0
setInterval(() => {
  console.error("# ", x++)
}, 1e3)

Also logging inside kOnBody and kOnExecute in Parser will give the following output:
kOnExecute
#  0
#  1
#  2
#  3
#  4
kOnBody

kOnExecute
#  5
#  6
#  7
#  8
#  9
kOnBody

kOnExecute
#  10
#  11
#  12
#  13
#  14
kOnBody

#  15
#  16
#  17
#  18
#  19
kOnBody

#  20
#  21
#  22
#  23
#  24
kOnBody

Notice how kOnExecute does not seem to be invoked on empty lines?

So the response from the server looks something like this:
HTTP/1.1 200 OK
Transfer-Encoding: chunked
Server: CouchDB/1.6.1 (Erlang OTP/17)
Date: Wed, 29 Jul 2020 10:06:14 GMT
Content-Type: text/plain; charset=utf-8
Cache-Control: must-revalidate

1

1

1

1

Basically it's long polling chunked response which sends \n is a heartbeat. It seems to me that for some reason a line of \n in some combination doesn't invoke kOnExecute. Maybe https://github.com/nodejs/node/blob/master/src/node_http_parser.cc#L665?
Might also explain https://github.com/mcollina/undici/issues/268
@indutny @addaleax Do you have any ideas?

Add a workaround. Would be interesting to fix "properly".

Node bug https://github.com/nodejs/node/pull/34578


[BUG] leapp/answerfile need to be acknowledge for remove_pam_pkcs11_module_check

When running leapp manually using LEAPP_OVL_SIZE=3000 /usr/bin/leapp upgrade command
if the answerfile is not setup correctly it ends up in a state where user need to adjust it
our current logic do not handle the comment correctly
============================================================
                     UPGRADE INHIBITED
============================================================

2023-09-07 17:26:29.469 ERROR    PID: 17994 leapp: Upgrade has been inhibited due to the following problems:
2023-09-07 17:26:29.471 ERROR    PID: 17994 leapp:     1. Inhibitor: Missing required answers in the answer file

============================================================
                     UPGRADE INHIBITED
============================================================

Upgrade has been inhibited due to the following problems:
    1. Inhibitor: Missing required answers in the answer file
Consult the pre-upgrade report for details and possible remediation.

============================================================
                     UPGRADE INHIBITED
============================================================

Debug output written to /var/log/leapp/leapp-upgrade.log

============================================================
                           REPORT
============================================================

A report has been generated at /var/log/leapp/leapp-report.json
A report has been generated at /var/log/leapp/leapp-report.txt

============================================================
                       END OF REPORT
============================================================

Answerfile has been generated at /var/log/leapp/answerfile
2023-09-07 17:26:29.516 ERROR    PID: 17994 leapp: Upgrade workflow failed, check log for details

> cat /var/log/leapp/answerfile
[remove_pam_pkcs11_module_check]
# Title:              None
# Reason:             Confirmation
# =================== remove_pam_pkcs11_module_check.confirm ==================
# Label:              Disable pam_pkcs11 module in PAM configuration? If no, the upgrade process will be interrupted.
# Description:        PAM module pam_pkcs11 is no longer available in RHEL-8 since it was replaced by SSSD.
# Reason:             Leaving this module in PAM configuration may lock out the system.
# Type:               bool
# Default:            None
# Available choices: True/False
# Unanswered question. Uncomment the following line with your answer
# confirm =

we need to make sure we adjust the remove_pam_pkcs11_module_check section with
confirm=True

RE-84


[FEATURE] An option to add format instructions for AiServices return type in SystemMessage instead of UserMessage

In LangChain4j version 0.30.0 (Quarkus integration 0.11.0), when letting an AiService return a specific type, eg. List, the instruction that makes the LLM use the right format gets added to the UserMessage instead of the SystemMessage, like this:
[{"role":"system",
"content":"Split the user feedback into coherent parts of literal user text that treat a similar topic, that can then be addressed separately.\nIf the user treats the same topic in multiple parts of the feedback, make sure to group them together. If the feedback is about only one topic, return only one item.\n"},
{"role":"user",
"content":"great food!\nYou must put every item on a separate line."}]
(in this example, I specified the SystemMessage, and '\nYou must put every item on a separate line.' got added by LangChain4j.
By adding this instruction to the UserMessage, half of the time, the model will return two feedback items instead of the expected one:

great food!
You must put every item on a separate line.

I think this would be solved by adding the instruction as last part of the SystemMessage.
I'm not entirely sure how this would interplay with memory, although I think the typical use case when AiServices return java objects other than strings, is that they have no memory, and if they do, every answer will be of the form specified in the SystemMessage instruction, so I expect that to work fine.
The same thing happens for AiServices returning POJOs, the JSON format it should answer in is also attached to the UserMessage instead of SystemMessage.

Related: https://github.com/langchain4j/langchain4j/issues/793

Hi @LizeRaes thanks! Did you test if setting instructions in system message works better?

Just tested with the same example as above, but adding 'You must put every item on a separate line' at the end of the SystemMessage (without AiService):
in case of multiple items, the result is correct, model returns eg.

Great food!
The room was a bit cold though

In case of a single item (UserMessage 'Great food!), it doesn't behave correctly at all, model return (mutliple times):
Thank you for your positive feedback on the food!
I can probably prompt it in a way that it does the right thing. I think that adding 'You must put every item on a separate line' at the end of the SystemMessage will usually not cause an issue (but adding it to UserMessage does). In any case it would be nice if one can overwrite or concatenate something before or behind the automatic LangChain4j addition.
It might be relatively easy to address when touching the code for #904
Related, I tested the TextUtils summarise method in our tutorial examples, setting n = 1. It has been returning any number of items (from 2 to 4) but not 1. I have observed an occasional similar issue during the labs, where it would return 2 bullet points instead of 3 (exceptionally). Definitely gpt-3.5 seems to be struggling with returning just one item.

Thanks to the Structured Outputs feature, this issue becomes less important because output format can be specified now using JSON schema (so no need to append instructions in the prompt itself). This works for OpenAI and Gemini and soon will work for Azure OpenAI and Github Models and hopefully more providers.
Currently, only POJO return type uses JSON schema, in the next release more return types will use JSON schema: Enums, List, etc


Added 'disableVideoTagContextMenu' option

Closes clappr/clappr#593

thanks again @tjenkinson can you also write the doc about this? disableVideoTagContextMenu

one in here https://github.com/clappr/clappr/blob/master/src/components/player.js#L84
and another at README like this one https://github.com/clappr/clappr/blob/master/README.md#loop (even though we might hold this PR for release date)

This ok?
https://github.com/clappr/clappr/pull/598


Replace jobfeed page by temporary not available page

HR are cancelling the contract with SmartRecruiters who are populating our jobs on the careers page. The new contract with the new provider is still not finalised hence we might be losing the jobs visibility. They would like to post a message that we are working on bringing the jobs back or something. It is likely to stop on Monday.

This can be done by a content change. Just put whatever message/content which makes sense on the job page.

@NCalexiaeche I added a new placeholder to https://docs.google.com/spreadsheets/d/1fhhdEIYdL1HAqN8Ehto4obh4UF_Tv8SbGTz9t75Qzpk/edit#gid=0 please make sure the text is aligned with marketing:


Mat/Par: Make it clear that estimating allowance is optional

Ad a user filling out the at/par form, I want to know see which estimates are optional and which ones are required.
Two examples are

when estimating parental leave allowance
2.) when estimating maternity leave allowance with EI

AC

[ ] Change button copy to "Estimate your maternity leave allowance (optional)" and ""Estimate your parental leave allowance (optional)"

example 2

Please test, thanks

Looks fabulous - Closing ticket


Feature: title in the card should link to app.opensauced.pizza

Type of feature
🍕 Feature
Current behavior
When viewing the card, nothing is linked. The expectation is that title should link to the app.
i.e. app.opensauced.pizza/repos/${data.full_name}
Suggested solution
The mocked data is incorrect and should provide the repo full name too. The full name is the combo of user and repo name, i.e. open-sauced/hot or ${organization}/{name}
cc / @hokagedemehin
Additional context
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Contributing Docs

[X] I agree to follow this project's Contribution Docs

.take


Photoswipe theme doesn't show image thumbnails when Javascript is disabled

Both the gallera and colorbox themes work admirably when the browser has Javascript disabled (With the mozilla NoScript plugin in my case). All thumbnails are shown and they load the full images when clicked. However, when the photoswipe theme is used, subfolders properly show thumbnails, but the actual images in each folder show up as blank white squares. The full images can still be viewed by clicking on the empty squares, though.
Is it possible to fix this without impairing the with-Javascript functionality of the theme?

Not sure if it can be fixed easily, and this is probably more an issue for photoswipe, as it seems to have its own way to load thumbnails.

Closing as this is something that depends on Photoswipe.


Get publish date

Hi,
Is there any way to get the publish date instead of "published 24 minutes ago" ?
Thanks you!

For the same reason as #114.


Remove extra trailing comma in istream iterator

A trailing comma at the end of the template parameter list is an error.

@TylerMSFT

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


How to roll back terraform deployments

Please reference  document to implement to terraform roll back ?

Hi, refer this https://developers.cloudflare.com/terraform/tutorial/roll-back/


Add color to edges?

Is there a way to change the color for some edges?

Hey @Tallyb
you can pass a style option to an edge: { style: { stroke: 'red' } ...otherOptions} or you can pass a classname. Does it work for you?


Images don't show in dev mode with Laravel backend

If you try this plugin with a Laravel + Vite + Vue stack, all the images will throw a 404 (Not Found) error and not show on the page.
This is because the tool is returning relative paths and normally an asset URL imported through Vite would have an absolute URL, and in the context of a backend such as Laravel the lack of absolute URL breaks the images.
Assuming you're running in dev mode
Without imagetools loader ( normal image importing ):
import Cat from<EMAIL_ADDRESS>
console.log(Cat)
// Output: http://localhost:3000/resources/images/cat.png

With imagetools loader:
import Cat from '@/images/cat.png?width=200'

console.log(Cat)
// Output: /@imagetools/5812d5ee51f96cb9c239acca9f2ecc22bd83998a
// Throws a not found error.

Note that build works fine. It's only a dev mode issue.

Can you check if https://github.com/JonasKruckenberg/imagetools/pull/400 would fix the issue you're facing?

Can you check if #400 would fix the issue you're facing?

No unfortunately it does not fix the issue :(
Also I think that PR is for a different purpose as they stated:

This PR fixes the paths of images in the Vite build result.

They talking about the build result. This issue I'm having happens in dev mode.

Same here. Getting 404 Errors on all images when running yarn dev in laravel vite environment
Error:
Failed to load resource: the server responded with a status of 404 (Not Found)

html code that corresponds to error
<source type="image/avif" srcset="/@imagetools/23ae5086f5b8fa6391e57bb0800aabc686bd2b37 850w">

Environment
Console Output: (just for reference and version numbers)
  VITE v4.0.1  ready in 503 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h to show help

  LARAVEL v9.43.0  plugin v0.7.1

package.json
  "laravel-vite-plugin": "^0.7.1",
  "vite": "^4.0.1",
  "vite-imagetools": "^4.0.11",
  "vue": "^3.2.45"

vite.config.js
export default defineConfig({
    build: {
        chunkSizeWarningLimit: 600,
    },
    plugins: [
        laravel({
            input: ['resources/css/frontend.css', 'resources/js/frontend.ts'],
            refresh: true,
            buildDirectory: '/build/frontend',
            config: 'frontend',
        }),
        vue({
            template: {
                transformAssetUrls: {
                    base: null,
                    includeAbsolute: false,
                },
            },
        }),
        imagetools({
            /* options */
        }),
    ],
    resolve: {
        alias: {
            '@': path.resolve(__dirname, './resources/js'),
        },
    },
    server: {
        strictPort: true,
        hmr: {
            host: 'localhost',
        },
    },

I have the same exact problem with a Rails backend:

@HassanZahirnia, if you get a chance, could you double-check that the changes from the above-referenced pull request also fixed it for you with Laravel, please?

nope, unfortunately it does not work. I'm using this plugin in a Laravel 9 and Nuxt 3 environment, in both environments @imagetools is not resolved as url in dev but build works as expected.

@DeedleFake No the issue is not fixed. Honestly not sure why you marked this issue as "fixed" before checking with a Laravel backend first 😅
If possible please re-open this issue @benmccann

Hey I've found a similar Vite plugin that uses Sharp underhood, and it's asset paths are correct in dev mode. I thought maybe someone could have a look at it and figure out what they did that would fix this issue, here is the source file:
https://github.com/jack-weilage/vite-image/blob/main/src/index.ts
Although I should mention I could have their plugin work in production. So be careful not to grab any production logic from their code.
Either way the focus is on how they've handled the path for dev mode.

Honestly not sure why you marked this issue as "fixed" before checking with a Laravel backend first 😅

To be honest, I'm not sure why I did either. Just wasn't thinking. Sorry.

@DeedleFake did you test https://github.com/JonasKruckenberg/imagetools/pull/489 with any app? I didn't think about this before, but I'm pretty sure https://github.com/JonasKruckenberg/imagetools/pull/489/files#diff-8d1a92b43a2575de2cdad4edc1af1e9586a5f1ee84ec2dad9b7af5ebc2322b13R123 is wrong because Vite's base middleware strips out the base path before passing it to any middlewares. I'm wondering if https://github.com/JonasKruckenberg/imagetools/pull/489 helps at all or should be reverted entirely?

did you test #489 with any app?

Yes, I did. I tested it with the Rails app that I was having the problems I posted above in this issue and it fixed them.

Vite's base middleware strips out the base path before passing it to any middlewares

The issue with the Rails backend was that the Vite dev server never even saw the requests because they didn't start with the base path. The way the Rails integration works is something like this:

If the path starts with the Vite base path, send it to the dev server.
If it starts with something else, check for configured Rails routes and use one that matches.
If none of those match, check for a matching file in the public directory and serve it.
If all of the above fails, yield a 404.

So without prefixing the string paths returned by the plugin when it's used in an import in the code, the Vite dev server will never even see them in the first place.

I've never worked with Laravel before, but I set up a simple project and it looks like the problem there is different, but related. In Laravel's case, assets are not routed through the main dev server but are instead sent directly to Vite. For example, in my case the Laravel dev server is running on port 8000, while the Vite dev server is running on port 5173. However, there's a big discrepancy between normal Vite image imports and ones routed through vite-imagetools:
import test from './test.png'
// test is http://[::1]:5173/resources/js/test.png

import test from './test.png?width=50'
// test is @imagetools/0078fa8134eed9d2fc44c1cd1ab4f62b63fe1041

I would speculate that there's another config option for Vite that Laravel is automatically setting to redirect assets to the dev server but that is being missed by vite-imagetools. I don't see anything obvious in the config, though.

@DeedleFake Thanks for looking into Laravel 🙌
The situation you mentioned is same as the one I also described in the first post. The assets need to have an absolute path, except on dev server the path start with the Vite server url (which would be http://localhost:3000 or http://[::1]:5173)
I suggest you to look into the repo I linked earlier. That plugin has a working path setup for dev server. I personally have no experience with Vite plugins so I couldn't figure it out myself.

I suggest you to look into the repo I linked earlier. That plugin has a working path setup for dev server.

I've been doing so, as well as looking at other plugins. The documentation around this particular situation, despite how common you'd think it is, isn't fantastic, unfortunately.

I personally have no experience with Vite plugins so I couldn't figure it out myself.

Neither do I. I'd never looked into how they worked at all before I started working on fixing this. In fact, I'd never used Vite before a week ago or so.

I tried out the repo that you linked above and it has the exact same problem:

Neither plugin generates absolute paths for their on-demand assets, and I'm not sure what the proper way to do so is.

didn't think about this before, but I'm pretty sure https://github.com/JonasKruckenberg/imagetools/pull/489/files#diff-8d1a92b43a2575de2cdad4edc1af1e9586a5f1ee84ec2dad9b7af5ebc2322b13R123 is wrong because Vite's base middleware strips out the base path before passing it to any middlewares

Okay, I think your change was correct and necessary. I can confirm that images in SvelteKit were broken on the prior release when using a base path. The way the imagetools middleware is being called it will be invoked before Vite's base middleware strips out the the base path. If on the otherhand we were returning a function that returned the middleware then we'd no longer want to strip out the base path because Vite would do it: https://vitejs.dev/guide/api-plugin.html#configureserver

Are you using laravel-vite-plugin 0.7.3? I see the latest release has a fix for the base path, so it might be broken if you're on an older version

I tried out the repo that you linked above and it has the exact same problem:
That's weird, it worked for me when I tried it.

Are you using laravel-vite-plugin 0.7.3?
Yeah I'm using the latest. But I have not modified base config so that PR fix does not affect me. Not to mention I believe majority of Laravel users don't change the base config since the default is good enough.

Honestly I think until one of maintainers sit down and try this library with a Laravel backend, there is no way to debug and fix this issue properly.

Could you provide a repository that reproduces the issue?

@benmccann Here is a reproduction repo: https://github.com/HassanZahirnia/laravel-imagetools-issue
Just in case you're not familiar with Laravel projects here are the instructions:

Rename .env.example to .env
Run composer install
Run npm install
Run php artisan key:generate
Run php artisan serve in a terminal and keep it open
In another terminal run npm run dev and also keep it open
Visit the url given by the serve command (step 5)
You can see the image fails to load since it's going through vite-imagetools plugin via the ?webp
The file you want to edit/play with is resources/views/pages/welcome.vue

After updating to vite-imagetools v4.0.16 I can confirm the images are getting resolved in Dev mode \o/, in a Nuxt 3 environment. 👍  (Haven't checked Laravel yet)

Glad the tool is starting working with other frameworks such as Nuxt and Rails, but unfortunately the Laravel support is not there yet.
@hopkins385 I checked with 4.0.16 and it still doesn't work.

Agree, I've checked it with Laravel and still not working.
package.json (just for reference)
 "vite": "^4.0.4",
 "laravel-vite-plugin": "^0.7.3",
 "vite-imagetools": "^4.0.16",
 "imagetools-core": "^3.3.0",

@driesvints @timacdonald any chance you'd be interested in taking a look at this one? It seems to occur exclusively with laravel-vite-plugin. For context, vite-imagetools is a Vite plugin for optimizing images. A Laravel-based reproduction was provided just above (https://github.com/JonasKruckenberg/imagetools/issues/396#issuecomment-1399288052), but I don't have PHP or Composer installed on my machine. I'm happy to help from this side.

Hey folks, I have a working solution for this for the Laravel plugin.
For the Laravel folks in the thread, we will can shift out of here and into this issue: https://github.com/laravel/vite-plugin/issues/194
tl;dr; We need to expose a way for developers to say "Please prefix /@imagetools with the Vite dev server URL while in dev mode.
-
+

PR will be up shortly.

See https://github.com/laravel/vite-plugin/pull/195


Logging http requests

Enable by config:
grails.plugin.sentry.logHttpRequest = true

Thank you.


Fix Typescript Models and Tests

Related to

https://github.com/manticoresoftware/manticoresearch-typescript/pull/2
https://github.com/manticoresoftware/manticoresearch-typescript/issues/3

The Typescript Package is not working for me, because aggregations and expressions are wrongly typed - with this PR i want to a) proof this with failing test cases b) fix the typings that i am aware of and c) improve the overall typescript package

Currently tests are failing but marked as green:
$ npm run test

><EMAIL_ADDRESS>test
> cross-env TS_NODE_COMPILER_OPTIONS='{"module": "commonjs" }' mocha -r ts-node/register 'test/**/*.test.ts'

✔  Utils Api Tests
ResponseError: Response returned an error code
    at UtilsApi.request (~/src/github.com/schwarmco/manticoresearch-openapi/out/manticoresearch-typescript/src/runtime.ts:135:15)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async UtilsApi.sqlRaw (~/src/github.com/schwarmco/manticoresearch-openapi/out/manticoresearch-typescript/src/apis/UtilsApi.ts:45:26)
    at async UtilsApi.sql (~/src/github.com/schwarmco/manticoresearch-openapi/out/manticoresearch-typescript/src/apis/UtilsApi.ts:61:26)
    at async Context.<anonymous> (~/src/github.com/schwarmco/manticoresearch-openapi/out/manticoresearch-typescript/test/manual.test.ts:21:13) {
  response: Response {
    [Symbol(realm)]: null,
    [Symbol(state)]: {
      aborted: false,
      rangeRequested: false,
      timingAllowPassed: true,
      requestIncludesCredentials: true,
      type: 'default',
      status: 501,
      timingInfo: [Object],
      cacheState: '',
      statusText: 'Not Implemented',
      headersList: [HeadersList],
      urlList: [Array],
      body: [Object]
    },
    [Symbol(headers)]: HeadersList {
      cookies: null,
      [Symbol(headers map)]: [Map],
      [Symbol(headers map sorted)]: null
    }
  }
}

in the next commit i will make the tests fail on error responses

Tests are now failing correctly:
$ npm run test

><EMAIL_ADDRESS>test
> cross-env TS_NODE_COMPILER_OPTIONS='{"module": "commonjs" }' mocha -r ts-node/register 'test/**/*.test.ts'

  Utils Api Tests
Error response: {
  "error": "only SELECT queries are supported"
}
    1) Testing utils api operations

  Index API Tests
Error response: {
  "error": "only SELECT queries are supported"
}
    2) Testing index api operations

  Search Api Tests
Error response: {
  "error": "only SELECT queries are supported"
}
    3) Testing search api operations

  0 passing (38ms)
  3 failing

  1) Utils Api Tests
       Testing utils api operations:
     AssertionError: expected ResponseError: Response returned an error… { response: Response{ …(3) } } to be null
      at Context.<anonymous> (test/manual.test.ts:35:22)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

  2) Index API Tests
       Testing index api operations:
     AssertionError: expected ResponseError: Response returned an error… { response: Response{ …(3) } } to be null
      at Context.<anonymous> (test/manual.test.ts:148:22)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

  3) Search Api Tests
       Testing search api operations:
     AssertionError: expected ResponseError: Response returned an error… { response: Response{ …(3) } } to be null
      at Context.<anonymous> (test/manual.test.ts:231:22)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

Looking at the other clients:

https://github.com/manticoresoftware/openapi/blob/c9296488892734049fc4a2dd508eb8987876ed96/out/manticoresearch-python/test/test_manual.py#L33
https://github.com/manticoresoftware/openapi/blob/c9296488892734049fc4a2dd508eb8987876ed96/out/manticoresearch-elixir/test/api_index_test.exs#L31

utilsApi.sql generally does not require the rawResponse parameter to be defined to allow queries like TRUNCATE or SHOW TABLES - therefore i defaulted the flag to true. Are you fine with this @Nick-S-2018 @sanikolaev ?
with the last commit (b0e54d2), the tests are green:

$ npm run test

><EMAIL_ADDRESS>test
> cross-env TS_NODE_COMPILER_OPTIONS='{"module": "commonjs" }' mocha -r ts-node/register 'test/**/*.test.ts'

  Utils Api Tests
    ✔ Testing utils api operations

  Index API Tests
    ✔ Testing index api operations

  Search Api Tests
    ✔ Testing search api operations

  3 passing (58ms)

Adding a Test Case with an Aggregation Array according to the Typescript Typings and the OpenAPI spec found here:
https://github.com/manticoresoftware/openapi/blob/c9296488892734049fc4a2dd508eb8987876ed96/out/manticoresearch-typescript/src/models/index.ts#L895
https://github.com/manticoresoftware/openapi/blob/master/manticore.yml#L625-L628
This results in a failed test result with the manticoresearch-server responding aggs property should be an object:
 $ npm run test

><EMAIL_ADDRESS>test
> cross-env TS_NODE_COMPILER_OPTIONS='{"module": "commonjs" }' mocha -r ts-node/register 'test/**/*.test.ts'

  Utils Api Tests
    ✔ Testing utils api operations

  Index API Tests
    ✔ Testing index api operations

  Search Api Tests
    ✔ Testing search api operations
Error response: {
  "name": "AssertionError",
  "message": "expected [ { total: +0, warning: '', …(1) } ] to have deep nested property 'hits.total'",
  "showDiff": false,
  "actual": [
    {
      "total": 0,
      "warning": "",
      "error": "\"aggs\" property should be an object\""
    }
  ]
}
    1) Testing search aggregation

  3 passing (78ms)
  1 failing

  1) Search Api Tests
       Testing search aggregation:
     AssertionError: expected AssertionError{ …(5) } to be null
      at Context.<anonymous> (test/manual.test.ts:254:24)
      at processTicksAndRejections (node:internal/process/task_queues:95:5)

Warning: The last commit 9261364 breaks all clients (the need to be rebuilt) because it changes the OpenAPI Spec - but it basically makes aggregations work:
https://github.com/schwarmco/manticoresearch-openapi/blob/feature/typescript-tests/out/manticoresearch-typescript/test/manual.test.ts#L236-L253
Resulting in all green tests:
$ npm run test

><EMAIL_ADDRESS>test
> cross-env TS_NODE_COMPILER_OPTIONS='{"module": "commonjs" }' mocha -r ts-node/register 'test/**/*.test.ts'

  Utils Api Tests
    ✔ Testing utils api operations

  Index API Tests
    ✔ Testing index api operations

  Search Api Tests
    ✔ Testing search api operations
    ✔ Testing search aggregation

  4 passing (76ms)

@sanikolaev have you had a chance to review the OpenAPI spec with the team?

Thank you for the PR, @schwarmco !

@sanikolaev have you had a chance to review the OpenAPI spec with the team?

Yes, we confirmed what you found is a mistake in it. Sorry we've been busy with other things lately, but are now getting back to the client issues.
@Nick-S-2018 pls review this PR.

@Nick-S-2018 thank you for the feedback! happy to hear that this works for you! if you wouldn't mind, i'd do the same thing for the expressions (adding failing tests, fix openapi spec and add working tests) before finalizing this PR. Of course i can remove the changes in out

so... according to the current openapi spec, expressions is an array - but the test fails:
npm run test

><EMAIL_ADDRESS>test
> cross-env TS_NODE_COMPILER_OPTIONS='{"module": "commonjs" }' mocha -r ts-node/register 'test/**/*.test.ts'

  Utils Api Tests
    ✔ Testing utils api operations (43ms)

  Index API Tests
    ✔ Testing index api operations

  Search Api Tests
    ✔ Testing search api operations
    ✔ Testing search aggregation
Error response: {
  "name": "AssertionError",
  "message": "expected [ { total: +0, warning: '', …(1) } ] to ...",
  "showDiff": false,
  "actual": [
    {
      "total": 0,
      "warning": "",
      "error": "\"expressions\" property should be an object"
    }
  ]
}

With the updated OpenAPI Spec (according to the docs) adding expressions to a search is working:
https://github.com/manticoresoftware/openapi/blob/57c1dd68fc170b7b78e4d4b328307db4e7754f19/test/typescript/manual.test.ts#L262-L275
$ npm run test

><EMAIL_ADDRESS>test
> cross-env TS_NODE_COMPILER_OPTIONS='{"module": "commonjs" }' mocha -r ts-node/register 'test/**/*.test.ts'

  Utils Api Tests
    ✔ Testing utils api operations

  Index API Tests
    ✔ Testing index api operations

  Search Api Tests
    ✔ Testing search api operations
    ✔ Testing search aggregation
    ✔ Testing search expressions

  5 passing (85ms)


Add .travis.yml

This change is

Is there any reason why all the formatting has been stripped? I assume it's because you ran the travis command when generating the token and it overwrote the file.
Do we want it stripped of formatting or no? I think the comments would be helpful to someone trying to understand what our travis.yml does.

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

After a quick discussion on slack, it was decided against porting over the comments from the original file as they don't provide any really useful information.

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


Weighted/correlated observations

It should be relatively straightforward to modify the IRLS algorithm to account for varying weights between data points or even correlations between data points. There may be other ramifications to consider, e.g. for convergence and termination conditions.

#37 incorporates both frequency (count) and variance (analytic) weights.
Correlated residuals are not used rarely as often, so an implementation allowing them will be left to the future, if ever.


TransactionInactiveError

//create myDB    "dexie": "^2.0.4",
let myDB = new Dexie('myDb');
myDB.version(1).stores({
sendFail: ++id, data,
questionFail: ++id, data,pages, classId, res
});
window.myDB = myDB;
//put
window.myDB.sendFail.put({
            data: JSON.stringify(toPubJson)
        })

// delete
window.myDB.questionFail.where("id").equals(1).delete()
.then(()=>console.log("success")).catch(e=>console.log(e))
//error
message: "Failed to execute 'count' on 'IDBObjectStore': The transaction is not active."

I learned that if i add a new table in myDB it doesn't work under the same version

Do you think it's related to what I describe in Database Versioning?

yes,i write a demo that reproduce them


How to zoom only video with videojs

I want to zoom a video with panzoom. However, it zooms the video player including all controls:
https://codepen.io/Sebzap/pen/oNymZBX
What can I do to make only the video itself zoom? I have no idea how to approach this.
Also, how can I fix the parent element so that the video always stays in the parent container, and can only be dragged to the edges (so that no black background is seen?)
Thanks for any hint,
Sebastian

Thanks very much, Timmy!
I got it to work. For future reference I updated the pen at https://codepen.io/Sebzap/pen/oNymZBX.


Refactor PathDetailsBuilderFactory

only use PathDetailsBuilderFactory within PathDetailsFromEdges.calcDetails()
use a Set for the request path details as duplicate entries make no sense
create all PathDetailsBuilders within a switch statement for better readability
provide varargs GHRequest.setPathDetails() variant for better readability when using hardcoded list of values(e.g unittests)

Why removing the method GraphHopper.setPathDetailsBuilderFactory? Only with this method adding custom encoded values and path details is possible.

I wasn't aware that this is supported at the moment. I've rebased my branch on the current master including the mtb changes and removed the last commit.

@karussell anything missing?

time :D

time for a closer review :D

Fixed the conflicts

@karussell i've switched back to using a List and implemented the duplicate detection within PathDetailsBuilderFactory


Jack's GildedRose

With my tests, should I update them to be dependent on the new variable class fields, or should I keep them with static numbers?
(i.e. should tests reflect the spec or the code)


authenticated api error

I am trying to make a basic authenticated  api and getting  error.
from bitfinex import ClientV2 as Client2
BTFXCLIENT = Client2('api656j56ejejKey', 'apiSec56je56jjj56j5ret')
BTFXCLIENT.active_positions()

Can you give me more details?
What are you Operating system, python version , error  you  receive ?

OS: win10
Python 3.8.5
Run the code in Anaconda Navigator
Error refer the picture

You have used the same api keys with a  different library or a different nonce multiplier.  You could try to instantiate with a higher nonce multiplier :
BTFXCLIENT = Client2('api656j56ejejKey', 'apiSec56je56jjj56j5ret', nonce_multiplier=2.0)
BTFXCLIENT.active_positions()
I recommend that you create a new api key for this and use different api-keys for different things : one for mobile app, one for each trading system

Thanks a lot!


Has anybody used it for a real live ActivityPub?
We've kicked the tires a bit because we know python but haven't figured out how to deploy a real AP with it yet.

hey! i haven't worked on it in a while. where i've got it to is, i could get posts to show up on mastodon? i haven't implemented much beyond that

i got real work, and that kind of put big side projects like this on hold. so did trying to figure out how manage authentication ;)

Uh-oh, that reall work will get ya!  But thanks for responding.

The message signing stuff looks like the tricky part. Eugen's blog post looks like a good summary though...
https://blog.joinmastodon.org/2018/06/how-to-implement-a-basic-activitypub-server/
Maybe I will try to make time to work of AP stuff again. Yeah real work stuff does get in the way.

yeah. i think that i got signing to work, at least sometimes? posts wouldn't have shown up on mastodon at all otherwise, right? in here


eosio_build.sh llvm exists error

When running
./eosio_build.sh
I get the error:
mkdir: wasm-compiler: File exists
fatal: destination path 'llvm' already exists and is not an empty directory.
	Unable to clone llvm repo @ https://github.com/llvm-mirror/llvm.git.
	Exiting now.

Independent from whether llvm is inside the directory, already installed with brew, unlinked etc.

Fixed it by:

Edit scripts/eosio_build_darwin.sh to delete the llvm folder before git clone

When error Found PythonInterp: /Users/skober/.pyenv/shims/python2.7 (found version "1.4") appears edit  scripts/eosio_build_darwin.sh  to point to your python installation with the cmake option  -DPYTHON_EXECUTABLE=/<path>/.pyenv/shims/python in the relevant section (wasm on my side, which is the last section in the script).

On this error:

Failed to find Gettext libintl (missing: Intl_INCLUDE_DIR)
Call Stack (most recent call first):
 /usr/local/Cellar/cmake/3.11.0/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:378 (_FPHSA_FAILURE_MESSAGE)
 /usr/local/Cellar/cmake/3.11.0/share/cmake/Modules/FindIntl.cmake:47 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
 programs/cleos/CMakeLists.txt:29 (find_package)

Reinstall gettext: brew reinstall gettext
Relink: brew unlink gettext && brew link gettext --force

You said scripts/eosio_build_darwin.sh and but didn't say what to do, what to edit? Explain little bit more?

@sisardor Updated the post. Does it help now?
And please add mention with @ notation, otherwise I dont get a notification.

@fabifrank @sisardor on darwin remove the directory /tmp/wasm-compiler
rm -rf /tmp/wasm-compiler
And run the eosio_build.sh script again and you should be good to go.

@pacificcode Yeah that should work in case there's no other error in the build process. Which was not the case on my side.


Regression in apache/pekko-connectors for derivation

Based on OpenCB failure for apache/pekko-connectors - build logs
Compiler version
Since 3.4.0
Last good release: 3.4.0-RC1-bin-20231212-97e4401-NIGHTLY
First bad release: 3.4.0-RC1-bin-20231213-9dce045-NIGHTLY
Bisect points to d6c7e18da5985a1452ec530ca204737e0301da42
Minimized code
import scala.deriving.Mirror

type FieldType[K, +V] = (K, V)
type ZipWith[T1 <: Tuple, T2 <: Tuple, F[_, _]] <: Tuple = (T1, T2) match
  case (h1 *: t1, h2 *: t2) => F[h1, h2] *: ZipWith[t1, t2, F]
  case (EmptyTuple, ?)      => EmptyTuple
  case (?, EmptyTuple)      => EmptyTuple
  case _                    => Tuple

trait LabelledGeneric[A]:
  type Repr <: Tuple

object LabelledGeneric:
  type Aux[A, R] = LabelledGeneric[A] { type Repr = R }
  inline given productInst[A <: Product](using m: Mirror.ProductOf[A]): LabelledGeneric.Aux[A, ZipWith[m.MirroredElemLabels, m.MirroredElemTypes, FieldType]] =
    new LabelledGeneric[A]:
      type Repr = ZipWith[m.MirroredElemLabels, m.MirroredElemTypes, FieldType]

trait PdxEncoder[A]
object PdxEncoder:
  given objectEncoder[A, Repr <: Tuple](using LabelledGeneric.Aux[A, Repr]): PdxEncoder[A] = ???

case class Person(id: Int, name: String)

@main def Test =
  val fails: PdxEncoder[Person] = PdxEncoder.objectEncoder // error

Output
-- [E172] Type Error: /Users/wmazur/projects/scala3/bisect/test.scala:27:58 ----
27 |  val fails: PdxEncoder[Person] = PdxEncoder.objectEncoder
   |                                                          ^
   |No given instance of type LabelledGeneric.Aux[Person, Repr] was found for parameter x$1 of given instance objectEncoder in object PdxEncoder.
   |I found:
   |
   |    LabelledGeneric.productInst[Person](
   |      Person.$asInstanceOf[
   |
   |          scala.deriving.Mirror.Product{
   |            type MirroredMonoType = Person; type MirroredType = Person;
   |              type MirroredLabel = ("Person" : String);
   |              type MirroredElemTypes = (Int, String);
   |              type MirroredElemLabels = (("id" : String), ("name" : String))
   |          }
   |
   |      ]
   |    )
   |
   |But given instance productInst in object LabelledGeneric does not match type LabelledGeneric.Aux[Person, Repr]
   |
   |where:    Repr is a type variable with constraint <: Tuple
   |.

Expectation
Should probably compile
Workaround
Defining LabelledGeneric.productInst as transparent inline fixes the problem

Closing as it works as expected, the commit mentioned in bisect describes that it's expected


Do not collapse Update Rates button in a transient state

Fixes #.
#352
Description of the changes:
In this change I am fixing an issue where focus moves from the "Update Rates" button to the "CE" button without being initiated by the user explicitly. The issue is that when "Update Rates" is pressed the button becomes collapsed. When the button becomes collapsed the XAML focus manager then migrates focus to the next logical thing (which happens to be the "CE" button). In this change I modified the "Update Rates" button to not collapse when being pressed. For completeness I added a storyboard animation to fade in the Currency Ratio so that it matches the animations of the Timestamp element it sits next to.
Now that the "Update Rates" button is always visible there is a possibility that the user will click it numerous times before the first update actually completes. My change safeguards this scenario by adding a logical check in the button's click handler so that work is only done if we are not already updating the rates.
How changes were validated:
Manual testing

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

Thanks @rudyhuyn for the quick feedback!
I think there might be a misunderstanding of my change. The "Update Rates" button never becomes collapsed/hidden/invisible. My change makes it such that the button is always visible. That is why I safeguarded against spamming the button quickly. The elements that I added the bindings to can't get focus and are not picked up by narrator, so there should be no issue with having them hidden during the reload.
Picture is after I press the button before it finishes updating the rate

With regards to the binding/storyboard combo, I didnt know that could race! Ill switch that over to a VisualState shared for the 2 elements.

Thanks @rudyhuyn for the quick feedback!
I think there might be a misunderstanding of my change. The "Update Rates" button never becomes collapsed/hidden/invisible. My change makes it such that the button is always visible. That is why I safeguarded against spamming the button quickly. The elements that I added the bindings to can't get focus and are not picked up by narrator, so there should be no issue with having them hidden during the reload.
Picture is after I press the button before it finishes updating the rate

With regards to the binding/storyboard combo, I didnt know that could race! Ill switch that over to a VisualState shared for the 2 elements.

 I missed this point. 👍
A Visual State will be great


Want to make a footer

Already assigned issue, please check the issue section before raising any new issues. Thank you!


Add Kinesis backing for tracker

Cousin of https://github.com/snowplow/snowplow-python-tracker/issues/46
Unscheduled

This is no longer aligned with our roadmap. It's overkill for this tracker; we're looking into alternative solutions for version 1.0.0. Closing.


panel dependency markdown compatibility problem

installing the latest version Markdown-3.1.1
results in a No module named 'fenced_code'
error for a panel markdown pane.

But is ok for 3.0?

Yes, 3.0.1 is fine.

This needs more investigation, it's not quite clear what's causing the issue but it may be related to the plugins we enable.

Cannot reproduce the issue with markdown version 3.1.1


IPv6 support of search backend

Hate to bring it up again but the backend we are using for the search doesn't seem to support IPv6. While Elasticsearch is perfectly capable of IPv6 the host (despite being on AWS) failed to enable it.
Like explained in my NixOS.org Netlify post we should try to have this as a baseline requirement for new services that will - to some degree - be mandatory/required to interacting with our services/websites.

I will ask if our ES provider can support IPv6.
I know your :heart: is in the right place, but I would like to avoid such strong wording as "This is a discrimination ...". It might be understood wrong depending on the context. I was also guilty of such mistakes in the past and I just hope I will not make them in the future.

Just so other people can find this using the GitHub search. I just got bitten by that.

Network Error!
A network request bonsaisearch.net domain failed. This is either due to a content blocker or a networking issue.

This is an accessibility issue. Accessibility is not only about "handicaps".
The search cannot ship if it's not IPv6 enabled, plain and simple. Some environments won't go through IPv4, as can be seen here by @mweinelt (I suppose), which means that some technically inclined people, you know, the kind of people a Linux distro, or a package manager caters for, will have an issue that is mostly out of their control for the site.
This is, I believe, not something that we can just program our way out of, so I think this'll need to be validated with the upstream provider.

Perhaps it is something we could fix with a ipv6 capable proxy if upstream isn't able to support ipv6 directly.
On Thu, Jul 30, 2020, at 11:11 AM, Samuel Dionne-Riel wrote:

This is an accessibility issue. Accessibility is not only about "handicaps".

The search cannot ship if it's not IPv6 enabled, plain and simple. Some environments won't go through IPv4, as can be seen here by @mweinelt https://github.com/mweinelt (I suppose), which means that some technically inclined people, you know, the kind of people a Linux distro, or a package manager caters for, will have an issue that is mostly out of their control for the site.

This is, I believe, not something that we can just program our way out of, so I think this'll need to be validated with the upstream provider.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/NixOS/nixos-search/issues/52#issuecomment-666440822, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAASXLCMYWPJFKJKZJEDRITR6GETTANCNFSM4NINNBNQ.

Ipv6 is a blocker, as it wasn't for nixos.org. It is important thing definitely, but not a blocker.

I also reminded bonsai.io to answer the questions regarding ipv6 support, since they didn't answer.

Regardless of their decision we should move forward and not punish all of the users. Punish is probably to strong of a word, but can not think of a better one.

Punish? What do you mean? We've been living with this solution for years now and it just works. It has different problems but none that make it unusable.

Any updates on this?

Still the same problem… When will this be fixed?
Also This is either due to a content blocker or a networking issue. is not true: It's not a content blocker or a fault in the network, it's a problem at bonsaisearch.

Right about now. Can someone double-check that PR?


Generate unique JTA Migratable Target names in configured clusters

A while back, WDT was fixed so that it generates unique JTA Migratable Target names in a dynamic cluster, but it looks like the same fix is also needed for configured clusters.
Namely the following configured server stanza:
             JTAMigratableTarget:
                Cluster: "@@PROP:CLUSTER_NAME@@"
                UserPreferredServer: "@@PROP:MANAGED_SERVER_NAME_BASE@@2"

Generates the same Name on each server in the cluster, for example:
  <jta-migratable-target>
      <name>NO_NAME_0</name>
      <user-preferred-server>managed-server1</user-preferred-server>
      <cluster>cluster-1</cluster>
    </jta-migratable-target>

The work around is to alter the WDT to specify a unique name:
 JTAMigratableTarget:
                Name: "@@PROP:MANAGED_SERVER_NAME_BASE@@2"
                Cluster: "@@PROP:CLUSTER_NAME@@"
                UserPreferredServer: "@@PROP:MANAGED_SERVER_NAME_BASE@@2"

Workaround suggested will not work as Name is not one of the attribute allowed in the JTAMigratable section-
Issue Log for createDomain version 1.9.1 running WebLogic version <IP_ADDRESS>.0 offline mode:
SEVERE Messages:
1. WLSDPLY-05029: Name is not one of the attribute names allowed in model location topology:/Server/managed-server1/JTAMigratableTarget
2. WLSDPLY-05029: Name is not one of the attribute names allowed in model location topology:/Server/managed-server2/JTAMigratableTarget
3. WLSDPLY-05029: Name is not one of the attribute names allowed in model location topology:/Server/managed-server3/JTAMigratableTarget
4. WLSDPLY-20001: createDomain did not complete the operation because validation failed
Total:       WARNING :     0    SEVERE :     4


Updates the GS:Experiments document with the new GS-Experiments project

Updates the GS:Experiments tutorial with the project and data found in https://github.com/iterative/get-started-experiments

This doesn't contain many content changes except removing the warning that dvc exp push doesn't work without dvc exp apply.
Will be rebasing shortly.
Closes #2479

It has +200 -100 - it means it got bigger - any reason for this?
The intention behind get started to keep it as simple and as short is possible. We should fight for lines here :)

@iesahin please make it from a branch (not a fork, so that it is deployed into a preview env automatically)


Multiblock Structures do not unload or load correctly.

They seem to load most of the time, but dont unload properly. Upon forcing them to unload, loading loads, unloads, then loads the structure again. This needs to be fixed.

Fixed


The .read and .rebuild APIs will stop working in the next Broccoli version

These notices are being logged on build after adding the plugin
[API] Warning: The .read and .rebuild APIs will stop working in the next Broccoli version
[API] Warning: Use broccoli-plugin instead: https://github.com/broccolijs/broccoli-plugin
[API] Warning: Plugin uses .read/.rebuild API: Filter

Would this PR solve the issue ?

#1636 should solve that actually


Need SM mitm support

Problem Description

Concept: GmSSL is an open source cryptographic toolkit that provide first level support of Chinese national cryptographic algorithms,
The SM algorithms are becoming mandatory in China，you could find definition in rfc8998
I encountered a situation that i need to intercept the netflow-traffic in HTTPs acted as SM4_CBC， plus SM2 for key-exchange
When i was trying to us mitmProxy to intercept the flow，here came the error:

OpenSSL Error([('SSL routines', 'ssl3_read_bytes', 'sslv3 alert handshake failure')])

So I leave this message to seek help，
Proposal
I would like to advise to add the support of intercepting TLS site based on ShangMi (SM) Cipher Suites, which you can find in

rfc8998
https://github.com/guanzhi/GmSSL

Alternatives
I dont know，maybe I should fingure out a way of Browser-Based interception
Additional context / reference

https://tools.ietf.org/id/draft-ribose-cfrg-sm4-09.html
https://www.rfc-editor.org/rfc/rfc8998.html
https://github.com/guanzhi/GmSSL , a repo where you can find the implementation of SM4

We use OpenSSL under the hood for all cryptography operations (via the excellent cryptography / pyOpenSSL packages). Your best bet would be to install cryptography with an OpenSSL version that supports these ciphers (if that exists).

It's nothing we can really fix in mitmproxy, so I'll be closing this here. If you or anyone else manages to get this working, please feel free to leave a comment with details nonetheless. :)

Hi! Thanks to @hi-unc1e, touched important question: support of the national crypto standards. @mhils according to your recommends, i took openssl with GOST support (russian national crypto standard) and compiled python3 with GOST support. pyOpenSSL understood these types of crypto algorithms, but i saw in source code of mitm that in some places you bind to specific crypto algorithms like RSA. Is it possible to provide an interface to support national crypto standards and how can i help the project to achieve these extra functionalities?

Is it possible to provide an interface to support national crypto standards and how can i help the project to achieve these extra functionalities?

Your best bet here is to maintain your own fork, which is permitted by the mitmproxy license.


chore(main): release 0.0.30

:robot: I have created a release beep boop
0.0.30 (2024-08-11)
Other

satisfy ValidationRule (#323) (a318dfc)

Dependency Updates

deps: update golang.org/x/exp digest to 0cdaa3a (#322) (1b290d2)
deps: update module github.com/onsi/ginkgo/v2 to v2.20.0 (#321) (d7deabd)
deps: update module github.com/validator-labs/validator to v0.1.2 (#317) (a93cb70)
deps: update module github.com/validator-labs/validator to v0.1.3 (#325) (8f0afbb)

Refactoring

do not return an error from Validate (#319) (d48d5d9)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.0.30
:sunflower: