text:
Add bevy_entropy plugin and include it in the default set

Objective

Bevy games / applications often need to use random number generators, but they make execution non-deterministic. Currently there is no official way to introduce determinism in a bevy-supported way.

Solution

Include a source of entropy to (optionally) enable deterministic random number generators. The plugin can be completely disabled if no source of entropy is required, the default entropy from the OS can be used if randomness is needed but deterministic execution is not, or a world seed can be specified for deterministic random number generation.

Note that I put up a PR previously to add default rngs. While most other engines (godot, unity, etc) provide built-in rngs, this is a lower-level (and more general?) building block we likely want to start with first.
Open items

[x] Is the naming ok? Entropy or EntropySource? get()? Naming is ok
[x] Should this be a plugin or in core? One can make the argument that entropy is as core as time and thus should always be there. Plugin is better and time might move out of core.
[x] Tests
[ ] Docs (did I miss these in the repo?)
[ ] Changelog item

I don't think this is deterministic where there is system ordering ambiguity - afaik I we don't make a promise about execution order in that case
However, I hadn't realised that a mutable resource would be deterministic if ordering is well defined - although obviously that does have the cost of making all entropy access serial.
One potentially neat thing would be for the rng to be a custom system parameter, which gets a 'system level' rng seed, without blocking the global entropy. We would probably need a pre-run hook which could hold resources for only a short amount of time (alternatively, chained systems could support something similar and those could be used instead)

Preface: I think that standardizing on a solution here is extremely important. Without it, each crate in the ecosystem will use their own PRNG solution, bloating dependencies and making a unified approach to determinism pretty much impossible.

I don't think this is deterministic where there is system ordering ambiguity - afaik I we don't make a promise about execution order in that case

We can currently use the single-threaded executor when we want drop-in determinism. There's space in the future for more sophisticated parallel executors as well.

One potentially neat thing would be for the rng to be a custom system parameter, which gets a 'system level' rng seed, without blocking the global entropy

Agreed, this would be extremely useful, and worth baking into Bevy as a whole. RNG use will be quite prevalent in some games, and it would be nice to have a non-blocking solution.

We would probably need a pre-run hook which could hold resources for only a short amount of time (alternatively, chained systems could support something similar and those could be used instead)

I prefer the former solution; I would probably build it using a simple exclusive system that runs at the start of the schedule and initializes the Local data of each RNG dependent system. Could you expand a little on how you think system chaining could work @DJMcNab?

The basic idea of how the system chaining would work is that the first system in the chain would only block the resources that it uses.
E.g. a system with a resmut parameter could be chained after a relatively long running system without blocking other system's access to that value, such as to update it at the end of the frame, say
Basically change chaining into dependencies with 'message passing'
Also our single threaded executor also doesn't guarantee ordering afaik, it's just a way to run the parallel system graph but only using one thread

Also our single threaded executor also doesn't guarantee ordering afaik, it's just a way to run the parallel system graph but only using one thread

Right... it runs it in topographic order, but that topographic order may vary freely within the constraints between runs.

Is the naming ok? Entropy or EntropySource? get()?

I much prefer Entropy. It's perfectly clear and we're going to need to type this a lot.

Should this be a plugin or in core? One can make the argument that entropy is as core as time and thus should always be there

Hmm. It would force a dependency on rand for every Bevy app, which is not great. I see your point though.

Docs (did I miss these in the repo?)

The doc strings and examples here are quite good so far. You could add module level documentation, but what probably makes more sense is to add a page on RNG as part of chapter 3 of the new book in the bevy-website repo. See https://github.com/bevyengine/rfcs/blob/main/rfcs/23-quick_start_book.md for an overview of the plan there.

@LegNeato we're currently undergoing relicensing to add Apache in addition to MIT. Could you please agree to this relicense over in https://github.com/bevyengine/bevy/issues/2373?

Commented. Will try to clean this up in the next day or so.

Not sure why the ci job is failing with something related to jni, I didn't touch anything there. Any pointers would be appreciated.
I'll look into automatically making rngs or entropy per-system if this lands.

Ah, the same CI issue exists on master:
https://github.com/bevyengine/bevy/runs/3326099396

This is now a part of an RFC: https://github.com/bevyengine/rfcs/pull/55

What are the pros/cons of this versus bevy_rand, besides this being intended to be built-in? Are there any design ideas to merge in or anything like that?

This predates bevy_rand and inspired a bit of it (and the verbage of much of the bevy_rand explanation is reused from the RFC associated with this).

Closing in favor of https://github.com/bevyengine/bevy/pull/7871 and/or bevy_rand. I still think this needs to be built into bevy.

authors: DJMcNab LegNeato alice-i-cecile rdrpenguin04


text:
Added example of how to create prefabs.

Objective

Creating prefabs in Bevy using scenes is largely undocumented, with the biggest issue being the inability to capture the spawned scene.
This inability makes it difficult to modify the prefab after spawn, in order to do things such as parent to other entities, adjust values, or add components.
The use of Dynamic Scenes is thus greatly limited, and until the involved systems are updated, Bevy needs an easier and more stable method of creating prefabs.

Solution

Using code from  bevy/crates/bevy_scene/src/dynamic_scene.rs, I have created a prefab factory that takes a new Entity and a Handle and inserts components from the loaded scene into the entity.
This PrefabFactory is simply a HashMap<Entity, Handle> that is placed into a Resource.
An exclusive system then checks to see if the handle is loaded, then applies the components directly to entity.
Components can be assigned to the Entity upon spawn, and will remain after the scene components are applied, assuming that the DynamicScene did not already have the component.

Limitations

Component data from the prefab won't be available immediately; the PrefabFactory systems run in the CoreStage::Last stage, and the actual scene must load before the scene is applied.
Sub-entities are not supported currently, as the factory only applies the first entity listed in the scene. It may be possible to spawn multiple new entities at a time, but it would be difficult to capture them. It is likely that nested scene support is necessary before prefab sub-entities are ergonomic.

Component data from the prefab won't be available immediately; the PrefabFactory systems run in the CoreStage::Last stage, and the actual scene must load before the scene is applied.
Sub-entities are not supported currently, as the factory only applies the first entity listed in the scene. It may be possible to spawn multiple new entities at a time, but it would be difficult to capture them. It is likely that nested scene support is necessary before prefab sub-entities are ergonomic.

Thanks for listing out these limitations; they're very useful to have documented.
Can you add them to the example? The PR description will not be very discoverable for future users.

Thank you for raising this issue :-)

Creating prefabs in Bevy using scenes is largely undocumented, with the biggest issue being the inability to capture the spawned scene.
This inability makes it difficult to modify the prefab after spawn, in order to do things such as parent to other entities, adjust values, or add components.

I agree with the need for better documentation, but there are ways to do what you described. They are shown in the update_gltf_scene example.
Here is how to spawn a scene as a child of another entity: https://github.com/bevyengine/bevy/blob/94db0176fecfac7e7e9763f2dc7458a54c105886/examples/3d/update_gltf_scene.rs#L38-L47
Here is how to modify the spawned entities: https://github.com/bevyengine/bevy/blob/94db0176fecfac7e7e9763f2dc7458a54c105886/examples/3d/update_gltf_scene.rs#L55-L74
Not shown in any example to my knowledge. but you can also modify the scene's inner world after it's loaded, before spawning it (possibly by listening to the asset creation event).
I do think we should improve the documentation, and make an example of a higher abstraction to easily work with scenes (fixing the limitations of the one proposed). I'm happy to answer any questions on the subject!

The issue with Scenes (versus DynamicScenes) is that there is no way to serialize them. This is not for 3d models, but more for data entities. I've been using this to generate items and stat entities for my RPG.

The issue with Scenes (versus DynamicScenes) is that there is no way to serialize them.

You should be able to use DynamicScene::from_scene to convert scenes into dynamic scenes and then serialize.

Can you convert it back though? There's nothing in DynamicScene to convert it back in order to spawn it as a child or instance. I've tried spawning the DynamicScene into a new world to make a Scene but it panics due to there being no TypeRegistry in the new world.

You're right, we should probably improve the API for DynamicScene to have parity with Scene, including commands.

I've tried spawning the DynamicScene into a new world to make a Scene but it panics due to there being no TypeRegistry in the new world.

I think you can clone the app's type registry and insert it in the scene's world, then use DynamicScene::write_to_world() (with an empty entity map).

Updated to add some features. I still think this method has some merit, since it returns an entity that can be used and/or stored immediately.

@Semihazah This looking good :) Can you click "Resolve" on the comments that you've addressed so reviewers can see what's outstanding?

I feel that if you fleshed out of few parts, this could be a useful third party plugin rather than an example:

using another custom file extension for prefab, with a custom loader that would still call the scene loader
adding checks on the fact that there is only one entity when writing the scene
adding a prefab writer system that would use the IOTaskPool to write files

* adding checks on the fact that there is only one entity when writing the scene

That's no longer necessary, you can have multiple entities in the scene and they'll all be loaded and mapped.

That's no longer necessary, you can have multiple entities in the scene and they'll all be loaded and mapped.

oh right I was confused with this limitation:
 Only components from the FIRST entity listed in the file will be inserted into the provided entity.
but on re-read it's clearer
Then I agree that we should first bring parity to DynamicScene from Scene which would make this example a lot simpler

This PR adds a new example. Adding module and item level doc comments, as described in:

#3951 and
#4438,

would be really useful to those who will browse examples.

The example description should go to the top, with //! comments. Documenting components where appropriate is also good.

Q: What's a prefab?
This PR adds the concept of a "prefab" but never defines what it means or why you would want to use it. I know the term is used in Unity, but I've never used Unity.

this looks too complex to be an example, and too limited to be merged in engine

source: gharchive/pull-request

authors: Davier Nilirad Semihazah alice-i-cecile mockersf viridia

repo: bevyengine/bevy

license_type: permissive

license_source: github-api


text:
Feat: Improved GLTF loader, implement typed asset loading

Two features:
(1) Issue #367 : I updated asset loading and implemented load_typed() to use alongside load_untyped(). I did this by changing the extensions-to-loader hashmap to have a key of (TypeId, String) instead of the previous String. This cleanly supports having multiple AssetLoader with different T but the same file extension.
(2) Implemented texture reading for GLTF.
(2a) Retouched the GLTF loading procedure so that instead of checking just the first node, it reads all nodes, meshes and textures. Then it returns just the first valid mesh/texture, depending on what you're requesting. This opens the door for potentially loading multiple assets from a GLTF file, but that is a much larger scope than this PR, because it is not possible to create and return multiple handles from within an AssetLoader at the moment.
Future work:

This work was mostly orthogonal to loading GLTFs as scenes.
A GLTF has to be parsed multiple times in order to get everything needed to load a model. This is highly inefficient -- as you can see in the 3d/load_model example, it takes a moment for the cubes to appear -- but as per (2a) it's not possible to easily solve right now.
We still only allow returning the first mesh or texture from a GLTF, when it can contain any number of files.

Would this PR solve #367 ?

Would this PR solve #367 ?

I think it should. You can't request, say, a Texture from a hypothetical OBJ loader because the list of extensions to loaders is keyed by type as well as extension.

Merge conflict resolved.

One of the possible workarounds for scene loading could be a load_scene method in AssetServer that will work similar to load_from_folder, but instead of the recursive directory walk, it can open a GLTF file and walk through assets, adding them.
I have suggested to use URI-like notation to access the assets and @cart liked it. For example, if you load spider.gltf, you can access assets using artificial paths like:

spider.gltf#model -> mesh
spider.gltf#skin -> texture
spider.gltf#walk -> walk animation
spider.gltf#jump -> jump animation

Alternative to # characters could be ? or :

I was going to implement the URI-like notation as well, way back when I first wrote this PR, but I ran out of steam, partially because it didn't seem like it would get accepted soon.

Yeah sorry for not responding sooner. I intentionally put this off because the asset system is either going to be replaced by atelier-assets or modified to account for cases like this better.
I don't want to merge anything that extends and/or hacks around the current asset system, as it will almost certainly be replaced in short order.
If we go with atelier, aspects of the implementation in this pr will need to change. If we go with extending the current asset system, aspects of this pr will need to change.
Again, I'm really sorry for not keeping you in the loop. I really appreciate the work you put in here and leaving you in the dark on my current thoughts for so long was disrespectful.

