allow three access

for the case when the page using model-viewer needs three to do some other job, since it is already bundled with model-viewer - it would be a shame to have to download three.js twice.
I see somebody have thought about it before but having official support for this would be nice.

Agreed! I just need to find the proper way to expose it and ensure the bundler doesn't tree-shake anything out. For this reason, I think we'll make a separate bundle for this, like model-viewer-three.min.js.

@makc Have you looked at #3948? The proposal is to distribute an additional mv package without three.js at all - then you would pull that in with an import map along with whatever other code you need it for. Does that look like a workable solution for you?

@elalish that does sound reasonable, but then would you not have false bug reports in mv if the user imports incompatible three revision?

Yeah, but at least we aren't claiming to validate versions like with npm. I prefer no handrail to a handrail you can't trust. We'll just have to put it in the docs and remind people to post their versions in the issue template.

This happened as part of v3.2, try model-viewer-module.min.js, and follow the import map instructions at https://modelviewer.dev/examples/postprocessing/#setup


[WIP] Add Empty Help links/buttons

1)
On competition detail, could align this vertically with the other buttons?

2)
http://localhost:8000/tasks/ help icon goes to competition bundle wiki page, think it should go here:
https://github.com/codalab/competitions-v2/wiki/Task-&-Dataset-Management
3)
Queue management helper should link here:
https://github.com/codalab/competitions-v2/wiki/Queue-Management


Drop separate kernel package for firmware

Replacement for https://github.com/openSUSE/nvidia-driver-G06/pull/35 which for whatever reason it can not be re-opened.

A bit of editing in the text as I confused the MR with the open  driver.

Convinced. Let's do it. I'll just make a quick buildtest.

Convinced. Let's do it. I'll just make a quick buildtest.

Build test was successful! ;-)


Problem with SWI Prolog's new stable PPA version 9.0.0 (Linux Ubuntu)

Yesterday, SWI Prolog's stable PPA version was updated to version 9.0.0 (from v8.4.3) and now Popper does work:
$ python3 popper.py examples/alleven
[Thread 1 (main) at Fri Nov 25 10:52:17 2022] /build/swi-prolog-hvyroz/swi-prolog-9.0.0-1-g0757fd884/src/pl-fli.c:2637: PL_put_chars: Assertion failed: 0
C-stack trace labeled "assert_fail":
  [0] PL_scan_options() at ??:? [0x7f692f994a98]
  [1] PL_unify_mpq() at ??:? [0x7f692f951fdf]
  [2] PL_put_chars() at ??:? [0x7f692f97582d]
  [3] ffi_call_unix64() at ??:? [0x7f6941588dec]
  [4] ffi_call() at ??:? [0x7f6941587f55]
  [5] _call_function_pointer() at /home/hakank/python/Python-3.7.6/Modules/_ctypes/callproc.c:850 [0x7f693dce0079]
  [6] PyCFuncPtr_call() at /home/hakank/python/Python-3.7.6/Modules/_ctypes/_ctypes.c:4017 [0x7f693dcdd0c3]
  [7] python3(_PyObject_FastCallKeywords+0x92) [0x561a29bf4ea2]
  [8] python3(_PyEval_EvalFrameDefault+0x4935) [0x561a29c65e75]
  [9] python3(+0x1c4658) [0x561a29cbf658]
  [10] python3(+0x16526a) [0x561a29c6026a]
  [11] python3(_PyMethodDef_RawFastCallKeywords+0xe9) [0x561a29bf4529]
  [12] python3(_PyCFunction_FastCallKeywords+0x20) [0x561a29bf4420]
  [13] python3(_PyEval_EvalFrameDefault+0x4643) [0x561a29c65b83]
  [14] python3(_PyEval_EvalCodeWithName+0x2de) [0x561a29c60afe]
  [15] python3(_PyFunction_FastCallKeywords+0x1bc) [0x561a29bf607c]
  [16] python3(_PyEval_EvalFrameDefault+0x49eb) [0x561a29c65f2b]
  [17] python3(_PyObject_Call_Prepend+0x2db) [0x561a29bf68fb]
  [18] python3(+0x13aea9) [0x561a29c35ea9]
  [19] python3(+0x137b94) [0x561a29c32b94]
  [20] python3(_PyObject_FastCallKeywords+0x92) [0x561a29bf4ea2]
  [21] python3(_PyEval_EvalFrameDefault+0x4935) [0x561a29c65e75]
  [22] python3(_PyEval_EvalCodeWithName+0x6a3) [0x561a29c60ec3]
  [23] python3(_PyFunction_FastCallDict+0x300) [0x561a29b5a600]
  [24] python3(_PyEval_EvalFrameDefault+0x1bc7) [0x561a29c63107]
  [25] python3(_PyEval_EvalCodeWithName+0x6a3) [0x561a29c60ec3]
  [26] python3(_PyFunction_FastCallKeywords+0x248) [0x561a29bf6108]
  [27] python3(_PyEval_EvalFrameDefault+0x13ad) [0x561a29c628ed]
  [28] python3(_PyFunction_FastCallKeywords+0xf2) [0x561a29bf5fb2]
  [29] python3(_PyEval_EvalFrameDefault+0x64d) [0x561a29c61b8d]
  [30] python3(_PyEval_EvalCodeWithName+0x2de) [0x561a29c60afe]
  [31] python3(PyEval_EvalCode+0x23) [0x561a29c60813]
  [32] python3(+0x208f22) [0x561a29d03f22]
  [33] python3(PyRun_FileExFlags+0x9d) [0x561a29d042ed]
  [34] python3(PyRun_SimpleFileExFlags+0x1b6) [0x561a29d040f6]
  [35] python3(+0x1dfe44) [0x561a29cdae44]
  [36] python3(_Py_UnixMain+0x3c) [0x561a29cdaadc]
addr2line: DWARF error: section .debug_info is larger than its filesize! (0x93ef57 vs 0x530ea0)
  [37] __libc_start_main() at ??:? [0x7f6942d77083]
  [38] python3(_start+0x2a) [0x561a29cda9ba]
[1]    44398 abort (core dumped)  python3 popper.py examples/alleven

So it seems that there is a problem with the pyswip package (again), and I'm trying to find a way to downgrade to the previous SWI Prolog stable PPA version.
(I also tried to downgrade the pyswip version, but all the versions I tried - 0.2,9, 0..2.10, 0.2.11 - yield some error.)

I asked about downgrading at the SWI Prolog forum: https://swi-prolog.discourse.group/t/best-easiest-way-to-downgrade-to-version-8-4-3-on-linux-ubuntu-20-04/5966 .
For me it worked by downloading the appropriate .deb files from https://launchpad.net/~swi-prolog/+archive/ubuntu/stable/+build/24099974 (the focal distribution for Ubuntu 20.05) and then installing them in correct order:
sudo dpkg -i swi-prolog-nox_8.4.3-1-g10c53c6e3-focalppa2_amd64.deb
sudo dpkg -i swi-prolog-x_8.4.3-1-g10c53c6e3-focalppa2_amd64.deb
sudo dpkg -i swi-prolog_8.4.3-1-g10c53c6e3-focalppa2_amd64.deb

Even if this fix works, it's an issue that I hope will be fixed so we can use the current stable SWI Prolog version.