It's just that Ateliers been happening soon:tm: for ages, and in the
meanwhile people can't load GLTF files properly. I feel like there's value
in merging this PR for the here and now.
On Fri, Sep 18, 2020, 00:26 Carter Anderson notifications@github.com
wrote:

Yeah sorry for not responding sooner. I intentionally put this off because
the asset system is either going to be replaced by atelier-assets or
modified to account for cases like this better.
I don't want to merge anything that extends and/or hacks around the
current asset system, as it will almost certainly be replaced in short
order.
If we go with atelier, aspects of the implementation in this pr will need
to change. If we go with extending the current asset system, aspects of
this pr will need to change.
Again, I'm really sorry for not keeping you in the loop. I really
appreciate the work you put in here and leaving you in the dark on my
current thoughts for so long was disrespectful.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bevyengine/bevy/pull/378#issuecomment-694532415, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA22VOZRQCZTTJNCM7JJ4FTSGKEINANCNFSM4QNPPSIA
.

I believe current bevy_asset can stay as  a part of the engine for longer, even as bevy_asset_legacy or bevy_legacy/bevy_asset, being deprecated, whatever path you choose to go either rewrite or switch to atelier.
Another thought on the topic, is that it could be optional choice to stay with atelier, or native bevy_asset, or even a 3rd party bevy_asset package, because for some projects atelier could be kind of an overkill.

authors: Lowentwickler andreasterrius cart skairunner


text:
scene_viewer: load cameras

Objective
glTF files can contain cameras. Currently the scene viewer example uses a camera defined in the file if possible, otherwise it spawns a new one. It would be nice if instead it could load all the cameras and cycle through them, while also having a separate user-controller camera.
Solution

instead of just a camera that is already defined, always spawn a new separate user-controller camera
maintain a list of loaded cameras and cycle through them (wrapping to the user-controller camera) when pressing C

This matches the behavious that https://github.khronos.org/glTF-Sample-Viewer-Release/ has.
Implementation notes

The gltf scene asset loader just spawns the cameras into the world, but does not return a mapping of camera index to bevy entity. So instead the scene_viewer example just collects all spawned cameras with a good old query.iter().collect(), so the order is unspecified and may change between runs.

Demo
https://user-images.githubusercontent.com/22177966/161826637-40161482-5b3b-4df5-aae8-1d5e9b918393.mp4
using the virtual city glTF sample file: https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0/VC

bors r+

(we can get to my nits later)

authors: alice-i-cecile jakobhellermann


text:
Support loading ROMs from file

Drag & drop, or something like that.
See https://github.com/bfirsh/jsnes/pull/2 for previous implementation.

Nice, thank you for the update on the moved repo. :)

source: gharchive/issue

authors: bfirsh jancborchardt

repo: bfirsh/jsnes-web

license_source: bigquery


text:
Add TypeScript definition

Related to https://github.com/sindresorhus/refined-github/pull/1750

Related to https://github.com/sindresorhus/refined-github/pull/1750

Published as @next.

You can add it to RGH as is and if it works I'll publish it. RGH can stay with the prerelease.

authors: bfred-it nickytonline

license: MIT


text:
Adding the NANOG88 Video Recording

Added the NANOG88 video recording

I have read the CLA Document and I hereby sign the CLA

recheck

I have read the CLA Document and I hereby sign the CLA

recheck

recheck

@tking I broken the CLA when I added branch protection, I think I have it fixed now, but you might need to sign again.

recheck

authors: grizz tking

repo: bgp/autopeer


text:
How to log jongo quries?

Can someone suggest simple way to debug jongo queries?

What about using a RawResultHandler
ResultHandler<DBObject> handler = new RawResultHandler<DBObject>();
Friend john = new Friend("John", "22 Wall Street Avenue");
collection.save(john);

DBObject result = collection.findOne().map(handler);
result.toString()...

I had problems with aggregation query. In general enabling db profiler - http://docs.mongodb.org/manual/tutorial/manage-the-database-profiler/ - is enough. It would be great to get similar info as app logs (manage it by slf4j)

It would indeed be nice to get logging on what queries are executed.
For example a logging statement on Find.map (LOGGER is and slf4j Logger in this example)
LOGGER.trace("{}: db.{}.find({}, {})", collection.getDB().getName(), collection.getName(), query.toDBObject(), getFieldsAsDBObject());

This is possible with aspectj load-time weaving, which I'm trying to avoid using.

You are right.
Here is the issue #27 (created in 2012!) to add logging.
It should be create to add logging capabilities without dependency to logging API

authors: bguerout fedotxxl haraldrombaut

repo: bguerout/jongo


text:
Advance next page does not work when I switch between amount of data to display

There seems to be a small bug when switching between the amount of data to display, as after doing so and clicking next it doesn't seem to respond until it is clicked twice.
Grabación de pantalla desde 2024-05-18 16-41-27.webm

Hi,
Its not a bug, buttons will be disabled till response not completed. you clicked before response completed, so you feel like its not working on first click but actually its works.

@bhaveshpatel200
It does not seem to be that, you can verify in the implementation of the following link:
https://angular.vristo.sbthemes.com/datatables/basic
In which when you change from 10 to 20 and click the next button (not the number), it does not work until you click it twice.
I already tried waiting a while without clicking, about 5 seconds and it works. The curious thing is that if we click on any number, even immediately it works, it is strange.
Translated with DeepL.com (free version)

Yes got it, will check once getting time and update in next release.

Can you please check its working in our demo.
https://ng-datatable-document.vercel.app/static-mode


text:
Weird validation in Django Admin when using array + choice + multiselect

Hey!
I encountered a strange validation behavior when using the below schema:
{
    "type": "object",
    "keys": {
        "source_ids": {
            "type": "array",
            "minItems": 1,
            "uniqueItems": true,
            "items": {
                "type": "string",
                "widget": "multiselect",
                "title": "Source fields",
                "choices": [
                    {"title": "Test", "value": "b7f368af-a173-4079-8348-e1b9625f220f"},
                    {"title": "Test 2", "value": "277d180c-7be0-495a-8685-340e08734599"},
                ],
            },
        }
    },
}

When trying to save the form, validation correctly shows: Minimum 1 items required.
But it's setting up the initial values of the dropdowns to empty string, see below:

When saving the form again, validation correctly shows: Invalid choice

Using widget.validate_on_submit=True helps with the first problem (setting initial values for dropdowns) but it does not behave correctly with the choices, see below

Expected behavior:

Validation error shows: Minimum 1 items required.
Dropdows stays empty

Released in v2.23.0.

authors: AlTosterino bhch

repo: bhch/django-jsonform


text:
Lint: prompt_background_jobs bad math expressions

Some simple lint.  It should also cause the occasional variable problem go away.
prompt_background_jobs:2: bad math expression: operand expected at end of string

Thx @docwhat

authors: docwhat dritter


text:
[Enhancement] Add support for RHEL icon

Adds support for Redhat icon in nerdfont-complete if os_release_id == 'rhel'.  Also added -s flag to grep command used to assign os_release_id in utilities.zsh.  This prevents an error from being displayed if /etc/os-release does not exist (e.g. rhel/centos 6).  Grep flag change fixes Bug https://github.com/bhilburn/powerlevel9k/issues/974 and duplicates PR https://github.com/bhilburn/powerlevel9k/pull/981.  I had not seen that PR until after I created this.

Sorry for the delay. I merged your PR into next (our development branch).
Merged with 8c981597e77a4806921926534c8ecedd975bcd09 and 8f7fc16fe684dd4c2cce453c4728a1ff9729a7e1 .
Thx @markleary

authors: dritter markleary


text:
🛑 Iwanson International GmbH - (www,https) is down

In 65fa712, Iwanson International GmbH - (www,https) (https://www.iwanson.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Iwanson International GmbH - (www,https) is back up in 0436f00.

repo: bhiwolfc/upptime


text:
Collected Water

Please merge this PR.

Thank you for your contribution!

authors: Spardha-hash bhumikatewary

repo: bhumikatewary/Practice-Problems


text:
Add code for rules table

This PR adds code for printing all available rules, partly solving https://github.com/biaslab/RxInfer.jl/issues/74. Just not sure how to call the implemented print_rules_table() inside the docs of RxInfer.jl. I presume this table would deserve its own subsection under user guide - model specification at https://biaslab.github.io/RxInfer.jl/stable/manuals/model-specification/

@bartvanerp I've put your table to the documentation (in the index.html we should move it to other place later). One thing I noticed is that meta type is not present in the table. The table has "duplicate" rules which differ only in meta specification and meta by itself is quite important so I suggest to add it to the table as well.

I added the meta field and moved the location of the table with rules in the docs. Furthermore I added the table printing to  src and added Markdown into the dependencies. The main idea is that now everyone can just print the table in case they think they need it, but this is something that can be discussed.

authors: bartvanerp bvdmitri


text:
Splatting does not work (with non-linear node)

The following code excerpt fails:
function foo(x...)
    return sum(x)
end

@model function model_test()
    z = randomvar(10)
    for k in 1:10
        z[k] ~ NormalMeanVariance(0.0, 1.0)
    end
    x ~ foo(z...)
    y = datavar(Float64)
    y ~ NormalMeanVariance(x, 1.0)

end

with error MethodError: no method matching as_variable(::FactorGraphModel, ::RandomVariable, ::RandomVariable, ::RandomVariable, ::RandomVariable, ::RandomVariable, ::RandomVariable, ::RandomVariable, ::RandomVariable, ::RandomVariable, ::RandomVariable).
It likely has to do with the splat operator, possibly in combination with the non-linear node.
This functionality is very useful for dealing with multiple random variables going into a non-linear node. This prevents us from having to write foo(z[1], z[2], ....), which is not automatable when the number is a hyperparameter.

Should also be fixed in graphppl 4.0 but I'll close this myself after we merge everything and I've checked.

@wouterwln why is this issue closed? This doesn't seem working in RxInfer.jl

authors: albertpod bartvanerp wouterwln


text:
Fixing the audio resource loading issue

Fixing the audio resource loading issue

@vipinpaul this issue is fixed, Now audio resources can be imported. App is not breaking.

authors: selvabenz vipinpaul


text:
Feature：webpack-plugin-https

Automatically generate https certificates for dev server.

Had implement in @montagejs/issue-cert-plus

repo: bigbigDreamer/montage


text:
build badge should be green!

:)

Woops, my bad.

authors: TheAlphaNerd joates

repo: bigboringsystem/bigboringsystem


text:
server api: to slash or not slash?

This ticket aims to reconsider the current position on trailing slashes as it is inconvenient for future client implementations.
See related comment: https://github.com/bigchaindb/bigchaindb/issues/362#issuecomment-241419134

solved by #588

authors: diminator sbellem

repo: bigchaindb/bigchaindb


text:
Moved data models docs back to server

As discussed this morning with @TimDaub @libscott and @sbellem , I moved the docs about the data models from the "root" BigchainDB docs back to the Server docs.
I also made a few edits to those docs.
Those docs will probably be revised or even replaced in the coming days, because this is something @libscott is working on. They'll also have to be updated to account for divisible assets. And more...

Current coverage is 96.57% (diff: 100%)

Merging #804 into master will not change coverage

@@             master       #804   diff @@
==========================================
  Files            26         26
  Lines          1634       1634
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1578       1578
  Misses           56         56
  Partials          0          0

Powered by Codecov. Last update c65d277...c5bf327

This PR will conflict quite substantially with PR #807 because it edited some of the same docs pages---after moving them.
Independent of PR #807, this PR is also a bit unfocused in that it both moved and edited some docs. I think it might be better to break it up into two smaller and more-focused PRs, one that moves the docs, and one that does some edits.
Therefore I'm closing this PR and will create two new PRs in its place.

authors: codecov-io ttmc


text:
[MANGO-68] Spark Upgrade

Resolves #68

Merged build triggered.

Merged build started.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/mango-prb/49/
Test PASSed.

authors: AmplabJenkins erictu

repo: bigdatagenomics/mango


text:
Specify expanding container in parent

Hi,
currently children are expanded from the bottom. But I would like to specify a container, which expands as I click on the parent. Let's say I have three containers in my parent namely a header, a main container and a footer, which are layouted horizontally. When I click on the parent the main container, which is in the middle should open moving the footer down as well (not overlapping it).
I'd like to hear your thoughts on that idea. Maybe I can help you and implement it myself if you are (too) busy.
Best regards
dasheck