There is a simple fix that seems to solve the problem (which I reported in https://swi-prolog.discourse.group/t/best-easiest-way-to-downgrade-to-version-8-4-3-on-linux-ubuntu-20-04/5966/9), namely to change the pyswip source according to this diff:
diff --git a/pyswip/core.py b/pyswip/core.py
index 33f7035..0bb992f 100644
--- a/pyswip/core.py
+++ b/pyswip/core.py
@@ -584,7 +584,7 @@ PL_VERSION_VM               =6      # VM signature
 PL_VERSION_BUILT_IN    =7      # Built-in predicate signature

 try:
-    PL_version = _lib.PL_version
+    PL_version = _lib.PL_version_info
     PL_version.argtypes = [c_int]
     PL_version.restype = c_uint

So now Popper works with SWI Prolog version 9.0.0 (stable PPA version).
(This was inspired by the PR 133 at pyswip: https://github.com/yuce/pyswip/pull/133 )

Posting my simple solution here:
I faced the same issue on my Mac M1. When i upgraded Prolog I faced the same issue. Popper was not working any more.
I had installed pyswip through Homebrew. All I had to do was:
locate pyswip core.py file:
for me it was in /opt/homebrew/lib/python3.10/site-packages/pyswip
change PL_version = _lib.PL_version (in line 587)
to PL_version = _lib.PL_version_info
This got Popper working again
Solution inspired by (https://swi-prolog.discourse.group/t/best-easiest-way-to-downgrade-to-version-8-4-3-on-linux-ubuntu-20-04/5966/18)

@hakank @youssefmahmoud89
Thanks for posting this issue. The master branch of pyswip now works correctly with the latest version of Prolog.


[driverless] HP Color LaserJet M281 cannot print test page

Hi!
we have report in Fedora 29 (cups-2.2.10, cups-filters-1.20.3) https://bugzilla.redhat.com/show_bug.cgi?id=1694797 , which is about driverless HP printer (dnssd backend, ppd created by cups-filters generator based on IPP comm) cannot print test page from GNOME control center, but other files does not do any problems.
Jan (the reporter) provided logs
cups_journal.txt , ppd
HP-ColorLaserJet-MFP-M278-M281.ppd.txt , file, which goes to CUPS
jvlug-app.txt and file which goes to the printer
jvlug-printout.txt . Input file looks good to me, but output of filters is missing all text and evince spits out:
'some font thing failed'
According logs there were 2 used filters, bannertopdf and pdftopdf, both from cups-filters, but pdfinfo tells that creator of pdf is cairo... I'm not sure if those filters calls cairo (IMO they do not).
Would you mind looking into it?

For me it looks like that when your print job runs the bannertopdf filter that the filter is not finding the fonts for the text part of the test page.
Extracting text from your output PDF file one sees that all the text is actually contained in the file. Also evince complains about fonts when displaying it and displays it without text then.
Then mention of cairo in the PDF file can come from the template PDF file (default-testpage.pdf), perhaps this was created with cairo.
Please check whether for the filters called by CUPS all fonts are available.
Your journal of CUPS unfortunately shows only the irrelevant lines. It filters exactly the lines coming from the job. You need the lines of the CUPS error_log (or the journal) which start with "[Job " followed by a number (which is the job number). Perhaps you did the call of journalctl in a wrong way.
Please try to get these lines to find out whether perhaps bannertopdf gives a warning or an error and post this here.

I tried the newest cups-filters and it works there - probably when bannertopdf was rewritten it was fixed.


Does this tool have the ability to list digest without tags and delete them

This script has the ability to delete repo tags but would be nice if it could delete repo digest without tags so that garbage-collector can clean up the associated blobs to regain disk space.

This tool just calls Harbor API, so if the server side support this function, our script will be really easy to add this feature.

Currently  our private registry is harbor 1.3.0.    And need a way to quickly and easily clean-up untagged digest so that Garbage collector can clean-up the blobs they reference.   The following link describes the issue with registry cleanup.
Garbage collect untagged manifests
https://github.com/docker/distribution/issues/1844
Found the following script that will find all untagged digest but doesn't authenticate with harbor docker private registry.  It would be awesome if harbor-client CLI would provide this function since it already provides delete image tags.
Docker Registry(v2) Manifest Cleanup
https://github.com/mortensteenrasmussen/docker-registry-manifest-cleanup


question

what does it mean by "size of windows" in the config notepad, does that mean the resolution?

Yes, It is the overall size of the Detection Area on the Primary display, This determines how large the detection area is, You can view the detection area on the Debug Window that pops up after starting the cheat.


Update spring-context, spring-core to 5.3.14

Updates

org.springframework:spring-context
org.springframework:spring-core

from 5.3.13 to 5.3.14.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.springframework" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #1145.


Limiting Queries Might be required ? for number of realm objects over 500K

Goals

I have a table view and I created 500K transaction objects.
I did a simple realm.objectsAll() on the transactions.
It blocked the main thread UI.
I used global queue and a thread reference and it made no difference when having it change over to a different thread.
I want it not to block the main thread.
From what I understand, reading about limiting queries, I should read maybe the first 10 rows before I have a tableview access it ?
Expected Results

For it not to block the main thread and ramp up memory to 300 mb
Actual Results
It ramped up memory to 300mb and brought it back down
Steps to Reproduce

Create a 500K transactions with 5 fields, make them strings.
Then create a list or table view and load it. It should block the main ui even if you query using a thread reference.
Code Sample
Ill provide a code sample later.
Version of Realm and Tooling

Realm framework version: ?
3.3.0
Realm Object Server version: ?
Xcode version: ?
latest
iOS/OSX version: ?
ios 11.0
Dependency manager + version: ?

@ArEnSc Is this synthetic test, or do you really need to get 500k objects at once?

Closing this issue due to no response. Feel free to reopen if additional information can be provided.


pls update, thanks

update it

@undersquire

I don't even use VSCode anymore 💀

what do you use?

also vscode is the only one I can link to using vscode.dev

@undersquire can I publish it, asking for permission?

what do you use?

I use Helix. And yes you can do whatever using this theme, you can continue the project if you want.


1.19.2 support

Hey, first I want to say thank you so much for making the code public where you added support for more recent versions of ShopChest.
It would be amazing if you could add support for "DECENT HOLOGRAMS" the same way they work with Holographic Display since its a more active plugin and has a lot more features that holographic display does not offer and its just more clean in a lot of ways.
Decent Holograms spigot page: https://www.spigotmc.org/resources/decent-holograms-1-8-1-19-papi-support-no-dependencies.96927/
Kind Regads,
Niko

Hi!
Making the code public seemed logic as the original plugin was public as well. But you're welcome. :D
For your suggestion, what do you mean exaclty by "DecentHologram support" ? I don't see the link between this plugin and ShopChest as it's a Hologram plugin and ShopChest handle that by its own.

For 1.19.2 support, it will be released when I will be back home (in 4 or 5 days)

Oh, sorry my bad for a second thought it was linked to that but later figured out it was the 1.19.2 that was messing with the startup. Ty for the quick reply.

Done


Everything Plugin doesn't detect Everything 1.5a

Microsoft PowerToys version
0.62.1
Running as admin

[ ] Yes

Area(s) with issue?
PowerToys Run
Steps to reproduce
Everything 1.5a isn't detected! it is already a very stable version with a lot of features and bug fixes and I think it should be supported at this stage.
✔ Expected Behavior
find files via Everything Plugin in PowerToys Run
❌ Actual Behavior
https://i.imgur.com/cpcDegI.png
Other Software
VoidTools Everything 1.5a (download from the forum thread)

that plugin is a community based plugin.  We do not ship with it.  please ping the author of it.

I thought he will get notified


Inefficient desugaring for rewrite

We desugar code like (rewrite (Add x y) (Add y x)) into something like:
(rule ((= e (Add x y))) ((union (Add y x) e)))

But  using union is only needed if the right-hand side of a rewrite is an identifier. When it's an expression, we could do:
(rule ((= e (Add x y))) ((set (Add y x) e)))

This should be safe, but it gives egglog less work to do: if (Add y x) is in the database already, setting it will call union anyway as part of the merge process. If it isn't we skip creating a new noncanonical id that rebuilding has to clean up.
On the following program, this is a significant speedup:
(datatype Num (N i64) (Add Num Num))
; instead of (rewrite (Add a b) (Add b a))
(rule ((= e (Add a b))) ((set (Add b a) e)))
; instead of (rewrite (Add a (Add b c)) (Add (Add a b) c))
(rule ((= e (Add a (Add b c)))) ((set (Add (Add a b) c) e)))

(let _lit0 (N 0))
(let _lit1 (N 1))
(let _lit2 (N 2))
(let _lit3 (N 3))
(let _lit4 (N 4))
(let _lit5 (N 5))
(let _lit6 (N 6))
(let _lit7 (N 7))
(let _lit8 (N 8))
(let _lit9 (N 9))
(let _lit10 (N 10))
(let _lit11 (N 11))
(let _v0 (Add _lit0 _lit1))
(let _v1 (Add _lit2 _v0))
(let _v2 (Add _lit3 _v1))
(let _v3 (Add _lit4 _v2))
(let _v4 (Add _lit5 _v3))
(let _v5 (Add _lit6 _v4))
(let _v6 (Add _lit7 _v5))
(let _v7 (Add _lit8 _v6))
(let _v8 (Add _lit9 _v7))
(let _v9 (Add _lit10 _v8))
(let _v10 (Add _lit11 _v9))
(let _r0 (Add _lit11 _lit10))
(let _r1 (Add _r0 _lit9))
(let _r2 (Add _r1 _lit8))
(let _r3 (Add _r2 _lit7))
(let _r4 (Add _r3 _lit6))
(let _r5 (Add _r4 _lit5))
(let _r6 (Add _r5 _lit4))
(let _r7 (Add _r6 _lit3))
(let _r8 (Add _r7 _lit2))
(let _r9 (Add _r8 _lit1))
(let _r10 (Add _r9 _lit0))
(run 10000)
(check (= _r10 _v10))

This program takes 22.5 seconds to saturate on my machine. The usual rules for associativity and commutativity take 29s.

Unfortunately using set on datatypes is going to be disallowed with the semantics we decided on recently.
Perhaps query compilation can recognize this optimization later in the pipeline?

I thought set would still be allowed, we just don't get lookups after a set?

set should be allowed for functions with custom merge functions, but constructors like Add should not be set, only unioned


OZ-560: Rename project,Added E2E tests and registration Opt In

This is a PR for the work in https://mekomsolutions.atlassian.net/browse/OZ-560. It introduces a number of changes to the original project;

Container registration is now opt-in
Upgrade a number libraries
Adds E2E Tests

@enyachoke  could you provide some instructions to test?
The Docker image mekomsolutions/container2sul does not seem to be available locally so how do I build it?

@enyachoke could you provide some instructions to test? The Docker image mekomsolutions/container2sul does not seem to be available so how do I build it?

@rbuisson This will be available after we merge https://github.com/mekomsolutions/container-to-consul/pull/1/files#diff-5c3fa597431eda03ac3339ae6bf7f05e1a50d6fc7333679ec38e21b337cb6721R13

Yes I know. So what are the instructions?
docker build first? (what exact command). And then what?


test: declaring and deploying new classes

Following workflow should be investigated:

Creating account smart contract
Creating account in wallet
Declaring account
Deploying account
declaring new class
deploying new class

Closed by https://github.com/eigerco/beerus/issues/694


Exoplayer error and Music player not working

No video is getting played with exoplayer, there is a PlatformException error. Also when try to play audio, no audio is getting played, it jest shows duration as infinity. I also saw that you have added BetterPlayer so does the exoplayer use betterplayer plugin or video_player plugin. If it's using video_player can you please tell me how to shift it to betterplayer. Also there is mpv player file, so you are gonna add mpv player support?
Is there a telegram group for this project?

Hello,
On which platform do you use the app ?
Video_player is only used for the web version (which very WIP) else on android or IOS better_player is used.
There was an MPV plugin once (https://github.com/alexmercerind/libmpv.dart 404 now) but it was barebone. I don't have time nor the resources to develop an MPV player on my own.
No telegram, it's just a hobby project nothing too serious.

I am receiving the above error for any video I try to play. It's not an unsupported video in better_player because I tried playing same video using direct link and it plays and it also plays on jellyfin original app on exoplayer.

On music player playing any song I get a player as above (1st photo on home screen) and on clicking three dots (2nd photo is shown which shows infinite time)
Device: Realme GT Neo 2
Android version : 12
Ya I understand this project is just hobby, but still maybe a telegram group or discord group might be good for communication.

Any Solution?

It's a strange bug as it works on One plus 6T.
But right now I'm reworking the whole to go away from the shitty spaghetti code. When it's done I'm going to look these issues.


Detach the test build branch from parent

Without that, any merge will cause all running jobs to break.

+1


trusted_user -> published defunct

Seems like isn't working nowadays, perhaps the docker image is a bit outdated and requires a refresh.
[2020-11-04 11:42:23,157] INFO in app: Loaded trusted user list
/lib/python3.7/site-packages/wrapt/wrappers.py:603: DeprecationWarning: Call to deprecated method __init__. (Please use ExpandedPyMISP instead (requires Python 3.6+). This class will be an alias of ExpandedPyMISP early 2020 and your code will most probably fail.)
  args, kwargs)
/lib/python3.7/site-packages/wrapt/wrappers.py:603: DeprecationWarning: Call to deprecated method get_recommended_api_version. (Use ExpandedPyMISP.recommended_pymisp_version) -- Deprecated since version 2.4.110.
  args, kwargs)
WARNING [api.py:112 - __init__() ] The version of PyMISP recommended by the MISP instance (2.4.133) is newer than the one you're using now (2.4.117). Please upgrade PyMISP.
/lib/python3.7/site-packages/wrapt/wrappers.py:603: DeprecationWarning: Call to deprecated method get_live_describe_types. (Use ExpandedPyMISP.describe_types_remote) -- Deprecated since version 2.4.110.
  args, kwargs)
/lib/python3.7/site-packages/wrapt/wrappers.py:603: DeprecationWarning: Call to deprecated method search. (Use ExpandedPyMISP.search) -- Deprecated since version 2.4.111.
  args, kwargs)

A fresh install with latest package+code updates fixed this. thx!


NullPointerException in DockerClientResolver when running multiple Gradle BuildImageTasks in parallel

Environment:

Jib version: 3.3.1
Build tool: Gradle 8.0.1
OS: Linux

Description of the issue:
We have multiple projects in our Gradle build which have the jib plugin applied to them and we are using parallel execution. This means that multiple instances com.google.cloud.tools.jib.gradle.BuildImageTask can execute in parallel. When that happens we are sometimes seeing the following exception (stacktrace truncated to significant parts only):
  Caused by: java.lang.NullPointerException: Cannot invoke "java.lang.ClassLoader.getParent()" because "this.currentLoader" is null
    at com.google.cloud.tools.jib.docker.DockerClientResolver.resolve(DockerClientResolver.java:38)
    at com.google.cloud.tools.jib.api.JibContainerBuilder.<init>(JibContainerBuilder.java:104)
    at com.google.cloud.tools.jib.api.Jib.from(Jib.java:87)
    at com.google.cloud.tools.jib.api.JavaContainerBuilder.from(JavaContainerBuilder.java:182)
    at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.getJavaContainerBuilderWithBaseImage(PluginConfigurationProcessor.java:543)
    at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.processCommonConfiguration(PluginConfigurationProcessor.java:425)
    at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.processCommonConfiguration(PluginConfigurationProcessor.java:490)
    at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.createJibBuildRunnerForRegistryImage(PluginConfigurationProcessor.java:309)
    at com.google.cloud.tools.jib.gradle.BuildImageTask.buildImage(BuildImageTask.java:116)

Expected behavior:
No NPEs being thrown when multiple instances com.google.cloud.tools.jib.gradle.BuildImageTask execute in parallel.
Steps to reproduce:
Run multiple instances of com.google.cloud.tools.jib.gradle.BuildImageTask in parallel. This is a concurrency issue so it's not always reproducible.
Additional Information:
I think that com.google.cloud.tools.jib.docker.DockerClientResolver#resolve is not thread safe because yet it can be called from multiple threads by the Gradle plugin when running with parallel execution enabled. It uses a reference to a static instance of ServiceLoader which according to its javadoc is not thread safe:

Instances of this class are not safe for use by multiple concurrent threads.

Would a PR simply changing com.google.cloud.tools.jib.docker.DockerClientResolver to instantiate a new instance of ServiceLoader per resolve() call be considered as a fix for this, @suztomo? I'd be willing to contribute that.

Another stacktrace with a slightly different error caused by what I believe is the same issue:
    Caused by: java.lang.ArrayIndexOutOfBoundsException: Index 2 out of bounds for length 2
12:56:37       at com.google.cloud.tools.jib.docker.DockerClientResolver.resolve(DockerClientResolver.java:38)
12:56:37       at com.google.cloud.tools.jib.api.JibContainerBuilder.<init>(JibContainerBuilder.java:104)
12:56:37       at com.google.cloud.tools.jib.api.Jib.from(Jib.java:87)
12:56:37       at com.google.cloud.tools.jib.api.JavaContainerBuilder.from(JavaContainerBuilder.java:182)
12:56:37       at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.getJavaContainerBuilderWithBaseImage(PluginConfigurationProcessor.java:543)
12:56:37       at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.processCommonConfiguration(PluginConfigurationProcessor.java:425)
12:56:37       at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.processCommonConfiguration(PluginConfigurationProcessor.java:490)
12:56:37       at com.google.cloud.tools.jib.plugins.common.PluginConfigurationProcessor.createJibBuildRunnerForRegistryImage(PluginConfigurationProcessor.java:309)
12:56:37       at com.google.cloud.tools.jib.gradle.BuildImageTask.buildImage(BuildImageTask.java:116)