Having a hard time following the situation you describe. Maybe some quick drawings showing the before and after of what you want would help clarify?

No problem at all. I will add some mockups when I get home.

Thanks @dasheck0 that cleared it up. Unfortunately I don't see that being in our roadmap right now, changes a lot about the behaviour of our content and expansion. Might be a better fit for a custom solution vs something to be rolled into this library.

Hi guys,
Dasheck, did you find some workaround ?
Samy

@samy-baili Not so far. Fortunately we changed the way the container behaves, which made the request obsolete. Still as fas as I know there is no library, which provides proper and flexible item expansion for lists and/or recyclerviews.

Ok too bad.
Thank you very much for your reactivity

authors: dasheck0 paul-turner samy-baili

repo: bignerdranch/expandable-recycler-view

license: mit


text:
Stop word filtering

Added code for stopword filtering based on wordfreq (for available languages).

Thanks, it’s done

Just to clarify. I added this pull request to replace nltk stopwords with stopwords based on wordfreq (which also supports more languages than nltk), but the code has changed since I wrote this request. When Oscar sample filter is finalised, the conflict with this pull request can be easily solved.

Just to clarify. I added this pull request to replace nltk stopwords with stopwords based on wordfreq (which also supports more languages than nltk), but the code has changed since I wrote this request. When Oscar sample filter is finalised, the conflict with this pull request can be easily solved.

Can we resolve conflicts and merge this?

Can we resolve conflicts and merge this?

It's on the to-do list, I'll do it for sure

See https://github.com/bigscience-workshop/data_tooling/issues/85


text:
🛑 Jefferson Real is down

In 0a5a093, Jefferson Real (https://jeffersonreal.uk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jefferson Real is back up in e5ef814.

repo: bigupjeff/my-site-uptime-monitor


text:
No Flatpak manifest found in this workspace.

terminal output:
2023-01-03 14:33:13.888 [error] Error: No Flatpak manifest found in this workspace.
    at ManifestManager.<anonymous> (/home/me/.vscode/extensions/bilelmoussaoui.flatpak-vscode-0.0.30/out/manifestManager.js:214:23)
    at Generator.next (<anonymous>)
    at fulfilled (/home/me/.vscode/extensions/bilelmoussaoui.flatpak-vscode-0.0.30/out/manifestManager.js:5:58)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) flatpak-vscode.build-and-run {"value":"bilelmoussaoui.flatpak-vscode","c":"bilelmoussaoui.flatpak-vscode"}

it happens at radom, sometimes it works sometimes it does not

Can you show the steps in reproducing the error?

Quite simply, I open a folder which directly contains a flatpak manifest

No commands were ran?

@SeaDve what do you mean with commands?

terminal commands
VS code commands (ctrl + shift + p)
commands ran by other extensions?

I have the same issue. I re-opened a project that previously worked fine. Now it tells me that "No Flatpak manifest found in this workspace".

I did some debugging of the plugin. It had a lot of log entries for "Trying to parse potential Flatpak manifest ". These were all in the build-dir directory of a previous manual flatpak-builder run. After deleting build-dir the plugin worked as expected. Is there a maximum number of files it tries to parse? Maybe a different message show be shown when the maximum is reached?

I did some debugging of the plugin. It had a lot of log entries for "Trying to parse potential Flatpak manifest ". These were all in the build-dir directory of a previous manual flatpak-builder run. After deleting build-dir the plugin worked as expected. Is there a maximum number of files it tries to parse? Maybe a different message show be shown when the maximum is reached?

It might be caused by this limit: https://github.com/bilelmoussaoui/flatpak-vscode/blob/eab905106292c343c9ac47eccadaa0427f85886a/src/manifestUtils.ts#L24

I guess the real issue is on the ignore glob pattern at https://github.com/bilelmoussaoui/flatpak-vscode/blob/eab905106292c343c9ac47eccadaa0427f85886a/src/manifestUtils.ts#L23

authors: SeaDve bilelmoussaoui caspermeijn mijorus

repo: bilelmoussaoui/flatpak-vscode


text:
RFC: consider removing Flatpak: rebuild command

Consider removing flatpak-vscode.rebuild and move its functionality to flatpak-vscode.run.
The rationale is it would be less clutter and confusion with flatpak-vscode.run. Additionally, it helps avoid accidentally running without rebuilding.

The reason I kept the two steps separate is we don't have a way to track the sources files if there were any changes and you would probably end up waiting a couple of seconds before the app is launched which could be not great :/

there's probably a vscode api to track modified file

The issue is to figure out if those files are part of the source code. That is something normally the build system can know

Please don't get rid of the rebuild / run separation. Sometimes its just convenient to rerun the app to check something even when some files are already modified.

I see, that makes sense.
Since the "run" button used in #55 is mapped to rebuild command, it would make sense to rename it to just run and rename run command to run-without-rebuild or something. Mainly for coherency, and to convey semantic oposite of stop

I think we can drop rebuild and only keep build here. We know whether the app was built once or not, so we can just make "build" triggers a "rebuild" instead. Make the run button triggers both build & run, and the run command from the palette only triggers run.

Make the run button triggers both build & run, and the run command from the palette only triggers run.

I think we want to have the run button to have the same behavior as the command palette one (for coherence), or to atleast have that behavior as an entry in the command palette

authors: SeaDve bilelmoussaoui flxzt


text:
Update README.md

Add spot.xyz

Thanks!

authors: billmei ghempton

repo: billmei/every-proximity-chat-app


text:
Executable installer

I would like to have installer. its more user-friendly.
** create it using a installer program. **
create a exe using it

we are using pyinstaller to make the executables currently.
For making setup files, we can use

innosetup
nsis

some modifications shall be done to the github workflows

@arnav56745 This idea won't hold much importance now as biscuit has been added to pypi
installation
pip install biscuit-editor

running
biscuit

repo: billyeatcookies/Biscuit


text:
#877	Het symbool voor tegel 150x300 en 300x150 in zogenaamd “blokverband”

#877	Het symbool voor tegel 150x300 en 300x150 in zogenaamd “blokverband” voor dikke als dunne tegels ontbreekt.

"toevoegen symbolen:
SVH-TEGEL_150X300_DIK_BLOK_KL-SO
V-SVH-TEGEL_150X300_DIK_BLOK_KL-SO
SVH-TEGEL_150X300_DUN_BLOK_KL-SO
V-SVH-TEGEL_150X300_DUN_BLOK_KL-SO
SVH-TEGEL_150X300_DIK_BLOK-SO
V-SVH-TEGEL_150X300_DIK_BLOK-SO
SVH-TEGEL_150X300_DUN_BLOK-SO
V-SVH-TEGEL_150X300_DUN_BLOK-SO
ook symbolen toevoegen in database (d.m.v. Excel)"

300x150 én 150x300 heeft te maken met de ligging van de richting van het halfsteensverband. Maar dat is niet voor alle afmetingen consequent doorgevoerd. Er zijn wel mogelijkheden voor verbeteringen in de verhardingsymbolen en patterns. Wellicht deze inventariseren en dan een voorstel maken voor toe te voegen dan wel te verwijderen arceringen en symbolen.

Ik heb een uitgebreide analyse gemaakt op alle verhardingssymbolen.
Voorstel tot te verwijderen of aan te passen symbolen opgenomen.
DWG volgt door Elisabeth.
Aanvullende symbolen volgen..

@MvanderHulst  hier staat dehet bestand: https://github.com/nl-digigo/NLCS/blob/main/ontwikkeling/bijlagen_bij_issues/56/ALLE SVH SYMBOLEN.dwg

Onderstaand vanuit de DWG alle rood gemarkeerde gecorrigeerde symbolen::

SVH-TEGEL_150X300_DIK_ELLEBOOG-SO
SVH-TEGEL_150X300_DIK_ELLEBOOG_STIP-SO
SVH-TEGEL_150X300_DUN_ELLEBOOG-SO
SVH-TEGEL_150X300_DUN_ELLEBOOG_STIP-SO
SVH-TEGEL_300X150_DIK_LINT-SO
SVH-TEGEL_300X150_DIK_LINT_STIP-SO
SVH-TEGEL_300X150_DUN_LINT-SO
SVH-TEGEL_600X200_HALFST-SO
SVH-TEGEL_600X200_LINT-SO
V-SVH-TEGEL_150X300_DIK_ELLEBOOG-SO
V-SVH-TEGEL_150X300_DIK_ELLEBOOG_STIP-SO
V-SVH-TEGEL_150X300_DUN_ELLEBOOG-SO
V-SVH-TEGEL_150X300_DUN_ELLEBOOG_STIP-SO
V-SVH-TEGEL_300X150_DIK_LINT-SO
V-SVH-TEGEL_300X150_DIK_LINT_KL-SO
V-SVH-TEGEL_300X150_DIK_LINT_STIP-SO
V-SVH-TEGEL_300X150_DUN_LINT-SO
V-SVH-TEGEL_600X200_HALFST-SO
V-SVH-TEGEL_600X200_LINT-SO

Voorstel te vervallen symbolen:
dit zijn allemaal niets zeggende, off amper zichtbare symbolen waarvan in verwacht dat deze NOOIT gebruikt worden.

SVH-COBBLESTONE_KL-SO
SVH-COBBLESTONE-SO
SVH-FUNDERING_BIMS_KL-SO
SVH-FUNDERING_BIMS-SO
SVH-FUNDERING_EPS_KL-SO
SVH-FUNDERING_EPS-SO
SVH-FUNDERING_GRANULAAT_KL-SO
SVH-FUNDERING_GRANULAAT_MENG_02_KL-SO
SVH-FUNDERING_GRANULAAT_MENG_02-SO
SVH-FUNDERING_GRANULAAT_PUIN_KL-SO
SVH-FUNDERING_GRANULAAT_PUIN-SO
SVH-FUNDERING_GRANULAAT_SINTELS_KL-SO
SVH-FUNDERING_GRANULAAT_SINTELS-SO
SVH-FUNDERING_GRANULAAT-SO
SVH-FUNDERING_OVERIG_KL-SO
SVH-FUNDERING_OVERIG-SO
SVH-GESLOTEN_KL-SO
SVH-GESLOTEN-SO
SVH-GLAS_KL-SO
SVH-GLAS-SO
SVH-HALFVERHARDING_01-SO
SVH-HALFVERHARDING_GRIND_02_KL-SO
SVH-HALFVERHARDING_GRIND_02-SO
SVH-HOUTSNIPPERS_KL-SO
SVH-HOUTSNIPPERS-SO
SVH-HSTEEN_KL-SO
SVH-HSTEEN-SO
SVH-KALKZANDSTEEN_KL-SO
SVH-KALKZANDSTEEN-SO
SVH-METSELWERK_KL-SO
SVH-METSELWERK-SO
SVH-NATUURSTEEN_02_KL-SO
SVH-NATUURSTEEN_02-SO
SVH-SIERBESTRATING_02_KL-SO
SVH-SIERBESTRATING_02-SO
SVH-SIERTEGEL_KL-SO
SVH-SIERTEGEL-SO
SVH-SPECIAAL_01_KL-SO
SVH-SPECIAAL_01-SO
SVH-SPECIAAL_02_KL-SO
SVH-SPECIAAL_02-SO
SVH-SPECIAAL_OVERIG_01_KL-SO
SVH-SPECIAAL_OVERIG_01-SO
SVH-SPECIAAL_OVERIG_02_KL-SO
SVH-SPECIAAL_OVERIG_02-SO
SVH-SPECIAAL_OVERIG_KOPSHOUT_KL-SO
SVH-SPECIAAL_OVERIG_KOPSHOUT-SO
SVH-SPECIAAL_OVERIG_LANGSHOUT_KL-SO
SVH-SPECIAAL_OVERIG_LANGSHOUT-SO
SVH-SPECIAAL_OVERIG_TRANENPLAAT_01_KL-SO
SVH-SPECIAAL_OVERIG_TRANENPLAAT_01-SO
SVH-SPECIAAL_OVERIG_TRANENPLAAT_02_KL-SO
SVH-SPECIAAL_OVERIG_TRANENPLAAT_02-SO
V-SVH-COBBLESTONE_KL-SO
V-SVH-COBBLESTONE-SO
V-SVH-FUNDERING_BIMS_KL-SO
V-SVH-FUNDERING_BIMS-SO
V-SVH-FUNDERING_EPS_KL-SO
V-SVH-FUNDERING_EPS-SO
V-SVH-FUNDERING_GRANULAAT_KL-SO
V-SVH-FUNDERING_GRANULAAT_MENG_02_KL-SO
V-SVH-FUNDERING_GRANULAAT_MENG_02-SO
V-SVH-FUNDERING_GRANULAAT_PUIN_KL-SO
V-SVH-FUNDERING_GRANULAAT_PUIN-SO
V-SVH-FUNDERING_GRANULAAT_SINTELS_KL-SO
V-SVH-FUNDERING_GRANULAAT_SINTELS-SO
V-SVH-FUNDERING_GRANULAAT-SO
V-SVH-FUNDERING_OVERIG_KL-SO
V-SVH-FUNDERING_OVERIG-SO
V-SVH-GESLOTEN_KL-SO
V-SVH-GESLOTEN-SO
V-SVH-GLAS_KL-SO
V-SVH-GLAS-SO
V-SVH-HALFVERHARDING_01-SO
V-SVH-HALFVERHARDING_GRIND_02_KL-SO
V-SVH-HALFVERHARDING_GRIND_02-SO
V-SVH-HOUTSNIPPERS_KL-SO
V-SVH-HOUTSNIPPERS-SO
V-SVH-HSTEEN_KL-SO
V-SVH-HSTEEN-SO
V-SVH-KALKZANDSTEEN_KL-SO
V-SVH-KALKZANDSTEEN-SO
V-SVH-METSELWERK_KL-SO
V-SVH-METSELWERK-SO
V-SVH-NATUURSTEEN_02_KL-SO
V-SVH-NATUURSTEEN_02-SO
V-SVH-SIERBESTRATING_02_KL-SO
V-SVH-SIERBESTRATING_02-SO
V-SVH-SIERTEGEL_KL-SO
V-SVH-SIERTEGEL-SO
V-SVH-SPECIAAL_01_KL-SO
V-SVH-SPECIAAL_01-SO
V-SVH-SPECIAAL_02_KL-SO
V-SVH-SPECIAAL_02-SO
V-SVH-SPECIAAL_OVERIG_01_KL-SO
V-SVH-SPECIAAL_OVERIG_01-SO
V-SVH-SPECIAAL_OVERIG_02_KL-SO
V-SVH-SPECIAAL_OVERIG_02-SO
V-SVH-SPECIAAL_OVERIG_KOPSHOUT_KL-SO
V-SVH-SPECIAAL_OVERIG_KOPSHOUT-SO
V-SVH-SPECIAAL_OVERIG_LANGSHOUT_KL-SO
V-SVH-SPECIAAL_OVERIG_LANGSHOUT-SO
V-SVH-SPECIAAL_OVERIG_TRANENPLAAT_01_KL-SO
V-SVH-SPECIAAL_OVERIG_TRANENPLAAT_01-SO
V-SVH-SPECIAAL_OVERIG_TRANENPLAAT_02_KL-SO
V-SVH-SPECIAAL_OVERIG_TRANENPLAAT_02-SO

Voorstel voor alle te vervallen TEGEL symbolen.
Dit zijn all varianten met de 'stip' of 'strepen' erin.
Nnood hoeven toepassen en totaal overbodige noodzaak.
Alle standaard symbolen hebben al 2 attributes, waarin je alles kwijt kan.

SVH-TEGEL_150X300_DIK_ELLEBOOG_STIP_KL-SO
SVH-TEGEL_150X300_DIK_ELLEBOOG_STIP-SO
SVH-TEGEL_150X300_DUN_ELLEBOOG_STIP_KL-SO
SVH-TEGEL_150X300_DUN_ELLEBOOG_STIP-SO
SVH-TEGEL_300X150_DIK_ELLEBOOG_STIP_KL-SO
SVH-TEGEL_300X150_DIK_ELLEBOOG_STIP-SO
SVH-TEGEL_300X150_DIK_HALFST_STIP_KL-SO
SVH-TEGEL_300X150_DIK_HALFST_STIP-SO
SVH-TEGEL_300X150_DIK_LINT_STIP_KL-SO
SVH-TEGEL_300X150_DIK_LINT_STIP-SO
SVH-TEGEL_300X150_DUN_ELLEBOOG_STIP_KL-SO
SVH-TEGEL_300X150_DUN_ELLEBOOG_STIP-SO
SVH-TEGEL_300X150_DUN_HALFST_STIP_KL-SO
SVH-TEGEL_300X150_DUN_HALFST_STIP-SO
SVH-TEGEL_300X150_DUN_LINT_STIP_KL-SO
SVH-TEGEL_300X150_DUN_LINT_STIP-SO
SVH-TEGEL_300X300_DIK_BLOK_STIP_KL-SO
SVH-TEGEL_300X300_DIK_BLOK_STIP-SO
SVH-TEGEL_300X300_DIK_HALFST_STIP_KL-SO
SVH-TEGEL_300X300_DIK_HALFST_STIP-SO
SVH-TEGEL_300X300_DIK_LINT_STIP_KL-SO
SVH-TEGEL_300X300_DIK_LINT_STIP-SO
SVH-TEGEL_300X300_DUN_BLOK_STIP_KL-SO
SVH-TEGEL_300X300_DUN_BLOK_STIP-SO
SVH-TEGEL_300X300_DUN_HALFST_STIP_KL-SO
SVH-TEGEL_300X300_DUN_HALFST_STIP-SO
SVH-TEGEL_300X300_DUN_LINT_STIP_KL-SO
SVH-TEGEL_300X300_DUN_LINT_STIP-SO
SVH-TEGEL_400X400_HALFST_STIP_KL-SO
SVH-TEGEL_400X400_HALFST_STIP-SO
SVH-TEGEL_400X400_HALFST_STREEP_KL-SO
SVH-TEGEL_400X400_HALFST_STREEP-SO
SVH-TEGEL_400X400_LINT_STIP_KL-SO
SVH-TEGEL_400X400_LINT_STIP-SO
SVH-TEGEL_400X400_LINT_STREEP_KL-SO
SVH-TEGEL_400X400_LINT_STREEP-SO
SVH-TEGEL_600X600_HALFST_STIP-SO
SVH-TEGEL_600X600_LINT_STIP_KL-SO
SVH-TEGEL_600X600_LINT_STIP-SO
SVH-TEGEL_BLOK_STIP_01_KL-SO
SVH-TEGEL_BLOK_STIP_01-SO
SVH-TEGEL_BLOK_STIP_02_KL-SO
SVH-TEGEL_BLOK_STIP_02-SO
V-SVH-TEGEL_150X300_DIK_ELLEBOOG_STIP_KL-SO
V-SVH-TEGEL_150X300_DIK_ELLEBOOG_STIP-SO
V-SVH-TEGEL_150X300_DUN_ELLEBOOG_STIP_KL-SO
V-SVH-TEGEL_150X300_DUN_ELLEBOOG_STIP-SO
V-SVH-TEGEL_300X150_DIK_ELLEBOOG_STIP_KL-SO
V-SVH-TEGEL_300X150_DIK_ELLEBOOG_STIP-SO
V-SVH-TEGEL_300X150_DIK_HALFST_STIP_KL-SO
V-SVH-TEGEL_300X150_DIK_HALFST_STIP-SO
V-SVH-TEGEL_300X150_DIK_LINT_STIP_KL-SO
V-SVH-TEGEL_300X150_DIK_LINT_STIP-SO
V-SVH-TEGEL_300X150_DUN_ELLEBOOG_STIP_KL-SO
V-SVH-TEGEL_300X150_DUN_ELLEBOOG_STIP-SO
V-SVH-TEGEL_300X150_DUN_HALFST_STIP_KL-SO
V-SVH-TEGEL_300X150_DUN_HALFST_STIP-SO
V-SVH-TEGEL_300X150_DUN_LINT_STIP_KL-SO
V-SVH-TEGEL_300X150_DUN_LINT_STIP-SO
V-SVH-TEGEL_300X300_DIK_BLOK_STIP_KL-SO
V-SVH-TEGEL_300X300_DIK_BLOK_STIP-SO
V-SVH-TEGEL_300X300_DIK_HALFST_STIP_KL-SO
V-SVH-TEGEL_300X300_DIK_HALFST_STIP-SO
V-SVH-TEGEL_300X300_DIK_LINT_STIP_KL-SO
V-SVH-TEGEL_300X300_DIK_LINT_STIP-SO
V-SVH-TEGEL_300X300_DUN_BLOK_STIP_KL-SO
V-SVH-TEGEL_300X300_DUN_BLOK_STIP-SO
V-SVH-TEGEL_300X300_DUN_HALFST_STIP_KL-SO
V-SVH-TEGEL_300X300_DUN_HALFST_STIP-SO
V-SVH-TEGEL_300X300_DUN_LINT_STIP_KL-SO
V-SVH-TEGEL_300X300_DUN_LINT_STIP-SO
V-SVH-TEGEL_400X400_HALFST_STIP_KL-SO
V-SVH-TEGEL_400X400_HALFST_STIP-SO
V-SVH-TEGEL_400X400_HALFST_STREEP_KL-SO
V-SVH-TEGEL_400X400_HALFST_STREEP-SO
V-SVH-TEGEL_400X400_LINT_STIP_KL-SO
V-SVH-TEGEL_400X400_LINT_STIP-SO
V-SVH-TEGEL_400X400_LINT_STREEP_KL-SO
V-SVH-TEGEL_400X400_LINT_STREEP-SO
V-SVH-TEGEL_600X600_HALFST_STIP-SO
V-SVH-TEGEL_600X600_LINT_STIP_KL-SO
V-SVH-TEGEL_600X600_LINT_STIP-SO
V-SVH-TEGEL_BLOK_STIP_01_KL-SO
V-SVH-TEGEL_BLOK_STIP_01-SO
V-SVH-TEGEL_BLOK_STIP_02_KL-SO
V-SVH-TEGEL_BLOK_STIP_02-SO

En dan doe ik weer een oud voorstel: geen extra _KL-SO symbolen meer maar één goed symbool per object. Scheelt ook weer een heleboel symbolen. Waarom moet je een groot én een klein symbool hebben?

@SanderNijhof voor nu focus ik mij nog even op de 'huidige' symbolen. Om daar een flinke bezem doorheen te halen.
De kleine symbolen hoeven van mij ook niet, gezien die niet leesbaar zijn.
Ik pas dan liever een clipping toe op de grote symbolen indien nodig.

Volgende stap is de controle op noodzaak:
mijn referentiekader:

Voorstel te vervallen:
SVH-TEGEL_1000X1000_BLOK_KL-SO
SVH-TEGEL_1000X1000_BLOK-SO
SVH-TEGEL_1000X1000_HALFST_KL-SO
SVH-TEGEL_1000X1000_HALFST-SO
SVH-TEGEL_100X300_HALFST_KL-SO
SVH-TEGEL_100X300_HALFST-SO
SVH-TEGEL_100X300_LINT_KL-SO
SVH-TEGEL_100X300_LINT-SO
SVH-TEGEL_2000X2000_BLOK_KL-SO
SVH-TEGEL_2000X2000_BLOK-SO
SVH-TEGEL_2000X2000_HALFST_KL-SO
SVH-TEGEL_2000X2000_HALFST-SO
SVH-TEGEL_2000X2000_LINT_KL-SO
SVH-TEGEL_2000X2000_LINT-SO
SVH-TEGEL_200X300_HALFST_KL-SO
SVH-TEGEL_200X300_HALFST-SO
SVH-TEGEL_200X300_LINT_KL-SO
SVH-TEGEL_200X300_LINT-SO
SVH-TEGEL_200X600_HALFST_KL-SO
SVH-TEGEL_200X600_HALFST-SO
SVH-TEGEL_200X600_LINT_KL-SO
SVH-TEGEL_200X600_LINT-SO
SVH-TEGEL_300X200_HALFST_KL-SO
SVH-TEGEL_300X200_HALFST-SO
SVH-TEGEL_300X200_LINT_KL-SO
SVH-TEGEL_300X200_LINT-SO
SVH-TEGEL_600X200_HALFST_KL-SO
SVH-TEGEL_600X200_HALFST-SO
SVH-TEGEL_600X200_LINT_KL-SO
SVH-TEGEL_600X200_LINT-SO
SVH-TEGEL_600X600_BLOK_KL-SO
SVH-TEGEL_600X600_BLOK-SO
SVH-TEGEL_600X600_HALFST_KL-SO
SVH-TEGEL_600X600_HALFST_STIP_KL-SO
SVH-TEGEL_600X600_HALFST-SO
SVH-TEGEL_600X600_LINT_KL-SO
SVH-TEGEL_600X600_LINT-SO
V-SVH-TEGEL_1000X1000_BLOK_KL-SO
V-SVH-TEGEL_1000X1000_BLOK-SO
V-SVH-TEGEL_1000X1000_HALFST_KL-SO
V-SVH-TEGEL_1000X1000_HALFST-SO
V-SVH-TEGEL_100X300_HALFST_KL-SO
V-SVH-TEGEL_100X300_HALFST-SO
V-SVH-TEGEL_100X300_LINT_KL-SO
V-SVH-TEGEL_100X300_LINT-SO
V-SVH-TEGEL_2000X2000_BLOK_KL-SO
V-SVH-TEGEL_2000X2000_BLOK-SO
V-SVH-TEGEL_2000X2000_HALFST_KL-SO
V-SVH-TEGEL_2000X2000_HALFST-SO
V-SVH-TEGEL_2000X2000_LINT_KL-SO
V-SVH-TEGEL_2000X2000_LINT-SO
V-SVH-TEGEL_200X300_HALFST_KL-SO
V-SVH-TEGEL_200X300_HALFST-SO
V-SVH-TEGEL_200X300_LINT_KL-SO
V-SVH-TEGEL_200X300_LINT-SO
V-SVH-TEGEL_200X600_HALFST_KL-SO
V-SVH-TEGEL_200X600_HALFST-SO
V-SVH-TEGEL_200X600_LINT_KL-SO
V-SVH-TEGEL_200X600_LINT-SO
V-SVH-TEGEL_300X200_HALFST_KL-SO
V-SVH-TEGEL_300X200_HALFST-SO
V-SVH-TEGEL_300X200_LINT_KL-SO
V-SVH-TEGEL_300X200_LINT-SO
V-SVH-TEGEL_600X200_HALFST_KL-SO
V-SVH-TEGEL_600X200_HALFST-SO
V-SVH-TEGEL_600X200_LINT_KL-SO
V-SVH-TEGEL_600X200_LINT-SO
V-SVH-TEGEL_600X600_BLOK_KL-SO
V-SVH-TEGEL_600X600_BLOK-SO
V-SVH-TEGEL_600X600_HALFST_KL-SO
V-SVH-TEGEL_600X600_HALFST_STIP_KL-SO
V-SVH-TEGEL_600X600_HALFST-SO
V-SVH-TEGEL_600X600_LINT_KL-SO
V-SVH-TEGEL_600X600_LINT-SO

We zijn er bijna:
De restanten van de dubbele naamgevingen zijn:

De symbolen voor 'elleboogverband' zijn identieke symbolen en is verschil van verband en legrichting dus niet aan de orde.
Te vervallen:
V-SVH-TEGEL_150X300_DIK_ELLEBOOG_KL-SO
V-SVH-TEGEL_150X300_DIK_ELLEBOOG-SO
SVH-TEGEL_150X300_DIK_ELLEBOOG_KL-SO
SVH-TEGEL_150X300_DIK_ELLEBOOG-SO
SVH-TEGEL_150X300_DUN_ELLEBOOG-SO
SVH-TEGEL_150X300_DUN_ELLEBOOG_KL-SO
V-SVH-TEGEL_150X300_DUN_ELLEBOOG-SO
V-SVH-TEGEL_150X300_DUN_ELLEBOOG_KL-SO
Dan blijft over:
Waarbij van de onderste series het veschil in het verband zichtbaar is.

Na alle acties is dit het voorstel voor de symbolen voor hoofdgroep VH.
https://github.com/nl-digigo/NLCS/blob/main/ontwikkeling/bijlagen_bij_issues/56/DEFINITIEFTOTAAL NIEUWE.dwg
waarin een behoorlijke opschoonactie is gedaan.

Niet te vergeten, de aanvullende symbolen waar de issue mee is begonnen:

Aanvullingen::
SVH-TEGEL_300X150_DIK_BLOK_01-SO
SVH-TEGEL_300X150_DIK_BLOK_KL_01-SO
SVH-TEGEL_300X150_DIK_BLOK_KL-SO
SVH-TEGEL_300X150_DIK_BLOK-SO
SVH-TEGEL_300X150_DUN_BLOK_01-SO
SVH-TEGEL_300X150_DUN_BLOK_KL_01-SO
SVH-TEGEL_300X150_DUN_BLOK_KL-SO
SVH-TEGEL_300X150_DUN_BLOK-SO
V-SVH-TEGEL_300X150_DIK_BLOK_01-SO
V-SVH-TEGEL_300X150_DIK_BLOK_KL_01-SO
V-SVH-TEGEL_300X150_DIK_BLOK_KL-SO
V-SVH-TEGEL_300X150_DIK_BLOK-SO
V-SVH-TEGEL_300X150_DUN_BLOK_01-SO
V-SVH-TEGEL_300X150_DUN_BLOK_KL_01-SO
V-SVH-TEGEL_300X150_DUN_BLOK_KL-SO
V-SVH-TEGEL_300X150_DUN_BLOK-SO

Het zou mooi zijn als er voor elk object 1 duidelijk symbool is en niet een grote én kleine variant. Bijv. bij grote tegelformaten is in het KL-symbool het tegelpatroon niet herkenbaar en het KL-symbool niet duidelijk.
Jouw voorbeeld hierboven: zou het 1:500 symbool juist niet kleiner dan het 1:200 symbool moeten zijn, of maximaal even groot als het 1:200 symbool? Waarom is het 1:500 symbool groter dan het 1:200 symbool?

Aanvullend: in de symbolen staan de maten in cm. Conform NLCS zijn materiaalmaten in mm. Dus of de symbolen aanpassen of een uitzondering opnemen in de FB.

Aanvullend: in de symbolen staan de maten in cm. Conform NLCS zijn materiaalmaten in mm. Dus of de symbolen aanpassen of een uitzondering opnemen in de FB.

Helemaal mee eens, deze opmerking heb ik ook al meerdere malen van mijn projectleiders gekregen.
Zou gewoon 300x300 moeten zijn bijvoorbeeld.
Persoonlijk vindt ik de standaard aanvullen 30x30 totaaal niet relevant.
Ik haal het dan meestal ook weg en verklaar het symbool in mijn legenda met de afmetingen.
Pas bij meerdere kleuren/afmetingen ga ik de attributes gebruiken voor verder specifieren.

Jouw voorbeeld hierboven: zou het 1:500 symbool juist niet kleiner dan het 1:200 symbool moeten zijn, of maximaal even groot als het 1:200 symbool? Waarom is het 1:500 symbool groter dan het 1:200 symbool?

ik gaf al aan dat dit even 1:1 is aangegeven...had even snel een plaatje in model gemaakt....maar dan maar even "officieel"
maar gaat er dus om dat vaak de "normale"verhardingssymbolen bij 1:500 te groot zijn om binnen een v(l)ak te plaatsen....waardoor we dus eigenlijk alleen maar de -KL varianten gebruiken.

Helemaal mee eens, deze opmerking heb ik ook al meerdere malen van mijn projectleiders gekregen.
Zou gewoon 300x300 moeten zijn bijvoorbeeld.
Persoonlijk vindt ik de standaard aanvullen 30x30 totaaal niet relevant.
Ik haal het dan meestal ook weg en verklaar het symbool in mijn legenda met de afmetingen.
Pas bij meerdere kleuren/afmetingen ga ik de attributes gebruiken voor verder specifieren.

klopt hier inderdaad ook...meestal niet in "tekening" en alleen in verklaring

Ik bedoelde of het niet zo zou moeten zijn:

Dus dat het symbool 1:500 2,5x kleiner wordt.

nee dat is niet hoe e.e.a. hoort te werken....het zijn namelijk annotatieve symbolen... dus symbool moet net zo groot blijven op elke schaal, anders wordt het dus, zoals je al ziet in jou voorbeeld, te klein en is e.e.a. niet meer te onderscheiden.

In de MODEL is het 1:500 symbool juist 2,5x groter dan het 1:200 symbool.
In de LAyout wordt de verschaling van de viewport gedaan, waardoor ze op papier weer even groot weergegeven worden.

Dat is een persoonlijke keuze maar is nooit NLCS-standaard geweest en hoort dat ook niet te zijn.

Dat is een persoonlijke keuze maar is nooit NLCS-standaard geweest en hoort dat ook niet te zijn.

Het beschreven gedrag is het Annotatieve gedrag van AutoCAD. oftewel -SO ;-)

oftewel -SO ;-)

Expliciet benoemd in de NLCS-EC: -SO staat niet gelijk aan annotatief.

zo wordt dit echter wel aangeboden door de leveranciers en over -SO hebben we al een "controversieel" issue lopen...dus laten we dat even daar houden...
mijn vraag is nu meer
blijven we dan voor 5.1 nu in ieder geval zowel de kl als de niet -kl symbolen aanbieden?
anders maak ik deze ook controversieel...tenzij er goede symbolen komen die zowel voor 1:200 als 1:500 gebruikt kunnen worden. en zoals aangegeven dan pleit ik juist voor de -kl versie. zoals aangegeven in mijn voorbeeld

#380

De 'grote' en 'kleine' symbolen mogen wat mij betreft gewoon blijven.
De weergave daarvan kan inderdaad wel wat beter. maar dat is weer een andere discussie. ;-)
In bovenstaande voorstel heb ik de bestaande bibliotheek even flink op de schop genomen, maar de huidige logica wel in stand gehouden.

authors: ElisabethKloren MvanderHulst NielsNederpel SanderNijhof

repo: bimloket/NLCS


text:
update wiki

ok, I give.
How am I to update items in the wiki?

(sorry for the late reply) You can update the items in the wiki by going to https://github.com/bio-linker/organization/wiki and click edit on page of choice. If this doesn't work, please re-open and contact me directly. Hope this helps.

authors: diatomsRcool jhpoelen

repo: bio-linker/organization


text:
invalid schema

I tried to leverage some automation on my openapi spec but they all failed because of errors in the schema:
Semantic error at components.schemas.BaselineCheck_'HasCase_PhysicalUnit
Component names can only contain the characters A-Z a-z 0-9 - . _
Semantic error at components.schemas.BaselineDescriptor_'CategoricalDescriptor
Component names can only contain the characters A-Z a-z 0-9 - . _

also I have names like "PlayerPoly_(PointG_Int)" .
I've tried to add some tests and a fix doing:
...
  , datatypeNameModifier = conformDatatypeNameModifier
...

-- | Adhere to spec https://www.rfc-editor.org/rfc/rfc3986#section-3.1
-- https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.3.md
conformDatatypeNameModifier :: String -> String
conformDatatypeNameModifier =
  foldl (\acc x -> acc ++ convertChar x) ""
  where
    convertChar = \case
      '(' -> "_parensL_"
      ')' -> "_parensR_"
--      '\'' -> "_squote_"
      other -> [other]

but seems like a better fix would be to do "percent-encoding" . I wonder if that would be allright and in which case how to do that. Looks like we could import a library like https://hackage.haskell.org/package/network-uri-2.6.4.2/docs/Network-URI.html#v:escapeURIString . Before putting up a PR, I wanted to ask if it's fine ?

https://github.com/biocad/openapi3/pull/74


text:
RFC: Add support for conventional commits and semantic release

https://www.conventionalcommits.org/en/v1.0.0/#summary
https://github.com/semantic-release/semantic-release

This issue was closed by stalebot. It has been reopened to give more time for community review.  See biocommons coding guidelines for stale issue and pull request policies.  This resurrection is expected to be a onos.environ["GITHUB_TOKEN"]e-time event.

@holtgrewe had sketched a release-please based implementation here

One wrinkle: in semantic-release, you designate breaking changes by including BREAKING CHANGE: in the commit body (whereas strictly speaking the conventional commits spec allows either this or a ! in the commit prefix to designate a breaking change). I kind of like this as a practice -- it forces the committer to spell out the breaking change in detail -- but we (Wagner lab) have just been doing the ! prefix, so it'd entail a slight change in workflow. More here