Hey @erdi, thanks for the report and investigation! I think you’re right, looks like the iterator usage of ServiceLoader runs into a similar multithreading limitation as reported per https://bugs.openjdk.org/browse/JDK-8230843.
Curiosity: how often were you observing this issue in parallel builds, and were you able to verify in some way that moving the ServiceLoader.load() call into the static method resolved this issue? (I'm guessing the rationale is that all instances of DockerClientResolver share the static field dockerClients in the current implementation, causing the race condition, but moving it to a local variable in the static resolve() method would have each thread calling this method store this variable in its own stack instead?)

Thanks for getting back to me, @emmileaf.
The most frequent it failed for us recently was 3 times in 9 builds, but on average you can expect one failure in every 100 builds. It's actually hard to give you a true frequency as it requires scouring through failed build logs to confirm that the failure was due to this problem, but it happens frequently enough for us to notice it's a thing and thus report it.
I did not test this fix because I would need to fork, build and publish a custom version of the plugin and then apply it to our build. But I believe that It's based on logic and strong evidence:

odd stacktraces point at concurrent usage of a ServiceLoader instance
it's clear that the code in question can be ran concurrently in parallel builds
ServiceLoader is clearly not thread safe as stated in its javadoc
use an instance of ServiceLoader per a call to DockerClientResolver.dockerClients() rather than sharing an instance between all of them to avoid using a ServiceLoader instance concurrently which is what you are referring to by

I'm guessing the rationale is that all instances of DockerClientResolver share the static field dockerClients in the current implementation, causing the race condition, but moving it to a local variable in the static resolve() method would have each thread calling this method store this variable in its own stack instead?

Thanks for the additional info! It's helpful to know roughly how frequently the issue is encountered, and the proposed patch/rationale makes sense to me. I’ll go ahead and merge the PR.
A thought for the future if the error still persists: since the exceptions seem to be thrown from iteration over dockerClients, it could be worth adding a try/catch around the iteration and have it return Optional.empty(), or retry in some way upstream. DockerClientResolver was introduced to enable usage of custom DockerClient implementations (which I'm guessing you are not using in your builds, but please correct me otherwise), and Jib should fall back to its default implementation of CliDockerClient if resolution is unsuccessful instead of failing the build.

Thanks for approving and merging, @emmileaf.
Do you know if a release is planned any time soon? It would be great to be able to benefit from the two contributions I've made recently, #3993 and #3936.

A thought for the future if the error still persists

I'm fairly sure that this particular issue will be solved by the fix. A ServiceLoader instance was clearly used concurrently and no longer will be so there is no longer an obvious reason for the iteration over it to fail.

Oh I see a release might be coming! 🎉
https://github.com/GoogleContainerTools/jib/releases/tag/v0.24.0-core

jib-core 0.24.0 (and jib-gradle-plugin 3.3.2 for your use case) has been released with this fix!

That's great news, thanks again, @emmileaf!


Assignment3

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
adding my solution to the third homework, regarding python.
What did you learn from the changes you have made?
to work with data files and numpy
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
not really. The approach is pretty clear from the assignment
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
not much.
How were these changes tested?
Run the code on my machine and worked well
A reference to a related issue in your repository (if applicable)
Checklist

[X] I can confirm that my changes are working as intended

Hi @anjali-deshpande-hub, Thanks for the feedback. I've created a new pr with the changes. Please, take a look and let me know.
Thank you.


Path for pytorch 2.4 release

Comment:
I've got users who want pytorch3d on conda to have support for pytorch 2.4, so I'd like to understand the "process" of how this comes about.
Here's my undersatnding, please let me know if this sound correct:

A new version must first be pushed to pytorch-cpu-feedstock, and it seems this is WIP in https://github.com/conda-forge/pytorch-cpu-feedstock/pull/248
Next a PR in the conda-forge-pinning-feedstock repo must adopt this new version, e.g. for 2.3: https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/5895
The @regro-cf-autotick-bot should then automatically put up a PR for an updated pytorch version for pytorch3d e.g. for 2.3: https://github.com/conda-forge/pytorch3d-feedstock/pull/12
Once accepted, a new release (same pytorch3d version as already released) will be built and uploaded to conda repos

That all sound about right?

Yes that’s correct


Release 0.11.0

It's close to that time again.
It is:

about the be the first of the month
we've gone more than 30 days without a release

Looking at the changes, 0.11.0 seems to be the appropriate version.
Anyone have time to do this in the next few days?

Since #1521 temporarily removed support of GCC 4.7 and 4.8, we might want to delay that release until support is restored. I'm working on implementing the algorithm discussed in #1521, it should be ready in the next few days.

@Praetonus sounds good to me.

@Praetonus @jemc We ready to do this release?

@SeanTAllen Apparently https://github.com/ponylang/ponyc/pull/1610 broke the build for Clang 3.5. It should be trivial to fix, can we hold off the release until that's resolved?

Yup.

@Praetonus has the clang 3.5 issue been resolved?

@SeanTAllen yes.

Ok, so @jemc @Praetonus shall i do a release this weekend?

No objections from me.

I'm going to assume that 1 ok is enough. TravisCI and Appveyor are all good. Going to start the release.

@Theodus i'm going to assume the release script wasn't tested on OSX? because it errors out on me...
sed: 1: "CHANGELOG.md": invalid command code C

@Theodus it appears the sed usage is non portable:
http://stackoverflow.com/questions/4247068/sed-command-with-i-option-failing-on-mac-but-works-on-linux

@Theodus I pushed a fix for this. Its not pretty but...
https://github.com/ponylang/ponyc/commit/2aaa174537df8d3b166a896ed5dd0bc3947a2040
Something we need to be aware of going forward.
Related: the differences between GNU and BSD said are awful. Ugh.

Using c1a87a0f48e8a40747b52bb5c449e57fdb0da64a as golden commit

Blessing 4ccafba1bfc230dc8d5e00a092cd133d50e80678

UPDATE: apparently that didnt work, i still end up with an error, working on it.

@Theodus i addressed by making GNU sed required. Kind of a pain but it works and I don't know sed and couldn't make the script portable otherwise:
https://github.com/ponylang/ponyc/commit/21d37aa2fed6f5d7e6deff292ef863f6b1fe2e8d

Release is underway

release branch recreated. VERSION and CHANGELOG updated on master.

homebrew PR opened:
https://github.com/Homebrew/homebrew-core/pull/10899

@stefantalpalaru release is underway.

The only update standard library docs on release task successfully executed. First time since the change, just wanted to note that all is in fact, good on that front.

Windows, RPM and Debian versions are available in Bintray.
Waiting on Homebrew.
Does anyone know why the Windows version creates two archives whereas RPM and Deb create one?
@killerswan ? ^^

Homebrew is done (damn that was fast).
The release process change over there, so I might need to update release docs a little.
I'll send out release notice email etc after I make myself some food.

Release notice sent. Only thing outstanding is Gentoo update that @stefantalpalaru maintains. I assume he still is and will leave this open for now.

Gentoo ebuild updated. I'll make a PR with the fix for linking with "--as-needed".

Awesome. Thanks @stefantalpalaru.

re: duplicate windows entries, it appears that setting the tag causes a second appveyor build...


Fix LVT SMAP readers

HDF5 is listed as an optional library in the LVT documentation, but LVT would fail to compile without it.
Change in datastreams/SMAPTB/readSMAPTBobs.F90:

For-loop at line 350 of read_SMAPTB subroutine moved inside if (defined USE_HDF5) block

After making the above fix, compilation failed again due to similar errors in datastreams/SMAP_L3TB/readSMAP_L3TB.F90 and datastreams/SMAPvod/readSMAPvodobs.F90. The fixes were simple:

Moved variable declarations for source and filename above if (defined USE_HDF5) which is consistent with readSMAPTBobs.F90

LVT now compiles successfully without HDF5 on Intel and GNU compilers.
Resolves #578

These changes look good to me.

Thanks @dmocko I'll go ahead and merge.
And thanks to @rfun for reporting this issue.


Swapping RGB <-> DarkRGB, replacing darkblue

Fixing #1310.
Red swapped with Darkred, Green with DarkGreen, Blue - with DarkBlue, and DarkBlue replaced with more suited #002173
Current colors:
Red: http://www.colorhexa.com/c80032 #c80032
Green: http://www.colorhexa.com/00c800 #00c800
Blue: http://www.colorhexa.com/6464ff #6464ff
DarkRed: http://www.colorhexa.com/ff0000 #ff0000
DarkGreen: http://www.colorhexa.com/00ff00 #00ff00
DarkBlue: http://www.colorhexa.com/0000ff #0000ff
Fixed colors:
Red: http://www.colorhexa.com/ff0000 #ff0000
Green: http://www.colorhexa.com/00ff00 #00ff00
Blue: http://www.colorhexa.com/0000ff #0000ff
DarkRed: http://www.colorhexa.com/c80032 #c80032
DarkGreen: http://www.colorhexa.com/00c800 #00c800
DarkBlue: http://www.colorhexa.com/002173 #002173

The thing is that the "Fixed" colors are very hard to read on graphs.

let's close this then :)


Memory Leak Fix & VMP conflict on 1.20.1 fabric

Describe the bug
Game in 1.20.1 crashes with only both the latest memory leak fix mod (1.1.4) + VMP (0.2.0+beta.7.102) and the associated fabric apis.
To Reproduce
Steps to reproduce the behavior:

Get fabric 1.20.1 loader and apis
Get memory leak fix + very many players

Runtime info (please complete the following information):

OS: windows
Minecraft version: 1.20.1
Mod version: 0.20+beta.7.102

Crash reports / logs
https://pastebin.com/raw/F8X1SYaV
Checklist

[x] I am using the official version of the mod.
[x] I tried the latest development version but the issue persists.
[x] I searched for similar open issues and could not find an existing bug report on this.

Additional context
This seems to only occur after the recent updates in memory leak fix, it occurs with both 1.1.4 and 1.1.3 of memory leak fix, but 1.1.2 works fine. Because the logs outputs an error from vmp, i thought to report here, but its a memory leak fix issue, lmk, and ill start one up there too.

It seems that you are trying to run a 1.17 version of memoryleakfix on 1.20.1.

memory leak fix has always been labelled as 1.17+?

And the version is supported as so on modrinth.

^ For version 1.1.3 it's clearly stated to support 1.20.x as well, and that still results a crash.
The only compatible version as of now is 1.1.2.

From the error it is clearly a version mismatch. But please try reproduce without VMP.

Memory fix leak 1.1.4 seems to be working fine though without VMP, even with other mods and various other major optimization mods.
This might be more of an issue from memory fix leak's side then? If so ill redirect the report there.


Sort out all the "convert" operations

We should inventory all the "convert" operations.
If necessary, we can come up with some sort of convention, or possibly more than one convention, and rename them for consistency.

https://github.com/Lokathor/safe_arch/blob/master/nomoj.txt


Added support for endorsed responses (answers)

Fixes: https://openedx.atlassian.net/browse/MA-1186
Updated UI for Question type thread:

@1zaman @bguertin @BenjiLee plz review

:+1: Looks good. Could you just add a few pixels of padding between the check mark and the word "Answer"? If you look at iOS you can see there's a little space between. Probably like 4sp or so.

@bguertin i've updated the screenshots in my first comment.
Also, I moved the drawable addition code to constructor instead of the binding function as an optimization.

@@            master    #536   diff @@
======================================
  Files          471     471
  Stmts        21846   21865    +19
  Branches      3165    3166     +1
  Methods          0       0
======================================
+ Hit           2947    2951     +4
+ Partial        378     377     -1
- Missed       18521   18537    +16

Review entire Coverage Diff as of 1d65c12

Powered by Codecov. Updated on successful CI builds.

:+1:

:+1:


Keep adress-info in form after submitting

Hi,
we will use the geoform-template for a public participation process where useres can do several submissions. For each submission adress-informations is required. When a user wants to submit several statements it is not userfriendly that he has to enter the same adress-information after submitting the data. Is it possible (e.g. via cookie...) to keep data of certain fields even after pressing the submit-button so that the user doesn't need to enter these data again when fullfilling a second form?

Thanks @STGiese we'll see if we can work something like this into the next version.


Error with turnip predictions

Things to check

Have you forced a refresh in your browser (e.g. ctrl+F5 in Chrome/Firefox)?

yes

Have you made sure the first time buyer option is correct? If you're unsure, try it both ways

yes

Have you time-travelled this week? Travelling backwards resets the prices, and therefore you must not put prices in from both before & after the time-travel

no

Describe the bug
Price estimates are not presented
To Reproduce
Steps to reproduce the behavior:
First-Time Buyer: No
Previous Pattern: Large Spike
price of turnips this week: 103
Monday

AM: 81
PM: 79

Tuesday

AM: 76
PM: 73

Wednesday

AM: 87
PM: 163

Permalink to your prices
Link
Expected behavior
Price estimates are presented
Screenshots

Desktop (please complete the following information):

OS: [Windows 10]
Browser [Chrome]
Version [130.0.6723.93]

Smartphone (please complete the following information):

Device: [Xiaomi Poco X3 Pro]
OS: [Android 12]
Browser [Chrome]
Version [130.0.6723.86]

Additional context
Using the same values in the Stalk Market Wizard gives a prediction (I don't know if I can put another external tool)

Another week, no prediction
https://turnipprophet.io?prices=<IP_ADDRESS>.........&pattern=1

At least this one give me a prediction
https://ac-turnip.com/share?f=99-93-65-76-62-107-100-129-66-74

Another week, no prediction
https://turnipprophet.io?prices=<IP_ADDRESS>.68........&pattern=0


Cannot download from Baidu

Hi
Can you please share the data and the pretrained model on GoogleDrive, DropBox, Box or any other cloud service.
Unfortunately, Baidu does not work so great in the west.
Best Regards
Wajahat

chrome browser plugin solved the problem


[microNPU] Add support for pack and unpack

Pack is represented by a series of expand_dims operations followed by a concatenate in Relay. Unpack is represented by a split followed by a series of squeeze operations in Relay. This PR legalizes expand_dims and squeeze to reshape operations while making use of existing legalization techniques for split and concatenate so that pack and unpack can be offloaded to the NPU.
cc @manupa-arm @ekalda @jacobbohlin @NicolaLancellotti @dchauhan-arm @mbaret

Thanks @lhutton1 . this is merged now!


Change invalid cert API to match native-tls

Summary

Changes the API around disabling the various kinds of cert validation
Fixes the docstring for completely disabling certificate validation

Details
This closely matches the API exposed from native-tls, and I think it ends up being more ergonomic for the end user.
Rather than
let mut clientbuilder = reqwest::ClientBuilder::new();
if insecure {
    clientbuilder.danger_disable_certs_verification();
}
let client = clientbuilder.build().unwrap();

one can simply
let client = reqwest::ClientBuilder::new()
    .danger_accept_invalid_certs(insecure)
    .build().unwrap();

If we are worried about backwards incompatibility with this change, we can add a helper function for danger_disable_hostname_verification() to maintain the old API for existing users.

Thanks!


Use forked branch for Svelte

Code changes

[x] Change Svelte to use the the forked branch with Aaron's fix.

License
I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Yarn grabs the github package in the original files without the compiler.js, which caused the failed build.
Tested that yarn Version 2 or 3 will fix the build issue, using npm grabbing the package would also works.
However, we are using yarn in vercel's runtime.

@yifanplanet does that mean that the only fix is to upgrade yarn on vercel?

@yifanplanet does that mean that the only fix is to upgrade yarn on vercel?

My suggestion is to override the Install Command in Vercel to use npm install


CI: sync PR 2858 to dev

Description:
Ports changes from https://github.com/casper-network/casper-node/pull/2858 -> dev
Changes:

Removes the use of cachepot in package and tag pipelines

Ticket:

https://app.zenhub.com/workspaces/cn-sre-60d363546afb85000e491ff6/issues/casper-network/sre/384

Related:

https://github.com/casper-network/casper-node/pull/2854
https://github.com/casper-network/casper-node/pull/2858

bors r+


Nvidia gtx 1050 render performence is much slower than intel integrated graphics.

I am referring to the example which loads a terrain model from a heightmap png, I have found that the rendering which occurs on my intel integrated graphics is 2 times faster than the rendering on my gtx 1050. I have had no issues with my laptop prior to this, I use my laptop for gaming, and games run completely fine.

Hi @isubasinghe, that's a very weird issue... please, could you provide more information?
When using GTX1050, is VSync activated in Graphic Card options?
What is the framerate in both cases, maybe 60 fps and 30 fps?
Are you setting a specific framerate with SetTargetFPS()?
What is the CPU performance you get in both cases?
I need some more info to track this issue...

Ok this is very weird but now I am getting good performance on the gtx, way better than intel integrated. My laptop may just have needed a restart?
That being said there is a another issue but i think it is small, compared to the is one anyway.
On intel integrated graphics, the heightmap renders like this

However on nvidia it renders like this

Vsync is not enabled on code. I am unsure how to check Graphic card options.
Irrelevant here but framerate is capped to 60 fps which intel and nvidia both meet.
The cpu performance is about the same at 19%.

`
int main()
{
int screenWidth = 1920;
int screenHeight = 1080;

InitWindow(screenWidth, screenHeight, "raylib [models] example - heightmap loading and drawing");

Camera camera = {{ 18.0f, 16.0f, 18.0f }, { 0.0f, 0.0f, 0.0f }, { 0.0f, 1.0f, 0.0f }, 45.0f };

Image image = LoadImage("resources/heightmap.png");
Texture2D texture = LoadTextureFromImage(image);

Mesh mesh = GenMeshHeightmap(image, (Vector3){ 16, 8, 16 });
Model model = LoadModelFromMesh(mesh);

model.material.maps[MAP_DIFFUSE].texture = texture;
Vector3 mapPosition = { -8.0f, -2.0f, -8.0f };

UnloadImage(image);

SetCameraMode(camera, CAMERA_ORBITAL);  // Set an orbital camera mode

SetTargetFPS(60);

// Main game loop
while (!WindowShouldClose())            // Detect window close button or ESC key
{

    UpdateCamera(&camera);              // Update camera

    BeginDrawing();

        ClearBackground(RAYWHITE);

        Begin3dMode(camera);

            DrawModel(model, mapPosition, 1.0f, BROWN);

            DrawGrid(20, 1.0f);

        End3dMode();

        DrawTexture(texture, screenWidth - texture.width - 20, 20, WHITE);
        DrawRectangleLines(screenWidth - texture.width - 20, 20, texture.width, texture.height, GREEN);

        DrawFPS(10, 10);

    EndDrawing();

}

UnloadTexture(texture);
UnloadModel(model);

CloseWindow();

return 0;

}
`

I see, thanks for the updated information! I already know what happens! Just remembered I got that same problem in the past... which version of raylib are you using?
About the different framerates, that's related to Sleep() method granularity in Windows, depending on the system load, it can take longer than expected, capping your framerate to 30 fps, it's really a lottery. Just reviewed this issue several times, related on this forum post and timming system reviewed on commits https://github.com/raysan5/raylib/commit/d1c9afd1d8ae4ae3e075b117fff7a5a77f3c4d60, https://github.com/raysan5/raylib/commit/b5dd18a70c6c660c727fd1c18b13222678974a74 and https://github.com/raysan5/raylib/commit/83aba22e494ffbc78cb9cda6a8e39e82963026f4
How big is the map you're rendering?
The color issue is related to models diffuse color and shader location... actually it depends on the graphic card and the drivers behaviour, just noticed it some days ago and corrected on commit https://github.com/raysan5/raylib/commit/81518ccd130cf56c87e22800f80ffffacb2f39c3.
Please, could you try using latest raylib develop branch? It should solve all those issues...

@raysan5 I have no idea about the version I just cloned from github about 10 days ago. Ah yeah that makes, sense I had some issues with windows' sleep function before, I just assumed that there might be libraries that fixed this. Also the map I was rendering was a heightmap from a png pf size 256 x 256. Alright I will give the develop branch a shot. I will close this issue as well.


Revert "fix(pool): always ping connection on release to see if it's still viable"

This reverts commit 0ed524d65c2a3ee2e2a6706910b85bf2bb72115f.
Unfortunately #1025 broke code that uses a SqlitePool, especially when using a max_connection count of 1.

I would prefer to find the underlying issue rather than reverting the fix as it probably just exposed another bug. SqliteConnection::ping() is a no-op which means it should be instantly released to the pool anyway. Could this possibly have been caused by #1080?

I bisected things, and this is the exact commit that breaks things

This commit may be triggering a bug I just spotted in DecrementSizeGuard::drop() because it changes the timing of release() by always spawning it as a background task: https://github.com/launchbadge/sqlx/blob/master/sqlx-core/src/pool/inner.rs#L402-L407
If the waker at the head of the queue has no strong refcounts left then this will return instead of attempting to wake the next one. With a pool of size 1 this means that any waiting tasks will stall until they time out.

This commit may be triggering a bug

I see that of course makes sense

fixed on master


feat: change pattern from cdn to seed peer

Description

Change pattern from cdn to seed peer.
Remove kustomize shell.

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1345 (6200fb0) into main (0ed03d1) will decrease coverage by 0.40%.
The diff coverage is 0.00%.

:exclamation: Current head 6200fb0 differs from pull request most recent head d60652b. Consider uploading reports for the commit d60652b to get more accurate results

@@            Coverage Diff             @@
##             main    #1345      +/-   ##
==========================================
- Coverage   45.84%   45.44%   -0.41%
==========================================
  Files         140      140
  Lines       11967    11967
==========================================
- Hits         5486     5438      -48
- Misses       5862     5908      +46
- Partials      619      621       +2

Flag
Coverage Δ

Object-compatibility-e2etests
?

unittests
45.44% <0.00%> (-0.41%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

client/config/dfget.go
29.06% <ø> (ø)

client/config/peerhost.go
33.21% <0.00%> (ø)

client/daemon/peer/peertask_piecetask_poller.go
30.43% <0.00%> (-20.29%)
:arrow_down:

cdn/supervisor/progress/progress.go
90.62% <0.00%> (-6.25%)
:arrow_down:

client/daemon/rpcserver/subscriber.go
48.85% <0.00%> (-2.30%)
:arrow_down:

...ent/daemon/peer/peertask_piecetask_synchronizer.go
47.61% <0.00%> (-1.30%)
:arrow_down:

client/daemon/peer/peertask_conductor.go
57.31% <0.00%> (-1.01%)
:arrow_down:


feat: improve asyncio write performance

Similar to https://github.com/python/cpython/blob/2a50772b63d7bc4ef97d16e9bcc53455c301b0ea/Lib/asyncio/selector_events.py?rgh-link-date=2022-09-24T02%3A51%3A37Z#L914
fixes #28

I don't think we can get rid of add_writer/remove_writer because its needed for unexpected disconnects.
However with this change ~85% of writes don't need to be scheduled and can happen right away so it helps quite a bit with the latency


Getting Request Denied

Hello, im always get Reques_Denied, i've enable direction API, what should i do?

I suggest checking few things before we dig deeper:

Check you are not using expired key / a key associated with the wrong project
Use Server Key, instead of Android key
Make sure you have enabled Directions API from the API console
Make sure you are not supplying any wrong parameters i.e. from, to locations.

At last, try some static example from author's documentation guide - usage examples!
Please let us know how it goes!
Best,
Sagar

Oh i see get error when converting LatLng to latitude/longitude,
java.lang.NumberFormatException: Invalid double: "lat/lng: (-6.192474" , the value have "(". Any idea bro?


⚠ Bofrost.be has degraded performance

In 2f3f060, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 865 ms

Resolved: Bofrost.be performance has improved in 7ecaae5.


Prevent infinite recursion in Name::Scan

This prevents a very unlikely but possible infinite recursion in the Scan function of Name.
A buffer that begins with [192,0] would cause infinite recursion to occur.
I'm not sure if that was the right Error type to use though.

Nice catch! Can you add a test?
I think it deserves another error, given that another option in error enum is cheap.
Can there be infinite recursion even if offset is non-zero? Given that the offset is against the original if it is the same as data it can result into infinite recursion too, right? Perhaps, there might be two offsets and we can infinitely jump between them. Or am I misunderstanding the issue?

You're totally right. I was thinking of a really simplistic case where the buffer passed in started [192, 0], but a non-zero offset could totally cause that to happen as well. I think that could be checked by doing a length check of original[off..].len() and data.len(). But I'm not sure how to prevent the jumping between two offsets besides adding an upper bound for recursion depth.

For testing, here are two simple buffers that each produce the infinite recursion you described.
Non-zero offset that recurses to the same offset, vec![192, 2, 192, 2]
Recursion that bounces between two offsets, vec![192, 2, 192, 4, 192, 2]

Oh yeah. I will make a unit test for this as well.
Here's how dnspython (a popular python dns package) handles it, they just don't do recursion and make sure that the offset always goes backwards, Line 751.
https://github.com/rthalley/dnspython/blob/master/dns/name.py#L717

We have this format for names just because we don't want additional memory allocations. Most names in dns packets are never decoded.
Making it a loop looks like not too hard. We already have a outer loop anyway. The recursion was just a lazy implementation way.
Do you need any help with this?

I'm not sure how I'd exactly do it unless I can pass in the offset value into the scan function as well.

What do you think of this? I had to add a few variables to make it work with the current Name format. I don't really like the return_pos option type, but I can't think of a way around it.

I think you can declare return_pos as a non-option and write:
let return_pos;
loop {
  if byte != 0 {
    return_pos = pos+1:
    break;
  }
  // ...
}

rustc is smart enought to find out that it's not an option and there are only two exit points from the loop and both of them assign to return_pos (i.e. they don't leave return_pos unitialized)
Overall it looks fine, but I need to take closer look to the edge cases. Do we have enough test to be sure that it doesn't break in some other way?

I knew that, but the reason I made it an option type was that I only wanted to set return_pos once right before the first time the offsetting happens. If i don't use an option type, I'm not sure how to prevent return_pos from being changed every time we have to offset to find a label.
I do need to create more tests. I'm not sure about having enough test cases, I can only make sure that it works in my use case on top of the unit tests.

I knew that, but the reason I made it an option type was that I only wanted to set return_pos once right before the first time the offsetting happens. If i don't use an option type, I'm not sure how to prevent return_pos from being changed every time we have to offset to find a label.

If you make variable non-mutable you can assign it only once (i.e. in two distinct branches of code is fine, but not subsequently)

Sorry, but I'm confused. The assignment of return_pos happens in the if byte & 0b1100_0000 == 0b1100_0000 case which can happen multiple times. If I declare return_pos as let return_pos;, it just complains that re-assignment of immutable variable return_pos`` and says that it was assigned on the same line. Can you elaborate more on how to do it?

Ah, yes, sorry, apparently it will not work this way.

@tailhook, I've squashed my commits and added some, pretty basic, unit tests.

It's bad idea to derive PartialEq, if we ever make PartialEq for Name we should compare actual names (like to_string()) not slices. While I'm not strongly opposed to PartialEq for error, you might use matches! macro anyway, because you can't compare the result on equality.

Please keep line lengths of 80 characters

Otherwise looks good.
P.S.: You don't have to squash manually, there is a merge-by-squash button in github

@tailhook I updated it to use matches! instead. I also did some line wrapping.

Looks good now. Thanks!


operators postgresql (5.1.0)

Signed-off-by: TJ Moore<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/test all

/test all

@tjmoore4 minKubeVersion is defined 1.20 which is v4.7 but it is in conflict with com.redhat.openshift.versions: 'v4.6'

/test all

/merge possible

/merge possible

@tjmoore4 replaces: postgresoperator.v5.0.5 is missing in csv. Can you fix it?

@tjmoore4 replaces: postgresoperator.v5.0.5 is missing in csv. Can you fix it?

@mvalarh We had an issue with our other bundles when using replaces because the previous bundles had an upper bound of 4.9 for the OCP version. We now want to use an unbounded supported version value (com.redhat.openshift.versions="v4.6") to support the newer OCP versions with v5.1.0.  As we understand it, each OperatorHub index is maintained as a separate entity so the indexes for 4.10 and 4.11 are 'missing' for the v5.0.5 release, meaning we cannot use replaces as we previously did.
To handle this issue, we used skips instead of replaces, i.e.
  skips:
  - 'postgresoperator.v5.0.5'

All that said, I do not believe replaces will work with are particular case, but it seems that perhaps our skips setting is not being respected? Or is it that replaces is always expected? (based on this error:
msg: 'Bundle ''quay.io/openshift-community-operators/postgresql:v5.0.2,quay.io/openshift-community-operators/postgresql:v5.0.3,quay.io/openshift-community-operators/postgresql:v5.0.4,quay.io/openshift-community-operators/postgresql:v5.0.5,kind-registry:5000/test-operator/postgresql:v5.1.0'''' was not added or not pushed to ''kind-registry:5000/test-operator/catalog:v4.9'' using mode ''replaces'' : [FAIL]'

)

@tjmoore4 see https://olm.operatorframework.io/docs/concepts/olm-architecture/operator-catalog/creating-an-update-graph/#skips
and add replaces: postgresoperator.v5.0.4

/merge possible

/test 4.9-deploy-operator-on-openshift

/merge possible


Formatting and linting with black + ruff

Let me know if you'd rather me turn off the black setting around standardizing on double-quotes (which is the bulk of the changes)

apologies @sfc-gh-zblackwood looks like your two PRs fought each other. If you can help resolve this I can merge this in

@sfc-gh-jhollan Fixed


fix: Update license copyright message

Signed-off-by: Klaus Smolin<EMAIL_ADDRESS>

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


Bug related to merging previous step config

@aolofsson I noticed a bug where the summary() function may print out steps even if only a subset of the graph is specified using -steplist.  However, that step may have been run with different settings. In this case, this particular issue comes about because the steplist of the current run gets overwritten by the steplist of the previous run.
As far as I know, calling readcfg() on the last step's config is just to pull forward the metrics. Do you think we could extend the readcfg API to cause it to only update a certain subtree of the schema? That way, I think this could be solved by only calling readcfg() on the metrics tree.

As far as I know, calling readcfg() on the last step's config is just to pull forward the metrics. Do you think we could extend the readcfg API to cause it to only update a certain subtree of the schema? That way, I think this could be solved by only calling readcfg() on the metrics tree.

We actually do this now, and this bug is confirmed resolved! (although it requires #981 to get an updated version of the reproducer working).


WASM load gtfb error

Because it use the Rayon, and "The global thread pool has not been initialized.: ThreadPoolBuildError".

Hmm are you using the wasm branch? I have it on a separate branch because it uses the master branch of wgpu-rs instead version 0.5 from crates.io.

Yes, I test the wasm branch.

There's a build script at scripts/build-web-demo.sh (sorry it's not documented). Try this:
mkdir -p target/generated/
# Build with the wasm target
RUSTFLAGS=--cfg=web_sys_unstable_apis cargo build --release --target wasm32-unknown-unknown --example basic
# Generate bindings in a `target/generated` directory
wasm-bindgen --out-dir target/generated --web target/wasm32-unknown-unknown/release/examples/basic.wasm

cp scripts/index.html target/generated/

Can you give that a try and let me know how it goes?


Reduce tool build time!

Something has gone wrong and the build time has drastically increased.
NEED to figure out why and reduce it again.

I can take a look. I've got a few ideas to try.

Cool, thanks!
Both, but mainly local build.
Quite annoying to have to wait 20s for a build.

Hmm so the problem is that I'm setting in the workspace global Cargo.toml the following:
[profile.release]
codegen-units = 1
debug = 2
debug-assertions = false
incremental = false
lto = 'fat'
opt-level = 3
overflow-checks = false

# do not optimize proc-macro crates = faster builds from scratch
[profile.dev.build-override]
codegen-units = 8
debug = false
debug-assertions = false
opt-level = 0
overflow-checks = false

[profile.release.build-override]
codegen-units = 8
debug = false
debug-assertions = false
opt-level = 0
overflow-checks = false

# cargo test
[profile.test]
codegen-units = 1
debug = 2
debug-assertions = true
incremental = false
opt-level = 3
overflow-checks = true

# cargo test --release
[profile.bench]
codegen-units = 1
debug = 2
debug-assertions = false
incremental = false
lto = 'fat'
opt-level = 3

which is really only meant for the firmware builds.
With this, the release build of the tool takes 14s but without, just 1.4 seconds.

Yeah. 😞 That was one of the factors in me recommending a split project in my PR. Enabling incremental builds can help the host app too. That way, you aren't rebuilding the entire project every time (only the parts that changed).

I found out how to apply the options only to the firmware, not tool.

Yeah, but I only applied it to release builds, that's ok.


Smart/Agentic Crawler (Invite Collaboration)

I'm planning to add a smart crawler that takes a set of user-defined objectives and continues crawling to satisfy them. Objectives can be a query requiring a sufficient amount of information to answer, a set of actions with specific goals, or other custom tasks. I also plan to incorporate reinforcement learning into this process later. I've created an issue for discussion and invite interested individuals to share ideas and comments. If you're enthusiastic about contributing, please share your email address, and I'll invite you to our Discord channels to collaborate.
Happy Crawling

<EMAIL_ADDRESS>THANKS FOR YOUR WORK

Sent :)

<EMAIL_ADDRESS>Nice work :)

Sending the links @wakaka6

Sending the links   发送链接@wakaka6

@unclecode Hi bro, I didn't get the invite link in my email. Also for the sake of other people contributing code better, it is recommended to create a way for git-hook and github action to use ruff and mypy to check and format the code as a way to ensure the style of the code and avoid confusion caused by editor formatting plugins used by different people.

@wakaka6 Already sent. and Thank you so much for your suggestion. It has been in our plans for a while. I wanted to engage with everything, like the raw material, to familiarize myself with how people interact with the library and gather ideas for building smart collaboration structures. I completely agree that Ruff is blazing fast, and I believe MyPy is the de facto standard. I love the pre-commit feature because it allows users to check their work on their own machines before submission. We're definitely working on it, and I hope to have it ready by January. May be you join and help me on this too.


Linux: Doesn't create directory, only file with directory name

Describe the bug
On Linux it doesn't create the directory specified, it just creates the file named like the directory you put in
To Reproduce
Steps to reproduce the behavior:

Create a new database
Put in the path
Put in a password

Expected behavior
It should create a directory and not the file named like the directory.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Fixed in this commimt


Add keepSpecialComments: 0 to minifyCss process …

Opps, missing comma... This removes all comments from the resulting compiled SASS and concat/minified CSS.  Solves an issue where the /*! style comments in bootstrap break the minification process.

Hey @nezencreation! Can you please squash these 2 commits and do a force push to our repo? Email if you need help with that.
Thanks!

git rebase -i HEAD~3
and then
pick 878f860 fix timezone offset in ISO 8601 date in byline
pick 4a938ef Add keepSpecialComments: 0 to minifyCss process
s 84146b8 fix missing comma


Subpath folder mappings deprecated according to Node.js documentation

This repository documents exports field with an example at https://github.com/jkrems/proposal-pkg-exports#1-exports-field.
In this example one of the configuration correspond to something called Subpath folder mappings in Node.js documentation. This configuration is deprecated according to Node.js documentation 15.x

Node.js documentation and this repository documentation are not in sync, can you explain me why?

Node.js documentation and this repository documentation are not in sync, can you explain me why?

I can attempt to explain the reverse. After active work on defining exports wound down and a lot of work was put into creating proper documentation in the node docs, this repo should've quickly become completely outdated. But @guybedford put in a lot of unpaid work to port updates to this repo as well as improving the content in the nodejs docs. That's why some things around imports are in here that were introduced after the primary work moved to node core.
Depending on how future work with bundlers goes, it may be less confusing the update the README on this repo to point to the node docs and archive the proposal repo.

To give you some context by the way:
I was asking this question because I made a tool to generate import maps from package.json. This tool takes into account every exports field eventually found in package.json. The recent depreciation of "subpath folder mapping" make exports no longer fully convertible to import maps. I wanted to know a bit more about the situation. In the end I have added  a warning about that topic in my documentation (https://github.com/jsenv/jsenv-node-module-import-map#subpath-import-warning).
Thank you for taking the time to respond to my question.  Can't wait to see import resolution getting stable, thank you for your work here.
Have a great day! :)

@dmail some ways to get around this include:

Handle the /*: /* to /: / conversion as you are doing
For other /*.js style cases, enumerating the list from the package is an option
When all the mappings in a folder are explicit mappings (./y.js: ./x/y.js and ./z.js: ./x/z.js then setting pkg/: pkg/x/ can be a sort of "deduping")

Wildcard exports always had this risk, but the arguments for them in Node.js were compelling enough to take it. It's likely we won't see them in import maps proper. But I'm hopeful that techniques like the above can bridge the gap here.

For other /*.js style cases, enumerating the list from the package is an option

I can think about two options when the script finds "./feature/*": "./features/*.js" in the package.json exports field:
a) Use filesystem
Downside of relying on filesystem:  will certainly generate a bunch of remapping never actually imported in the codebase.
b) Parse the code to find static and dynamic imports
Downside of parsing files: makes the tools more complex because it suddenly needs a js parser that is configurable to support TypeScript, jsx, ...

When all the mappings in a folder are explicit mappings (./y.js: ./x/y.js and ./z.js: ./x/z.js( then setting pkg/: pkg/x/ can be a sort of "deduping".

I don't understand 😅 . Do you mean that if all mappings are explicitely written in the package.json, they can be copied as such in the import maps?

Wildcard exports always had this risk, but the arguments for them in Node.js were compelling enough to take it. It's likely we won't see them in import maps proper. But I'm hopeful that techniques like the above can bridge the gap here.

I think omitting extension creates confusion and complexity in tooling. It is still not crystal clear why Node.js (and TypeScript) encourages directly or indirectly to omit extension.

@dmail it makes the .mjs / .ts / .js extension an implementation detail. Also many package authors are accustomed to publishing pkg/feature instead of pkg/feature.js. Import maps allow us to omit extensions, ./: ./ effectively gives preferential treatment to extensions. There were cases of authors publishing huge "exports" fields with separate entries because ./x/: ./y/ wasn't sufficient. Even to the point of npm having trouble with the size of the manifests. Wildcards also ensure not exposing unnecessary files by acting as a filter which is a powerful property. We let users make the decisions by giving them the flexibility. We had import maps in mind, but this wasn't seen as a blocker or a strong enough problem - enumerating from the file system as a package processing step isn't so bad honest.
Import maps always have the problem of unnecessary bloat regardless though. In general basing them on a tracing analysis operation is always a needed optimization, even more especially since they are first load blocking it justifies that work.
I mean that the import map:
{
  "imports": {
    "pkg/y.js": "/pkg/x/y.js",
    "pkg/z.js": "/pkg/x/z.js"
  }
}

can be automatically simplified to:
{
  "imports": {
    "pkg/": "/pkg/x/"
  }
}

as an optimization. I also prefer extensions for this reason, but we cannot dictate (or if you want to, advocate!).

Got your point about .mjs / .ts / .js becoming implementation detail.
Also got it for the deduping of mappings declared in the importmap.
I will not advocate for extensions but would give all my support and adoration to someone that would :D
Thanks for the valuable infos @guybedford and @jkrems


linux: Can't run examples. HCI.send blocks forever.

Hello,
I've tried to run scanner and explorer examples, but unfortunately they hang on gatt.DefaultDevice(). I looked deeper and it looks like that select https://github.com/currantlabs/ble/blob/master/linux/hci/hci.go#L253 blocks forever.
My system:
-> uname -r
4.6.2-1-ARCH

Could you please give any tip about what is going wrong here?
Thanks!

Let's see if the following can get us a little bit further.  :)

Check if your system is running "bluetoothd", if yes, turn it off for now and see if that's the case.

Reset the HCI device in case it was in some bad status we couldn't recover from.

sudo hciconfig hci0 reset
sudo go run scanner/main.go

Check if your system was configured with bluetoooth at all.

sudo hciconfig hci0 up
sudo hcitool -i hci0 lescan

If the hcitool works while the examples are still not working, run the hcidump to log the packets for both cases (examples, and hcitool) for comparison/debugging.

sudo hcidump -i hci0

Thanks for the help, @roylee17! Unfortunately it still doesn't work for me. I'm still getting stuck at gatt.DefaultDevice().
hcitool and gatt library work fine on the same machine.
I'll try to dump the logs from hcitool, gatt and ble and compare them. I hope I'll find something.

Just a little update: I tried to use ble on another Ubuntu linux machine and I experienced the same problem. Though, it worked just fine on the raspberry Pi.
I'll try to investigate more.

Hi @eicca & @roylee17 I have the exact same issue on Ubuntu 14.04. with the latest ble package and the scanner example.
Attached is my hcidump file.
Thanks!
scan.txt

FOr a little additional info, this where it gets "stuck": https://github.com/currantlabs/ble/blob/master/linux/hci/hci.go#L253

Called as part of the Init() https://github.com/currantlabs/ble/blob/master/linux/device.go#L21 to be clear.

Oops, I had forgotten the hcidump for my successful sudo hcitool -i hci0 lescan run. Here it is.
hcitool.txt

It is this Send() here that suspends forever: https://github.com/currantlabs/ble/blob/master/linux/hci/hci.go#L179

Last comment, hopefully. the latest currantlabs fork of gatt works fine on the same machine, just not this package.

Sorry for the late response.
We should be able to fix it quickly once we can reproduce it.
I just installed a vagrant box (virtualbox) with ubuntu-14.04 with updated bluez, to reproduce it, but it didn't happen.
Is it 100% reproducible in your config, or it happens sometime?
Can you show the following configuration for reference?
vagrant@vagrant:~/go/src/github.com/currantlabs/ble/examples/basic/scanner$ dpkg -s bluez|grep Version
Version: 4.101-0ubuntu13.1

vagrant@vagrant:~/go/src/github.com/currantlabs/ble/examples/basic/scanner$ uname -a
Linux vagrant 3.13.0-103-generic #150-Ubuntu SMP Thu Nov 24 10:34:17 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Version prints the Go version, as reported by runtime.Version.
vagrant@vagrant:~/go/src/github.com/currantlabs/ble/examples/basic/scanner$ go version
go version go1.7 linux/amd64

vagrant@vagrant:~/go/src/github.com/currantlabs/ble/examples/basic/scanner$ git show --oneline
65396cf Merge pull request #21 from syoder/flush-socket-after-bind

vagrant@vagrant:~/go/src/github.com/currantlabs/ble/examples/basic/scanner$ sudo ./main
Scanning for 5s...
[68:d9:3c:7c:72:83] C -81: MD: 4C000906031F0A000111
[68:d9:3c:7c:72:83] C -81: MD: 4C000906031F0A000111
[65:7b:59:12:5a:40] C -100:
[65:7b:59:12:5a:40] C -98:
[68:d9:3c:7c:72:83] C -87: MD: 4C000906031F0A000111
[68:d9:3c:7c:72:83] C -81: MD: 4C000906031F0A000111
[68:d9:3c:7c:72:83] C -81: MD: 4C000906031F0A000111
^Ccanceled

In your hcidump, there is  a vendor specific command at the end of the initialization sequence.
And after that the device is not responding to our first command.
175 < HCI Command: Vendor (0x3f|0x003f) plen 0
176 > HCI Event: Command Complete (0x0e) plen 4
177     Vendor (0x3f|0x003f) ncmd 1

178 < HCI Command: Read BD ADDR (0x04|0x0009) plen 0

Can you attach the hcidump (with -t) for the following experiment:
hciconfig down hci0
hcidump -t hci0 (another terminal or redirect to file)
hciconfig up hci0
hcitool -i hci0 lescan run

Just in case, experiment with hci reset as well.
hciconfig down hci0
hcidump -t hci0 (another terminal or redirect to file)
hciconfig reset hci0
hcitool -i hci0 lescan run

Let's see if that vendor specific command shows up, and what need to be done before it takes/responds to the next command (some... delay?).
In that case, hack our init() call to wait a little bit and see if that 's the case:
Add time.Sleep(time.Second*5) after socket.NewSocket(h.id)
https://github.com/currantlabs/ble/blob/master/linux/hci/hci.go#L138

Thanks for looking into this.
Here are my system settings:
$ dpkg -s bluez|grep Version
Version: 4.101-0ubuntu13.1
$ uname -a
Linux ron-XPS-13-9343 4.4.0-57-generic #78~14.04.1-Ubuntu SMP Sat Dec 10 00:14:47 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ go version
go version go1.7.4 linux/amd64
$ git show --oneline
65396cf Merge pull request #21 from syoder/flush-socket-after-bind

Looks like we have different kernel versions?
I performed the dumps as requested. Note that the syntax for hciconfig down hci0 is actually hciconfig -a hci0 down etc. In any case, there was no occurrence of Vendor anywhere in either log.
Lastly, I added the suggested time.Sleep() but it had no effect.
hcidump2.txt

Okay, let's where does that vendor command come.
https://github.com/currantlabs/ble/commit/7445c31b838a5f554f844c4a0d8d2a5846cb10fa
Can you apply this commit, and run it with the log enabled (sudo LOGXI=* ./scanner), and also hcidump with -t at the same time.
This add a few 1-second delay, and dump the raw traffic we send to HCI.
Cross reference the timestamp from hcidump, we should be able to find where and then figure out why.

OK here is the output:
$ sudo LOGXI=* ./scanner
15:22:58.446404 INF hci Creating socket
15:22:59.446763 DBG socket down hci
15:23:00.448324 DBG socket up hci
15:23:01.496202 DBG socket down2 hci
15:23:02.497270 DBG socket bind hci user_channel
15:23:03.498104 DBG socket poll previous left over
15:23:04.518374 INF hci Creating sktloop
15:23:05.518675 INF hci Send init seq
15:23:05.518813 DBG socket Write raw: [01 09 10 00]

And here is the dump file:
hcidump3.txt

A few quick experiments.
Comment out those three "up and down" in our code.
From
https://github.com/currantlabs/ble/commit/7445c31b838a5f554f844c4a0d8d2a5846cb10fa#diff-a58a7abf497cdab9034b34b85b0800bfR93
To
https://github.com/currantlabs/ble/commit/7445c31b838a5f554f844c4a0d8d2a5846cb10fa#diff-a58a7abf497cdab9034b34b85b0800bfR111
Use hciconfig to init the device before invoking the scanner binary.
(with hcidump)
sudo hciconfig down
sudo hciconfig up
sudo hciconfig down

and again
sudo hciconfig reset
sudo hciconfig down

When I remove these lines https://github.com/currantlabs/ble/blob/debug/issue_11/linux/hci/socket/socket.go#L93-L111 I receive this error:
$ sudo LOGXI=* ./scanner
18:56:53.431004 INF hci Creating socket
18:56:54.431364 DBG socket bind hci user_channel
2017/01/06 18:56:54 can't new device : can't init hci: no devices available: (hci0: can't bind socket to hci user channel: device or resource busy)

The device state at the time of being binded with HCI_USER_CHANNEL must be down.
After hciconfig hci down in both cases, check again and see if the state is really down.

I forgot the syntax is sudo hciconfig -a hci0 down etc. My bad.
In both cases, the log is quite short:
HCI sniffer - Bluetooth packet analyzer ver 2.5
device: hci0 snap_len: 1500 filter: 0xffffffffffffffff
2017-01-06 19:11:18.680933 < HCI Command: Read BD ADDR (0x04|0x0009) plen 0

With the following output:
$ sudo LOGXI=* ./scanner
19:11:14.659604 INF hci Creating socket
19:11:15.659995 DBG socket bind hci user_channel
19:11:16.660293 DBG socket poll previous left over
19:11:17.680607 INF hci Creating sktloop
19:11:18.680823 INF hci Send init seq
19:11:18.680897 DBG socket Write raw: [01 09 10 00]

Then this is really strange. The very first thing we tried to talk with device after initialization, it doesn't respond.
I suspect the particular driver of that particular kernel version is doing something differently when it comes to HCI_USER_CHANNEL.
But you mentioned gatt, which also uses HCI_USER_CHANNEL does work in your system.
Can you help to hcidump gatt.
And also strace both ble binary and gatt binary.
I'll try if I can install that kernel on my ubuntu later. Or if its easier that you can try other kernel version.
3.13 on ubuntu works. And I've been using 3.17, 4.1, 4.8 and and a few other version on my gentoo box without problem.

OK here is my gatt run:
$ sudo ./discoverer
2017/01/06 20:07:29 dev: hci0 up
2017/01/06 20:07:29 dev: hci0 down
2017/01/06 20:07:29 dev: hci0 opened
State: PoweredOn
scanning...

Peripheral ID:C1:CD:28:CF:12:8E, NAME:(2B-128E)
  Local Name        = 2B-128E
  TX Power Level    = 246
  Manufacturer Data = []
  Service Data      = []

Peripheral ID:EE:A3:19:85:15:8C, NAME:(2B-158C)
  Local Name        = 2B-158C
  TX Power Level    = 246
  Manufacturer Data = []
  Service Data      = []

Peripheral ID:F3:F2:6D:55:71:08, NAME:(BB-7108)
  Local Name        = BB-7108
  TX Power Level    = 6
  Manufacturer Data = [51 48]
  Service Data      = []

and the associated hcidump file:
hcidumpgatt.txt

https://github.com/currantlabs/ble/compare/debug/issue_11
I revert the device/socket handling. Give it shot and see if anything changes

Here is the strace from the gatt run:
tracegatt.txt
Here is the strace from the scanner:
scanner-trace.txt

Here is the scanner strace after a sudo hciconfig -a hci0 reset && sudo hciconfig -a hci0 down:
scanner-trace-after-reset.txt

Here is the strace form the scanner after the reverted code:
scanner-after-revert.txt

So the reverted one still not working? BTW, I got Slack back on. Let's work on this more interactively.

The reverted code isn't working for me either. I'll to reproduce the issue with virtualbox so it'd be easier to debug.

I have the same problem also on my Intel Edison running Yocto, so it is not just an Ubuntu issue:
root@howtocode:~# hciconfig -a hci0 down
root@howtocode:~# ./robots/scanner
2017/01/06 21:59:08 dev: hci0 up
2017/01/06 21:59:08 dev: hci0 down
2017/01/06 21:59:08 dev: hci0 can't bind to hci user channel, err: invalid argument.
2017/01/06 21:59:08 dev: hci0 opened
^C
root@howtocode:~# hcitool lescan
Could not open device: No such device
root@howtocode:~# hciconfig -a hci0 up
root@howtocode:~# hcitool lescan
LE Scan ...
7D:22:0A:9F:01:82 (unknown)
F3:F2:6D:55:71:08 (unknown)
F3:F2:6D:55:71:08 BB-7108
C1:CD:28:CF:12:8E (unknown)
EE:A3:19:85:15:8C (unknown)
EE:A3:19:85:15:8C 2B-158C
7D:22:0A:9F:01:82 (unknown)
C1:CD:28:CF:12:8E 2B-128E
^Croot@howtocode:~# hciconfig -a hci0 down
root@howtocode:~# ./robots/scanner
2017/01/06 22:00:58 dev: hci0 up
2017/01/06 22:00:58 dev: hci0 down
2017/01/06 22:00:58 dev: hci0 can't bind to hci user channel, err: invalid argument.
2017/01/06 22:00:58 dev: hci0 opened

@deadprogram , this might be different.  I seemed to remember Edison Yocto was using an earlier kernel that doesn't support HCI_USER_CHANNEL yet.
In gatt, we used to fall back to use RAW channel in that case. But, that means we might have some subtle behavior as Kernel is also talking to the device in the background.
You can try if that's the case by changing the unix.HCI_CHANNEL_USER to HCI_CHANNEL_RAW. And the reverted version should work, I guess.

HCI_CHANNEL_RAW got rid of the can't bind to hci user channel, err: invalid argument. error. New code did not get any further as far as scanning, however.

I note that when I switch gatt discoverer to use HCI_CHANNEL_RAW it has the same "sit forever without scanning" behavior on both my Ubuntu notebook and my Edison as the ble scanner does.

OK, here is my log output:
$ sudo LOGXI=* ./scanner
21:43:35.302067 DBG socket down hci
21:43:36.302430 DBG socket up hci
21:43:37.350326 DBG socket down2 hci
21:43:38.351446 DBG socket bind hci user_channel
21:43:39.351734 DBG socket poll previous left over
21:43:39.372037 DBG socket Write
   raw: [01 06 20 0F 20 00 20 00 00 00 00 00 00 00 00 00 00 07 00]

Attached is my hcidump file:
hcidump6.txt

Honestly, I'm really running out of idea about what's going on. At least one of those experiments we did should make some difference.
We're stuck at the early stage that the very first thing we send to the kernel is not responded. So we don't even have a chance to do anything wrong with the response yet.
Reverting the socket/device package should give us the identical handling with what gatt is doing up to that point.
Probably the last attempt I can think of - try the reverted version again with different condition:

with the hci0 device down.
with the hci0 device up.

They will hit different paths in the socket package.

I upgraded my Dell XPS 13 (Dell Developer Notebook) to Ubuntu 16.04:
$ uname -a
Linux ron-XPS-13-9343 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

However, I still have the same problem with ble. I am able to scan using hcitool:
$ sudo hciconfig -a hci0 reset && sudo hciconfig -a hci0 up
$ sudo hcitool -i hci0 lescan
LE Scan ...
EE:A3:19:85:15:8C (unknown)
EE:A3:19:85:15:8C 2B-158C
54:44:EE:EC:76:97 (unknown)
54:44:EE:EC:76:97 (unknown)
C1:CD:28:CF:12:8E (unknown)
C1:CD:28:CF:12:8E 2B-128E
F3:F2:6D:55:71:08 (unknown)
F3:F2:6D:55:71:08 BB-7108

I compiled scanner using the last commit to both the debug/issue_11 branch as well as the master branch, but neither one was able to do the scanning.
$ sudo ./scanner
2017/01/14 11:14:25 dev: hci0 up
2017/01/14 11:14:25 dev: hci0 reset
2017/01/14 11:14:25 dev: hci0 down
2017/01/14 11:14:25 dev: hci0 opened

Attached is the hcidump file from running the scanner from the debug/issue_11 branch. I see that vendor command as the last command sent before it stops responding:
2017-01-14 10:57:52.511758 > HCI Event: Command Complete (0x0e) plen 4
    Vendor (0x3f|0x003f) ncmd 1

hcidump1604-1.txt
Likewise, I am completely baffled here. Obviously the hardware itself "works" but there is something in there somewhere in ble not quite handling things in the same way.

My new bluez version:
$ dpkg -s bluez|grep Version
Version: 5.37-0ubuntu5

Here is the hciscan dump of the successful sudo hciconfig -a hci0 reset && sudo hciconfig -a hci0 up and sudo hcitool lescan commands.
I notice that it does start with the same vendor command, but then immediately issues a reset:
2017-01-14 11:45:58.235923 > HCI Event: Command Complete (0x0e) plen 4
    Vendor (0x3f|0x003f) ncmd 1
2017-01-14 11:45:58.249971 > HCI Event: Command Complete (0x0e) plen 4
    Reset (0x03|0x0003) ncmd 2
    status 0x00

I do not know enough about the low-level protocol here, but looks interesting?
hcidump1604-lescan.txt

The things bothers me is that I tried to reverted blue to the point that should work as gatt, and they still behave differently. The hcidump from your gatt discover also has a vendor command presents, but it works fine.
You have a spare machine that can ship to me? I can spend a day or two dedicated on it.

func (h *HCI) init() error {
   h.Send(&cmd.Reset{}, nil)

So give it a shot, reset it in the h.init().

It worked!!
$ sudo ./scanner
2017/01/14 12:07:36 dev: hci0 up
2017/01/14 12:07:36 dev: hci0 reset
2017/01/14 12:07:36 dev: hci0 down
2017/01/14 12:07:36 dev: hci0 opened
Scanning for 5s...
[ee:a3:19:85:15:8c] C -74:
[ee:a3:19:85:15:8c] C -74: Name: 2B-158C, Svcs: [22bb746f2ba075542d6f726568705327]
[f3:f2:6d:55:71:08] C -44: MD: 3330
[f3:f2:6d:55:71:08] C -44: Name: BB-7108, Svcs: [22bb746f2ba075542d6f726568705327], MD: 3330
[c1:cd:28:cf:12:8e] C -67:
...

I thought it looked "interesting".
Wow, thank you for persevering thru to find out what was happening here!

That same one line change when made to master branch also worked to scan as expected.

I've submitted a PR with the change here https://github.com/currantlabs/ble/pull/26. @eicca can you please check to see if this works for you?

Thanks for both of you. Especially @deadprogram for his persistence and patience tracing through and resolving the issue. :)

Don't forget to close this issue now, and thanks again.


 But all newly created repo (Next to migration) haven't problem.
Exact same configuration on 1.1.3 work fine.

duplicated with #1794

For information, upgrade to 1.2-rc2 cause exactly same problem.
This issue not concern only team repository, but all of repository previously in gitea.
Is possible that issue be caused by an initial gogs upgrade from ?

@vfricou maybe because from a gogs upgrade which missing some migrations.

Is possible to update database needed fields (I don't find any database structure information nowhere) ? Because I've done an upgrade from gogs in higher version than specified on website ?

You should change the db version to 14 and then upgrade.


automapper removed and replaced by mapster completely

all the comments and are removed and automapper package is also removed and replace by mapster

Thanks! Any feedback about this project. Are the other endpoints working well for you? any suggestions? @ittyabrehman

Yes all is working fine to me till now. Just Today i started exploring this project. I will go through it step by step and let you know more. At the end, Trust me brother you are doing awesome work and your efforts are super appreciated. Keep it up🙂

Thanks! Any feedback about this project. Are the other endpoints working well for you? any suggestions? @ittyabrehman


Improve LDAP integration

User don't need anymore add the files for ldap configuration to the config folder
Minor fixes

Thank you very much!


Arrow keys automatically repeated if pressed once with wsl and an X server

Environment
Platform ServicePack Version      VersionString

Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0
Steps to reproduce
problem 1

install VcXsrv, start it
open a file using emacs from wsl
press any of the arrow keys once
the cursor might automatically move until reached the end or the head of the file, like the arrow keys were automatically repeated
This problem is randomly appears.

problem 2

uninstall VcXsrv, change to MobaXterm
open a file using emacs from wsl
press any of the arrow keys once
there are something like<PHONE_NUMBER>11111111111,<PHONE_NUMBER>22222222,<PHONE_NUMBER>44444444 would appear on the software
This problem is also randomly appears

Expected behavior
arrow keys should move the cursor correctly
Actual behavior
arrow keys repeated automatically

The behavior of the keyboard and cursor in any of those products (VcXsrv, emacs, many things beside) is not under the control of WSL. Can't repro here, but even if I could there wouldn't be an actionable. [Because WSL doesn't have a keyboard.]
If you explore your scenario further in a forum related to those products, recommend framing the question in terms of a VM or cloud scenario using VcXsrv or Moba as the server.

Here's the discussion Vcxsrv https://sourceforge.net/p/vcxsrv/bugs/59/

https://sourceforge.net/p/vcxsrv/bugs/59/#5b37

I changed the IME with shift+ctrl to default IME, then it works. But this is very strange.

It works for me! @schelian thanks

try to turn off IME

https://sourceforge.net/p/vcxsrv/bugs/59/#5b37

I changed the IME with shift+ctrl to default IME, then it works. But this is very strange.

It works for me! @schelian thanks

hi, I have the same issue, would you tell me what kind of IME do you use ? I tried fcitx but not work.


upgrade workflows from Node 12/14 to either LTS or current

@JSAssassin tests here need to match the version the actual test suites run in so I believe node 16 now.


PowerRename Doesn't rename Files

Microsoft PowerToys version
0.80.1
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
PowerRename
Steps to reproduce
right click the files I want to rename -> open PowerRename -> does not let me rename the files
✔ Expected Behavior
cant rename any file, tried to change to file only, change to only target files and not folders, etc.

❌ Actual Behavior
only able to change the txt format of the files, doesnt let me rename them

Other Software
No response

What do you want to replace? You SEARCH fields are empty 🤓

What do you want to replace? You SEARCH fields are empty 🤓

hi thank you yes, that was on part, but also how could I rename them completly?
as whenin the "search for" I put file but it renames the file to "1 RenameFile (1)" and I want it just to be ""1 RenameFile" but I dont know how to select all the numbers with brackets or if is there a way to select all the files selected to rename them

If you want to remove the numeration at the end, try \(\d+\) and make sure "use regular expressions" is checked. Let us know if that does it.

this is it, thank you for the help!!!!