authors: jsstevenson reece


text:
fix #2109

Fixing, the upload now looks like this:

and when done it looks like:

Codecov Report

Merging #2191 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2191      +/-   ##
==========================================
- Coverage   92.06%   92.05%   -0.02%
==========================================
  Files         191      191
  Lines       19581    19581
==========================================
- Hits        18027    18025       -2
- Misses       1554     1556       +2

Impacted Files
Coverage Δ

...t/handlers/api_proxy/tests/test_sample_template.py
97.77% <0%> (-0.89%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: antgonza codecov-io

repo: biocore/qiita


text:
Check code complexity using flake8 and travis

flake8 has built in code complexity checks using the flag --max-complexity. Running with max-complexity 10, we get (as an example)
skbio/alignment/_alignment.py:847:1: C901 'Alignment.subalignment' is too complex (15)
skbio/alignment/_pairwise.py:918:1: C901 '_traceback' is too complex (14)
skbio/io/format/_base.py:139:1: C901 '_format_fasta_like_records' is too complex (12)
...

If we integrate this into the current flake8 checks in travis, we can also make sure overly-complex code is flagged on pull-request and doesn't propagate into the codebase.

:+1:

authors: jairideout squirrelo

repo: biocore/scikit-bio


text:
ENH: TreeNode.tip_tip_distances supports nodes without associated length

Contains the commits in #882 and updates based on code review there. Fixes #791.
@ebolyen can you please review?

Ready for merge when tests pass

authors: ebolyen jairideout


text:
Proposal for rows

We can change it here or in ontobio, but we only have 3 functions here and I don't see why this default value could not be infinite ? Furthermore, if we change it in ontobio, it would prevent any API call to actually change this value if needed

@lpalbou IMO, the default not being infinite is to prevent unnecessary calls hammering an existing Solr instance. Of late, we (Monarch and GO) have been noticing high amount of traffic hitting our instances with more than a handful being scripted requests with the goal of performing bulk retrieving operations.
If every call defaults to give all rows then the amount of documents sent back for each call will be large. I do see this as a side effect to this change.
So perhaps changing at the Ontobio would end up causing more trouble than its worth.
If we are changing just for one or two routes then that seems more justified.
But I will defer to @cmungall, @kltm and @kshefchek to chime in on this change.

going through all old PRs, what is the status of this?

authors: cmungall deepakunni3 lpalbou

repo: biolink/biolink-api


text:
About the pretraining resources

Hi, great work on your model published in Nature Methods.
However, maybe I missed something but I can't find details on training time and computational resources in the paper and supplementary materials. such details are essential for comparing with other models.
Could you please share the information?
Thank you!

Hi,
Thank you for your interest in our work! We trained our model on 64 A100 cards for about 2 weeks.

Thanks! I'll close this issue.

repo: biomap-research/scFoundation


text:
chore: update angular to v13. update nx to 13.2

What new features does this PR implement?
Please summarize the features that this PR implements. As relevant, please indicate the issues that the PR closes.

Adds ABC (closes #X)
Adds XYZ (closes #X)

What bugs does this PR fix?
Please summarize the bugs that this PR fixes. As relevant, please indicate the issues that the PR closes.

Fixes ABC (closes #X)
Fixes XYZ (closes #X)

Does this PR introduce any additional changes?
Please summarize any additional changes that this PR introduces.

Corrects typos in documentation
Changes theme of documentation

How have you tested this PR?
Please summarize the tests that you implemented to test this PR.

Added test for ABC
Added test for XYZ

Additional information
Please describe any information needed to review this PR.

blocked by https://github.com/angular/flex-layout/issues/1368

Blocked by #3706

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

repo: biosimulations/biosimulations


text:
fix: create project fails in combine-api

What bugs does this PR fix?
Fixes silent failure when creating new omex file.  The transaction failed when uploading to a temporary S3 bucket.  The cause was improper environment variable used for S3 credentials.

Fixes create project fails when writing to S3 (closes #4736)

How have you tested this PR?
Unit test CreateCombineArchiveTestCase.test_create_combine_archive_with_uploaded_model_file_and_save_to_s3_biomd0000000010() exercises this code path in combine-api.

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

authors: biosimulations-daemon jcschaff


text:
Geo-IP Tracker

Description
A python script that will be able to track location. city, time zone, continent and postal of a given IP Address
Technologies and Languages
Python

Great..Go ahead..Waiting for your PR

Hey @larymak   any update? Do let me know if you need any help

yes, @bislara I have created an update

@larymak I would like to work on it ,please assign me.

authors: AnuragDhavale bislara larymak

repo: bislara/code-n-stitch


text:
右键扩展过多，能否本插件所有的选项集中到一个复选框内？

右键扩展过多，导致电脑无法全部显示所有右键菜单
能否本插件所有的右键选项集中到一个一级右键菜单中内？

查看了一下源码，再看了一下knife1.8的功能，发现1.8存在将所有扩展缩为一个右键菜单的选项。
因此，本issue已解决。

查看了一下源码，再看了一下knife1.8的功能，发现1.8存在将所有扩展缩为一个右键菜单的选项。
因此，本issue已解决。


text:
build: Include autogen.sh in EXTRA_DIST

Adds autogen.sh to the distribution; corresponds to:
https://github.com/bitcoin-core/secp256k1/blob/0d9540b13ffcd7cd44cc361b8744b93d88aa76ba/Makefile.am#L175
Noticed when working with make dist in Bitcoin.
Got an error when entering src/univalue, something like:
make[6]: Leaving directory '/Users/Jon/bitcoin/src/secp256k1'
make[5]: Leaving directory '/Users/Jon/bitcoin/src/secp256k1'
 (cd univalue && make  top_distdir=../../bitcoin-0.19.99 distdir=../../bitcoin-0.19.99/src/univalue \
     am__remove_distdir=: am__skip_length_check=: am__skip_mode_fix=: distdir)
make[5]: Entering directory '/Users/Jon/bitcoin/src/univalue'
>>> No rule to make target `distdir`.

This fixed itself when autogen.sh was added. Can't replicate it now, unfortunately.

This shouldn't be an issue after https://github.com/bitcoin/bitcoin/pull/22646. Closing for now.

repo: bitcoin-core/univalue-subtree


text:
افزودن ویدیوهای جادی

سلام. جادی ویدیوهای خوبی در مورد بلاکچین و بیت‌کوین در این پلی لیست داره:
https://youtube.com/playlist?list=PL-tKrPVkKKE1gLxAL-56H-XR-fTapqofC
این ویدیوها بسیار معروف هستند.
دلیل خاصی داره که اضافه نشده‌اند؟
لطفاً بررسی بفرمایید و اگر لازم به کمک بود برای درجشون کمک کنم.

سلام
ممنون بابت معرفی این لیست
آنها را درنظر می گیریم

شما این ویدیوها رو شخصا دیده اید؟

سلام ممنون بابت معرفی این لیست
آنها را درنظر می گیریم
شما این ویدیوها رو شخصا دیده اید؟

من کامل ندیدم. ولی در جلسه اول در مورد رفرنس ویدیوها صحبت میشه. در واقع مبحث بر اساس اون کتاب رفرنس پیش میره. خود جادی هم که شناخته شده هست و در سایر ویدیوهای تخصصی که ازش دیدم هیچوقت مبحث پرت نداشته.

سلام. من ویدیو‌ها رو دیدم. به نظرم توضیحات ساده و قابل فهمی داره و اگر کسی بخواد دنبال کنه ارزشمنده

شما این ویدیوها رو شخصا دیده اید؟

من این ویدئوها رو دیده‌م. بسیار مفیدن، به‌خصوص اگه تازه‌وارد باشید. این پلی‌لیست رو به افرادی که تازه با بیت‌کوین آشنا می‌شن پیشنهاد داده‌م، ازجمله خانواده، و برای اون هم مفید بوده. پیشنهاد می‌کنم به سایت افزوده بشن.

 این ایشو رو به یکی از دوستان تحریریه سپردیم و قراره تصمیم گیری بشه درباره ش. تشکر از دوستانی که توی این ایشو نظر دادن.

authors: LordArma amirbagh75 bitcoind-me mcsaeid

repo: bitcoind-me/bitcoind-me


text:
Bug when using browserify

I just imported the lib and compile with browserify, but:

Any idea?

Need steps to reproduce.
Versions of things (like browserify), commands, etc etc.
Whatever you did, the bundler did not recognize the browser files and tried to bundle the NodeJS files instead.

node version, npm version, browserify version, what commands / configs did you use for the bundling.
etc etc etc

Also, this issue is with tiny-secp256k1, not ecpair. So I'm closing it here.
Please open an issue in the appropriate repo with more info. Thanks.
Also search for existing issues (this sounds familiar)

node: v16.18.1
npm: 7.12.0
browserify: v17.0.0
I just run browserify file.js -o bundle.js with it:
const ecc = require('tiny-secp256k1')

@junderw sorry, you right!

authors: Anderson-Juhasc junderw

repo: bitcoinjs/ecpair


text:
Newsletters: add 218 (2022-09-21)

[ ] Lede, releases/RCs, topic links @harding
[x] Client/services section @bitschmidty
[x] Core Lightning 5581 @Xekyo

Made edits (thanks @glozow @Xekyo @LarryRuane @bitschmidty), added lede, removed releases/RC section (I don't see anything), added topic links, and reviewed @bitschmidty and @Xekyo contributions (thanks!).  Thanks everyone!

Added fedimint signet/faucet news to the client service section

Looking good! Thanks @harding @Xekyo @LarryRuane and @glozow for contributing this week! 🚀

authors: bitschmidty harding


text:
LogIn Issue from China Mainland! Need a network setting for Socks5 proxy!

An error occurred
WORKER:ERROR [2023-04-27T05:23:03.793Z]     Error: ETIMEDOUT
  - METHOD_NAME: signUp
  - STATUS_CODE: 500
  - STATUS_MESSAGE: Internal Server Error
  - STACK_TRACE RequestError: Error: ETIMEDOUT
    at new RequestError (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:198:22)
    at Timeout._onTimeout (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:764:12)

Debug info

Version
4.5.1

Commit Hash
721acbda1a5e7b4930571918aeecdff2523ba15d

Commit Date
2023-04-26T10:39:39Z

Electron
13.6.9

Chrome
91.0.4472.164

Node.js
14.16.0

V8
9.1.269.40-electron.0

OS version
Darwin Kernel Version 18.7.0: Tue Jun 22 19:37:08 PDT 2021; root:xnu-4903.278.70~1/RELEASE_X86_64

OS release
Darwin x64 18.7.0

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz x 4

RAM
8GB (0.05GB free)

App RAM limit
2072Mb (9.65MB used)

Main log
    at Timeout._onTimeout (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/
[2023-04-27 12:28:10.863] [error] WORKER:ERROR [2023-04-27T04:28:10.862Z]     Error: ETIMEDOUT
  - METHOD_NAME: loginToBFX
  - STATUS_CODE: 500
  - STATUS_MESSAGE: Internal Server Error
  - STACK_TRACE RequestError: Error: ETIMEDOUT
    at new RequestError (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:198:22)
    at Timeout._onTimeout (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:764:12)
[2023-04-27 13:23:03.811] [error] WORKER:ERROR [2023-04-27T05:23:03.793Z]     Error: ETIMEDOUT
  - METHOD_NAME: signUp
  - STATUS_CODE: 500
  - STATUS_MESSAGE: Internal Server Error
  - STACK_TRACE RequestError: Error: ETIMEDOUT
    at new RequestError (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:198:22)
    at Timeout._onTimeout (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:764:12)

Worker errors
WORKER:ERRO
  - METHOD_NAME: loginToBFX
  - STATUS_CODE: 500
  - STATUS_MESSAGE: Internal Server Error
  - STACK_TRACE RequestError: Error: ETIMEDOUT
    at new RequestError (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:198:22)
    at Request.emit (events.js:315:20)
    at Timeout._onTimeout (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:764:12)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)
WORKER:ERROR [2023-04-27T05:23:03.793Z]     Error: ETIMEDOUT
  - METHOD_NAME: signUp
  - STATUS_CODE: 500
  - STATUS_MESSAGE: Internal Server Error
  - STACK_TRACE RequestError: Error: ETIMEDOUT
    at new RequestError (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/errors.js:14:15)
    at Request.plumbing.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:87:29)
    at Request.RP$callback [as _callback] (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/request-promise-core/lib/plumbing.js:46:31)
    at self.callback (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:198:22)
    at Request.emit (events.js:315:20)
    at Timeout._onTimeout (/Applications/Bitfinex Report.app/Contents/Resources/app/bfx-reports-framework/node_modules/bfx-api-node-rest/node_modules/request/request.js:764:12)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

Worker exceptions
Empty

The issue was opened from the electron app

Hi @Ken-n do you experience this only when using the report tool or also when accessing bitfinex.com ?

Hi @Ken-n do you experience this only when using the report tool or also when accessing bitfinex.com ?

Only when using the report tool, because I access bitfinex.com on my browser which allows me to set a proxy.

Hi @Ken-n do you experience this only when using the report tool or also when accessing bitfinex.com ?

Only when using the report tool, because I access bitfinex.com on my browser which allows me to set a proxy.

@Ken-n thanks for reporting, checking!

Hi @Ken-n has this been solved?

You can use electron proxy arguments in the command line:
./BitfinexReport-4.16.0-x64-linux.AppImage --proxy-server=IP:PORT --proxy-bypass-list=<-loopback>

authors: Ken-n ezewer krm35

repo: bitfinexcom/bfx-report-electron


text:
DCA Actions Missing

DCA functions needed for CL and QL models. This issue may be related to the model detection problem.
DCA Level Adjust / DCA On / DCA Off

I think it would also be great if there was a DCA assign/unassign as well. I'd love to select a channel and assign or unassign it from the stream deck quickly.

The DCA functions are all there now, with feedback. The new module has been submitted, so hopefully soon it will replace the current module. Please test it when it does and let me know if it works for you. I was only able to test functionality on a CL console, don't have a TF to test with.

@MeestorX thank you! Will test out the new module once it pushes out in the next build. I've only got a QL and CL to test with, though.

authors: MeestorX ethan-tripp lekogm

repo: bitfocus/companion-module-yamaha-scp


text:
ShowMore and dismiss buttons problem in BitMessageBar

In BitMessageBar component when Truncated and OnDismiss properties both got value then the related buttons get so close to each other and makes mobile user to click on show more button

Current State
Expected State

@maryamhdr
plz investigate this issue 😊

@maryamhdr plz investigate this issue 😊

This issue is valid 👍🏻

authors: RezaKargar maryamhdr msynk

repo: bitfoundation/bitframework


text:
use nuget package instead of direct project reference (#2016)

This closes #2016

PING! @msynk


text:
Pre-fetched data sent to the CSE

If the user has given permission to collect data for the session and if the user is on the hodler/diamond hands tier, and if they request for a human chat support... at that time, the human customer support should received the following data:

Tier Info
Phone and OS
App version history
Screen context (where the user is coming from)
Tor and network (WiFi/ Mobile) status
Sentry items - error codes

Verified on Zendesk.

repo: bithyve/bitcoin-keeper


text:
Reshare of Keeper Device.

-Reshare of Keeper Device is not working properly.
-Can’t become a Keeper when you have restored.

I was able to become a keeper post-restoration, wasn't able to test the Reshare of keeper due to lack of devices (@cakesoft-swati can you test and confirm this once?)

-Not able to test this scenario.
-Healch check status is not accurate.

authors: Parsh cakesoft-swati

repo: bithyve/hexa


text:
What is changing in v2?

I see that there is v2.0.0-alpha.1 tag.
Whats changing?

Check https://github.com/bitinn/node-fetch/blob/master/CHANGELOG.md#2x-release (especially the "major" points). The upgrade guide is helpful too, as it outlines the most important changes.

Thank you! Sorry, I have missed it.

authors: TimothyGu gajus

repo: bitinn/node-fetch


text:
Proper "Bloom filter" capitalization

It's a really minor issue, but the correct name is "Bloom filter", not "bloom filter", since Bloom is the inventor's last name.

Fair point. Done. https://github.com/bitly/dablooms/commit/c38b226779678dc0d7e93f0afb41bb40675d344a

authors: alexeyr ploxiln

repo: bitly/dablooms


text:
Update to 0.13.0 Bitcoin Core

https://github.com/bitcoin/bitcoin/releases/tag/v0.13.0

I have squashed the commits modified on the 0.12.1 branch here at https://github.com/braydonf/bitcoin/commits/0.12.1-bitcore-squashed for applying to the 0.13 branch.

Changes rebased onto 0.13.0 at https://github.com/bitpay/bitcoin/pull/35

repo: bitpay/bitcoin


text:
add getTx

add getTx, tests and doc.

Coverage increased (+0.05%) to 94.38% when pulling 8ac6dea5a68d04508d94a8583b21ab45760a5b12 on matiu:feat/getTx into c53726177681325be940521b1420a9bdc93a356f on bitpay:master.

authors: coveralls matiu

repo: bitpay/bitcore-wallet-client


text:
🛑 Plex is down

In ef04c85, Plex (https://plex.bitpushr.net/web/index.html#!/) was down:

HTTP code: 530
Response time: 123 ms

Resolved: Plex is back up in 1460102 after 10 minutes.

repo: bitpushr/upptime


text:
Links to gifs do not unfold

Hi guys,
Thanks for this cool step! :D
We were using it in its 2.1.0 version and were able to send gifs on succesful/failed builds.
Unfortunately, when updating to 2.3.0, the gifs do not unfold anymore :(
See below the difference: the two first messages were sent with 2.3.0 version of the step, and the two last with version 2.1.0. A green line has also been added in the body of the message (probably the cause of this :))

Yeah, I believe this is related to the change from raw text messages to Slack's attachment API in 2.2.0 and 2.3.0 - https://github.com/bitrise-io/steps-slack-message/releases - 2.2.0 had an option to use the raw text option, which was removed in 2.3.0
Do you know if link expansion can be enabled in Slack's attachment API? Or is it a text only option?

Looking into Slack's documentation on attachments, could it not be achieved by adding the image_url parameter to be editable?
Example:  example

That very well might work @simonmartyr - if you have the time feel free to test it & send a PR!

Thanks @simonmartyr for the PR!
Released in v2.4.0 (https://github.com/bitrise-io/steps-slack-message/releases/tag/2.4.0) - should be available on bitrise.io too, once the publish is accepted (~10-20 mins)!

authors: Almouro simonmartyr viktorbenei

repo: bitrise-io/steps-slack-message


text:
🛑 Luogu CDN is down

In 67c5422, Luogu CDN (https://cdn.luogu.com.cn/fe/loader.js?ver=20230228-2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Luogu CDN is back up in 6282713.

repo: bitsstdcheee/luogu-status


text:
🛑 Luogu CDN is down

In dc3d5c0, Luogu CDN (https://cdn.luogu.com.cn/fe/loader.js?ver=20230228-2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Luogu CDN is back up in 9142814.


text:
Fix typos

Summary of changes
I'll review the commits, so I mostly want to understand the "why" rather than the "what"
Checklist

[ ] New functions have typespecs, changed functions were updated
[ ] Same for documentation, including moduledocs
[ ] Tests were added or updated to cover changes
[ ] Commits were squashed into a single coherent commit
[ ] Notes added to CHANGELOG file which describe changes at a high-level

@bitwalker Any updates on this?

Thanks!

:+1: :tada:

authors: bitwalker kianmeng

repo: bitwalker/timex


text:
JSONAPI compliance fixes

Asana Card

added few fixes in accordance with JSONAPI specification.

Engine will merge

authors: matthewford myxrome

repo: bitzesty/trade-tariff-backend


text:
Staging release

update feedback page

 [TARIFF17] Update the feedback page to include the HMRC complaints page

repo: bitzesty/trade-tariff-frontend


text:
Remote host

Hi, I want not just to have the localhost for the sending machine. The background is I want to connect the T265 to a laptop and then sending over local network to the receiving machine via WiFi so I do not have a cables between.
Do you have any clue how to do it?

Yes, you can add the IP(s) it should be sending to in the commandline.
"py ./tracker.py 192.168.1.x"


text:
vrapi: Expose pinch strength

Currently it is not possible to get the Oculus provided pinch strength, which is surprising.  It isn't clear if this should be mapped to trigger (easier porting, slightly less correct, probably preferred) or if a new pinch axis should be added.
Related, there are a few flags that are available.  There are 4 booleans indicating whether each finger is pinching (seems less useful than axis), and whether the hand is performing the funky home/menu gestures (perhaps certain inputs should be blocked while this is happening, or they get mapped to the menu button).

Does pinch automatically get mapped to trigger or something?  Is it just a button or an axis?  Is it the same as the pinch strength?

Added in oculus-pinch-pointer branch, using trigger axis

Merged to dev

repo: bjornbytes/lovr


text:
Manufacturers and device types

The manufacturers should use official taxonomy as per https://github.com/netbox-community/devicetype-library
Thus I do understand that different Tools and APIs might give different representations, maybe having a mathing table or simmilar?
i.e.
Cisco Systems Inc. -> Cisco
Fortinet. Inc. -> Fortinet
Fortinet Inc. -> Fortinet
HP -> HPE
HP Enterprise -> HPE
HP Inc. -> HPE
and so on

Yes this is currently missing, but it is a main goal to include device type library in this microservice, because it will be also useful to fetch all data from library for physical devices (interfaces etc.). Will soon start working on it.
The idea is to dynamically generate static code (golang map) with go generate. So on every build there will be map of all data created from devicetype-library.

sound like a good plan.
P.S. I soon will create another issue related to deviced and virtual appliances that would impact plan you described a bit.

solution also should not create device templates on it's own if there is an existing template in the system or in the device-type library. Often there is more of valuable information such as weight, size, etc. that is essential for other functions like DCIM.

I will come with a plan in a few days and we can talk more about implementation...

Have automatically generated (data.go)[https://raw.githubusercontent.com/bl4ko/netbox-ssot/142-manufacturers-and-device-types/internal/devices/data.go] from netbox's device library, just have to figure out how to include this in external sourcese.

Hello I have written generator which creates static device data map from devicetype-library. This data is then used to get correct slug for device types. Also other physical aspects for each device can be added easily in the future.
For manufacturer map, as you suggested I have created special serialize function.

:tada: This issue has been resolved in version 1.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
fix LCE fill when block size == fill width

This change fixes a bug in the LCE when cache block size is equal to cache fill width size. In this case, there is only a single fill packet so the first count input to the stream counter used to generate the proper fill index should be zero.

We should add configs with single cycle fill for both unicore and multicore so we can add it to weird CI

Merging to me_dev_hotfixes.

authors: dpetrisko muwyse

repo: black-parrot/black-parrot


text:
localhost:9900 unreliable

Ripple sometimes doesn't like loading from localhost:9900. Sometimes it works sometimes it fails. I cannot figure out how to reliably load my app. Sometimes I just get a white screen when I use localhost:9900. If I use http://blackberry.github.com/WebWorks-Samples/kitchenSink it works 100% of the time. If I try http://localhost:9900/HelloWorld/index.html it  works sometimes. If I type the url and then restart Ripple sometimes it works. Once 9900 URLs are working they keep working for the current session, but it seems like you can easily get into a state where nothing happens. Yet real URLs work 100% of the time. Firewalls are off etc...

I am having exactly the same issue

Could be an issue with node.js not being able to grab port 9900?
cc: @kwhatmough

@npross @areel Thanks for reporting! What operating system are you using? You indicated that firewall protection is off, so then I presume that you did not receive any pop-ups asking whether to unblock or continue blocking...
Ripple installs and uses node.js to help implement this feature. If possible, try to check for the node.js process running on your system. For example, check if node is running. Also check whether more than one node process is running. This should help diagnose the cause of the issue.

authors: areel kwallis kwhatmough npross

repo: blackberry/Ripple-Framework


text:
Fixed problem with JS player URL

The JS player URL could not be found anymore, possibly because of a change on Youtubes side.
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Today, many youtube videos could not be resolved anymore, because the JS player url changed its location:
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', '--no-warnings', '--dump-json', '--id', '--', 'WXzFCS72QIA']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dlc version 2020.10.25
[debug] Git HEAD: 6f8557ec4
[debug] Python version 3.8.5 (CPython) - Linux-5.4.67-1-MANJARO-x86_64-with-glibc2.2.5
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1, rtmpdump 2.4
[debug] Proxy map: {}
ERROR: Unable to extract JS player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dlc with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/home/peet/GitRepos/yt-dlc/youtube_dlc/YoutubeDL.py", line 830, in extract_info
    ie_result = ie.extract(url)
  File "/home/peet/GitRepos/yt-dlc/youtube_dlc/extractor/common.py", line 532, in extract
    ie_result = self._real_extract(url)
  File "/home/peet/GitRepos/yt-dlc/youtube_dlc/extractor/youtube.py", line 2065, in _real_extract
    jsplayer_url_json = self._search_regex(
  File "/home/peet/GitRepos/yt-dlc/youtube_dlc/extractor/common.py", line 1010, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dlc.utils.RegexNotFoundError: Unable to extract JS player URL; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dlc with the --verbose flag and include its complete output.

The fix was quite straightforward, I expanded the regex to recognize the new "jsUrl" config value. Both the old and the new content can be parsed now.
New location:
yt.setConfig({
	'WEB_PLAYER_CONTEXT_CONFIGS': {
		"WEB_PLAYER_CONTEXT_CONFIG_ID_EMBEDDED_PLAYER": {
			"rootElementId": "movie_player",
			"jsUrl": "/s/player/9b65e980/player_ias.vflset/en_US/base.js",
			"cssUrl": "/s/player/9b65e980/www-player-webp.css",
			"contextId": "WEB_PLAYER_CONTEXT_CONFIG_ID_EMBEDDED_PLAYER",

Previously, it was found here:
yt.setConfig({
	"VIDEO_ID": "WXzFCS72QIA",
	"INNERTUBE_API_KEY": "AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8",
	"XHR_APIARY_HOST": "youtubei.youtube.com",
	"XSRF_FIELD_NAME": "session_token",
	"INNERTUBE_CONTEXT_CLIENT_NAME": 56,
	"POST_MESSAGE_ORIGIN": "*",
	"GAPI_HINT_PARAMS": "m;\/_\/scs\/abc-static\/_\/js\/k=gapi.gapi.en.9Ky5Gf3gP0o.O\/d=1\/ct=zgms\/rs=AHpOoo9ntgUgaVmSKxb6oXsk111880adyg\/m=__features__",
	"GAPI_HOST": "https:\/\/apis.google.com",
	"DELEGATED_SESSION_ID": null,
	"PLAYER_CONFIG": {
                "args": <removed>
		"attrs": {"height": "100%", "width": "100%", "id": "video-player"},
		"assets": {
			"player_canary_state": "none",
			"js": "\/s\/player\/9b65e980\/player_ias.vflset\/en_US\/base.js",
			"css": "\/s\/player\/9b65e980\/www-player-webp.css"
		}
	},

Will check it tomorrow morning when I have internet again.

Tried this with previously broken video, seems fine for me.

I can also confirm that this commit fixes the issue that I've been having before.

license: Unlicense


text:
Failing to sample from Dirichlet Process Mixture Model using SGLD

Bug Description
I'm trying to reproduce the example from tensorflow-probability titled Fitting Dirichlet Process Mixture Model Using Preconditioned Stochastic Gradient Langevin Dynamics by using blackjax api. I've used the SGLD class. I tried to follow the example notebook that shows how to use SGMCMC in blackjax, but I can't seem to reproduce the results in the tensorflow example.
Steps/Code to Reproduce
I've implemented the blackjax version of the example in a Google Colab notebook located here
Expected Results
Samples from the posterior where there are three clusters
Actual Results
I'm getting nan values for the variables I'm trying to sample.
Versions
BlackJAX 0.8.2
Additional comment
I suspect there are two causes of the issue:
1. My definition of the log probability function
2. the usage of the step size scheduling function

Thank you for opening an issue. To help me debug, could you do the following:
1 - Look at the output of logprior and loglikelihood with test values for the parameters;
2 - Do the the same for the gradient estimator.

The step size is probably too small. Moving this to discussions as it does not seem to be a bug. Have you tried the parameters given in the TFP article?
# Learning rates and decay
starter_learning_rate = 1e-6
end_learning_rate = 1e-10
decay_steps = 1e4

# Number of training steps
training_steps = 10000

# Mini-batch size
batch_size = 20

# Sample size for parameter posteriors
sample_size = 100

authors: Habush rlouf

repo: blackjax-devs/blackjax


text:
Fix the Introduction Example

Fixed small typo in Introduction Example raising error.
Thank you for opening a PR!
A few important guidelines and requirements before we can merge your PR:

[ ] If I add a new sampler, there is an issue discussing it already;
[x] We should be able to understand what the PR does from its title only;
[ ] There is a high-level description of the changes;
[ ] There are links to all the relevant issues, discussions and PRs;
[x] The branch is rebased on the latest main commit;
[x] Commit messages follow these guidelines;
[ ] The code respects the current naming conventions;
[ ] Docstrings follow the numpy style guide
[ ] pre-commit is installed and configured on your machine, and you ran it before opening the PR;
[ ] There are tests covering the changes;
[x] The doc is up-to-date;
[ ] If I add a new sampler* I added/updated related examples

Consider opening a Draft PR if your work is still in progress but you would like some feedback from other contributors.

Thank you!


text:
Bug report: in Calendar view the week starting with Sunday

What happened?
The Dataview plugin don't use the ipadOS Settings > General > Language & Region settings to get the day when a week start.

I have to install the Calendar plugin and set "Start week on:" to Monday to get the right day start of the week.
DQL
CALENDAR sdate
FROM #event

JS
No response
Dataview Version
0.5.55
Obsidian Version
1.4.4 (99)
Device
iPad Pro 12.9 (5th gen)
OS
ipadOS 16.4.1a

I find similar bug on dateformat(file.day,"yyyy-'W'WW") that start the week from monday instead of sunday in my computer setup.

repo: blacksmithgu/obsidian-dataview


text:
Find all paths between 2 nodes?

Is your feature request related to a problem? Please describe.
I wonder if there is a way to display all paths between 2 given nodes? I have tried plugins like Journey but it only gives the shortest path using the Dijkstra algorithm and it does not support code fences.
Describe the solution you'd like
I think it would be great if dataview support query like this:
link "muscles" to "bones"
from "anatomy"
where link.hop < 5

and the output could be a nested list like (it would be even better if the result could be displayed in mermaid or some other graph view):

muscles

biceps

humerus

bones

scapula

bones

...

Do you want all shortest paths, all paths of length <= N? There are exponentially many paths between any two nodes in a graph, which would lag out quickly.

I think the result should be all simple paths between 2 arbitrary nodes. I originally thought that this feature could be easily implemented with a simple DFS and cut out all branches that exceed a given max depth and didn't think much about the time complexity...
The original motivation for this feature is that as a medical student, I'm struggling with connecting different systems (e.g., cardiovascular system, immune system...) together. It would be great if dataview could help reveal the hidden connections between nodes. Apparently, neither I nor the computer is good at connecting things QAQ...
I will close this issue since it is not feasible due to the high order of time/space complexity. Thank you for your reply.
PS: dataview is a great plugin!!! :)

I think the result should be all simple paths between 2 arbitrary nodes. I originally thought that this feature could be easily implemented with a simple DFS and cut out all branches that exceed a given max depth and didn't think much about the time complexity...
The original motivation for this feature is that as a medical student, I'm struggling with connecting different systems (e.g., cardiovascular system, immune system...) together. It would be great if dataview could help reveal the hidden connections between nodes. Apparently, neither I nor the computer is good at connecting things QAQ...
I will close this issue since it is not feasible due to the high order of time/space complexity. Thank you for your reply.
PS: dataview is a great plugin!!! :)

One option would be to compute the shortest path, and then compute all other paths that are at most N (say 1 - 3) longer than the shortest path. This is generally computationally feasible (if a little slow).
I think the coolest thing that could be done here would be to implement a graph viewing extension to Dataview which embeds a graph view that you can filter on. I wonder how feasible that is.

I think dataview is quite similar to SQL. After all, it's like writing SQL to me so far. However, the reason that I choose obsidian (or other software that has 2-way links) over Excel is that it takes the whole vault as a graph instead of a table. Unfortunately, the filters function in the graph view is not very handy, which makes the global graph view almost useless as the size of the vault quickly grows (I created nearly 3.5k nodes last semester and my vault will continue to expand at this speed in the following 2-3 years QAQ). I think it would be really useful if dataview could include some NoSQL/graph DB features, and what you have commented sounds truly promising. I'm looking forward to that :)

authors: blacksmithgu tctco


text:
Custom Date field

Hi, first of all, thanks a ton for this amazing plugin!! I don't think I'd have moved from Notion without it - not to mention it's so much more flexible.
So, there's this little thing that's bothering me: when rendering a table that contains a "date" field, the values render in a weird format that's very hard to read quickly, at least for me:

I'd prefer it if we could customize the date rendering format, I believe this shouldn't be too complicated to implement^^
Thanks again!!

Oh, that does look bad. This is probably a localization thing - the date rendering naively assumes an English-looking localization even if the underlying language is different. I will see if I can make it more customizable.

Possibly related → https://github.com/blacksmithgu/obsidian-dataview/issues/120

Custom dataview date formats have been added for 0.4.3.

authors: Lulullia Moonbase59 blacksmithgu


text:
🛑 Discord Nurive Bot is down

In c4232fa, Discord Nurive Bot (https://discord-bot-nurive.blackveriun.repl.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Discord Nurive Bot is back up in 021e1cd.

repo: blackveriun/status


text:
Limit simultaneous requests

Is there a way to limit simultaneous requests?
I've tried to set this but doesn't seem to have any effect:
import request from 'popsicle';
import auth from 'popsicle-basic-auth';
import http from 'http';
http.globalAgent.maxSockets = 10;

Any suggestion ? :smile:
Thanks!

Not built in, but we could publish a plugin. The relevant logic is pretty much: https://github.com/blakeembrey/popsicle-limit/blob/master/popsicle-limit.js#L9-L13. Just make a before wrapper that limits the number of concurrent requests running.

I've temporarily solved using https://github.com/ForbesLindesay/throat but in 2 weeks when I'm back from hols I'll see if I can build a plugin :+1:

I've added throat to the README: https://github.com/blakeembrey/popsicle#helpful-utilities. It's a great solution and easily re-usable in other places.

repo: blakeembrey/popsicle


text:
Add child_pages to the glitter nav toolkit

This is great for making ad-hoc trees / list pages

This should be a method on Pages instead of a template tag - the tag was just a workaround.

Let's do improved navigation as part of the next set of updates - the template tag isn't the solution.

authors: hawkz tomkins

repo: blancltd/django-glitter


text:
Supply recipe width for shaped ore crafting.

This should fix #225.

Thanks


text:
add_node_custom / add_edge_custom doesn't work since bind is pub(crate)

I have some code that uses add_node_custom / add_edge_custom.
While updating egui_graphs, I had to comment .bind b/c it's not public anymore.
Now that it compiles, I get a crash on self.id.unwrap() (particularly in Node::id).
Looking at default_node_transform and the one for edges, it still calls .bind.
So it seems like the intent is still for the transform function to call .bind, but that's no longer possible with it being pub(crate).
This doesn't seem like something I can fix from my end, and the g.add_node/edge function families don't seem to help with custom transforms.

Hi! Sorry for the long answer. This is totally a bug. I will address it soon in the upcoming Layout feature and support implicit binding or change the mechanic completely.

no worries. As a workaround I forked master and removed the (crate) in pub(crate) fn bind.

Fixed in separate PR

Fix is in master now.


text:
Feature Request - Repost button needs some Razzle Dazzle

Love the animation put on the "like" / "heart" button. Would like to see that on the repost button as well 🙏

The like animation is from Mastodon and I'm neither an icon designer or animator but I'll see what I can do!

Finally made it a thing with v1.3.0, closing it now

repo: blobcatz/pebble-mastodon-theme


text:
Feature: Add vue package

Description
Continuation of https://github.com/blocknative/web3-onboard/pull/911
Checklist

[x] The version field in package.json is incremented following semantic versioning
[x] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[ ] This PR passes the Circle CI checks

@wonderbeel looks good!

authors: taylorjdawson wonderbeel