[Core Rulebook] Loading Issue

Issues loading into the game. The homepage would load, but the chat window, assorted buttons, and commands do not appear or function.
Reloaded in safe mode, and the issue corrected itself.
The issue resurfaces whenever I install the Core Rulebook or any other official WFRP4e Book Mod.
I have uploaded all my regular mods, and they are working without issues, but I have avoided the Book Mods.
Fortunately, I have imported most of the journals, items, macros, and rollable tables.
Hopefully, you can resolve this issue soon. I've noticed it happening for around a week or so, and it would sometimes not occur, but today, I have had zero luck until I reset the mods.
Here is a screenshot of the error. I also have long load times, and that issue persists even after I reset the Mods, so I assume it's due to all my Imported content.
https://cdn.discordapp.com/attachments/1236904878802993162/1294399974037262462/Forge_Issue.jpg?ex=670adf6a&is=67098dea&hm=dcf4c9190bba113307fee34650871ab1112269715c03d9c9e858d46d553f4174&From: jorlackfoundry: 12.331wfrp4e: 8.1.3Active Modules: JB2A_DnD5e, Rideable, _chatcommands, autoanimations, betterroofs, breaktime, chat-commander-wfrp4e, combat-tracker-dock, custom-fonts, dice-calculator, dice-so-nice, dice-so-nice-more-sfx-triggers, easy-target, elevationruler, entice-with-dice-so-nice, forien-quest-log, foundryvtt-simple-calendar, fuzzy-foundry, gm-screen, healthEstimate, hover-distance, illandril-hotbar-uses, illandril-tidy-module-settings, illandril-token-hud-scale, illandril-token-tooltips, image-previewer, lib-wrapper, lordudice, monks-combat-details, monks-combat-marker, monks-scene-navigation, monks-sound-enhancements, monks-tokenbar, moulinette-core, moulinette-gameicons, moulinette-imagesearch, moulinette-scenes, moulinette-sounds, moulinette-tiles, pings, popout, popout-resizer, quick-insert, rich-info-tooltips, ripper-premium-dice, ripper-premium-dice-ea, routinglib, sequencer, settings-extender, smalltime, smarttarget, socketlib, talisdice, theripper-premium-hub, token-action-hud-core, token-action-hud-wfrp4e, warhammer-lib, wfrp4e-gm-toolkit, wfrp4e-night-vision, wfrp4e-random-treasure, wikirole_dice, forge-vtt

likely forge issue


Add Flickr API service

You need to rebase with upstream to have the travis tests pass.

In package.json you have flickrapi, are you still using this?

Travis CI is failing because it cannot load config.js. We will need to resolve this tomorrow morning. With build variables and default values.


FR: Additional Highlighting for $INCLUDE, $MetaCommands, and OPTION

I would love it if there was additional highlighting for:
'$INCLUDE:
'$* Meta-commands ($IF, $LET, $ENDIF, etc.)
OPTION

Option is already 'blue'  do you want it include in the metacommands scope?

Hi @LordDurus been a while :)
Is OPTION a meta command? I thought they all started with $whatever ? hrmm.
If it's a meta command I guess make it part of that group?
🙏🏻

I didn't change $Include, that is a bigger ball of wax since it will have go to definition side effects.
If include is a must add an item just for it.
I don't know if "Option Explicit" is technically a meta command but I do like it having colored as one.  So I included it :)
I did add a scope metacommand.QB64 and it includes
REM $DYNAMIC
' $DYNAMIC
REM $STATIC
' $STATIC
$ASSERTS
$CHECKING
$COLOR
$CONSOLE
$DEBUG
$ERROR
$EXEICON
$LET
$IF
$ELSEIF
$END IF
$SCREENHIDE
$SCREENSHOW
$VIRTUALKEYBOARD
$VERSIONINFO:Comments
$VERSIONINFO:CompanyName
$VERSIONINFO:FileDescription
$VERSIONINFO:FileVersion
$VERSIONINFO:InternalName
$VERSIONINFO:LegalCopyright
$VERSIONINFO:LegalTrademarks
$VERSIONINFO:OriginalFilename
$VERSIONINFO:ProductName
$VERSIONINFO:ProductVersion
$VERSIONINFO:Web
Option Explicit
This is in dev v0.9.1


BUG Restrict pandas version by Python minor version

Pandas dropped Python 3.4 support with v0.21, and our Python 3.4 tests have recently begun failing when they attempt to install the newest version. In the project requirements, make sure that we're requiring versions of pandas which are compatible with the user's Python version.

@keithing , this is another version of what you reviewed at https://github.com/civisanalytics/civis-python/pull/249 .


[Maybe] Use Tailwindcss CLI (instead of Webpack) to build styles

How?
This would look something like:

Adding something similar to the build:styles npm script to package.json in this PR
Adding a npm run <our script name(s)> command to our Dockerfile (I think)
Removing the tailwind style import from our javascript (currently in index.js)

Part of this task is determining if we want to do this. See the Why and Why not below.
Why?
There are a few benefits of doing this:

No need to maintain precarious Webpack.scala + webpack.sbt code that may need work to be maintained/updated in the future
Webpack seems to be pretty slow - this would eliminate the step of installing and building Webpack
It's pretty awkward that the way we currently (as of #214) include Tailwindcss styles is by importing it into a javascript file that is otherwise empty. As far as we can tell, the generated javascript file pretty much just defines a string of all the styles and appends it in a <style> tag. Would be nicer if we could skip the JS step and just include generated CSS instead.

Why not?

It's possible we want Webpack for other reasons - other JS/CSS plugins we don't foresee right this moment. In that case, it might make more sense to just keep our Tailwindcss build step in Webpack.

This is done in #552


Choose tech stack

Goal

Research the best technologies to use for this project, taking in account the needs and limitations expressed in the below details section.

Details

The ultimate goal of the project is to create a blazing-fast, secure, and easy-to-maintain personal portfolio website. The website will likely support multiple languages and have a blog section. Therefore, the editorial experience should be fast and enjoyable with minimal friction when creating new content or adding languages.
The chosen technologies should be widely adopted and supported, have a low cost to host and maintain, and be based on PHP (and frameworks) and/or JavaScript (and frameworks). They should also be easy to test.

After evaluating several options, I opted for the following tech stack:
Backend

Sanity.io CMS

Frontend

Next.js 13
TypeScript
Tailwind CSS

Dev Tools

Conventional Commits
Prettier + ESLint
Husky
GitHub Actions
Docker

Details

One of the goals is to be able to easily edit and publish new content. For this reason, I excluded the option of a frontend-only approach using Markdown to manage the blog. I tried this option in the past and found it frustrating to deal with multiple languages.
I looked at many different content management system (CMS) options, like WordPress, Strapi, Craft CMS, Statamic, and even one I made myself using Laravel. I decided to use Sanity.io because it's hosted in the cloud, so I don't have to worry about managing hosting. The free plan is enough for this project, and upgrading later won't be too expensive. Another good thing is that Sanity.io uses Node.js, which makes it easier to use the same programming language (JavaScript) for both the frontend and backend. Lastly, it's open source.
There are many reasons why I chose to use Next.js. First, I was already familiar with this framework. Second, it's commonly used in the industry. Third, it's based on JavaScript. Fourth, it works well with Sanity.io. Lastly, it's open source.
It's important to note that Next.js 13 made some big changes that could be helpful for this project. These changes include the app directory, turbopack, and @next/font.
Tailwind CSS is a way to avoid maintaining separate CSS files when developing components (using CSS modules). I already have experience with it, and it is widely used with Next.js.
Conventional Commits is a specification that helps enforce standards in commit messages.
Prettier and ESLint will be used to define code standards, and Husky will be used to enforce them locally (including the conventional commits).
GitHub Actions will be used as a second check to enforce code standards remotely, and it will probably be used for publishing on stage and production.
Docker is the best option for having a stable and reliable local environment on my machine and whoever wants to contribute to the project.
There are two tools that could be useful to evaluate while working: pnpm and class-variance-authority. I used pnpm recently in some projects and it seems really fast compared to npm or yarn. class-variance-authority seems to be a great option for building type-safe UI components, according to their website.


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/jupyter-dash-feedstock#4.


Join problem

How can I use JOIN with static values?
The second (joining) table has column "xyz" and I need to create JOIN query where "xyz" = 123
Thank you.

I found similar problem here https://github.com/catfan/Medoo/issues/167
Can you please add the modifier [$] to the next release of Medoo

I ran into the same problem, but came up with a quick solution for v1.0.2 while the developers find a neat way to add support for this.
Note: this quick hack is only meant to get you through the problem if you're in a bind.
Step 1, change line 595 to the following:
BEFORE:
	'"' . (isset($match[ 5 ]) ? $match[ 5 ] : $match[ 3 ]) . '"."' . $value . '"';
```php

AFTER:

```php
	((substr($value, 0, 4) == '[SV]') ? substr($value, 4) : '`' . (isset($match[ 5 ]) ? $match[ 5 ] : $match[ 3 ]) . '`.`' . $value . '`');
```php

Step 2, add temporary support for denoting a static value by preceeding your join value with "[SV]". For example, in your table join, instead of using something like [ 'fieldName' => 'fieldValue' ] use this instead:

```php
[ 'fieldName' => '[SV]fieldValue' ]
```php

Hope this helps.


Organism and BFO:Object v. BFO:Material Entity

In OBI, the immediate parent of 'Organism' is material entity. Following this treatment, 'homo sapiens' in NCBITaxon is a subclass of 'material entity'.
Human beings, however, are generally treated as objects in BFO (see p. 36 of the BFO specification where 'human being' is said to meet the criteria for BFO:object). This makes its way into some BFO-conformant ontologies. For instance, the Common Core Ontologies hold that Person is_a BFO:object, and Ontoneo declares 'pregnant woman' as subclass of BFO:object.
The result is a problem. I'm working on an ontology now where 'pregnant woman' from ontoneo and 'homo sapiens' from the NCBITaxon are both imports. The result is that I can't infer that pregnant women are homo sapiens, because although both are material entities, pregnant women are objects and homo sapiens are mere material entities.
Thoughts?

I would assume that pregnant women would be defined as humans in a specific
state? Any such classification should not be affected by differences in the
parents as material entity vs. object. If you can provide a bit more detail
on the logical definitions, that would be helpful.
On Sat, Feb 2, 2019 at 6:38 PM J. Neil Otte<EMAIL_ADDRESS>wrote:

In OBI, the immediate parent of 'Organism' is material entity. Following
this treatment, 'homo sapiens' in NCBITaxon is a subclass of 'material
entity'.
Human beings, however, are generally treated as objects in BFO (see p. 36
of the BFO specification where 'human being' is said to meet the criteria
for BFO:object). This makes its way into some BFO-conformant ontologies.
For instance, the Common Core Ontologies hold that Person is_a BFO:object,
and Ontoneo declares 'pregnant woman' as subclass of BFO:object.
The result is a problem. I'm working on an ontology now where 'pregnant
woman' from ontoneo and 'homo sapiens' from the NCBITaxon are both imports.
The result is that I can't infer that pregnant women are homo sapiens,
because although both are material entities, pregnant women are objects and
homo sapiens are mere material entities.
Thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/obi-ontology/obi/issues/994, or mute the thread
https://github.com/notifications/unsubscribe-auth/ANN9Iq_2VD4UXDhIUqA_4yIlDCVSgU73ks5vJkuggaJpZM4af5qF
.

--
Bjoern Peters
Professor
La Jolla Institute for Allergy and Immunology
9420 Athena Circle
La Jolla, CA 92037, USA
Tel: 858/752-6914
Fax: 858/752-6987
http://www.liai.org/pages/faculty-peters

The issue is Ontoneo placed 'pregnant woman' under BFO:object (per the BFO spec). As a result, the class is not a subclass of 'Homo sapiens', which is_a obi:Organism and thus is-a BFO:material entity. We shouldn't now have to assert that pregnant woman is-a homo sapiens (on pain of multiple inheritance). See a wee screenshot here:

None of these classes are disjoint, so one could still declare instances of pregnant woman are also instances of homo sapiens without contradiction. The point is more that this is the sort of inference that the class taxonomy should give one, and the distinction between Object and Material Entity is getting in the way here.

When I look in Ontobee, it seems that in Ontoneo pregnant woman is a subclass of 'homo sapiens', and organism, and object, and material entity, just like it should. Maybe your issue comes from looking at versions of the ontology that are not reasoned?

Ok, this is odd (and thanks for helping me try to get to the bottom of this). When I open the owl files, in OntoNeo, OBI:organism is subclass of BFO:object as depicted in your screenshot. However, in the OWL for OBI, this is not asserted. It doesn't appear to be a reasoning issue.

See also gravid organism in uberon: https://www.ebi.ac.uk/ols/ontologies/uberon/terms?iri=http%3A%2F%2Fpurl.obolibrary.org%2Fobo%2FUBERON_0009097
We should have all design patterns registered such that cross-ontology reasoning will work (e.g if ontoneo uses the same DP as uberon then your class will be inferred under the uberon class here)

I believe this was a local reasoning issue and has been resolved. Please reopen if I'm mistaken.


How to get maximum character width?

I'm trying to render a text entry box that allows for up to 30 characters to be entered. To calculate its width, I need to know the max possible width of a 30-character string. Assuming nothing funny happens with spacing between letters, I think I can just multiply 30 by the max width of any character in that font.
I found global_bounding_box, and so I'm trying this:
let font_id = ...;
let font_size = 21;
fontdb.with_face_data(font_id, |data, face_index| {
        let font = ttf_parser::Face::from_slice(data, face_index).unwrap();
        let scale = (font_size as f64) / (font.units_per_em().unwrap() as f64);
        scale * font.global_bounding_box().width() as f64
})

For the Overpass regular font, I get 30.4 from this, which seems visually to be too wide for most of the alphanumeric characters I'm trying out. Is there maybe an outlier character that's especially wide, or is this calculation incorrect? I'm not sure what units global_bounding_box returns, nor if my understanding of units_per_em is correct.
Thanks!

global_bounding_box returns a rectangle that is guaranteed to feet any glyph in the font. But it's not a tight box, afaik. And it doesn't even have to be correct. It just a random value stored in the font. It's not calculated or anything.
Calculating a width of N characters for non-monospaced font in general doesn't make any sense. In most cases it would be too wide.
There are a lot of values you might be interested in hhea table, but ttf-parser doesn't export most of them. This is an easy fix.

units_per_em

This is just an internal font scale. It's used to convert between font units and application units (like pt).

Calculating a width of N characters for non-monospaced font in general doesn't make any sense.

I'm guessing most text boxes with a character limit are manually tuned, then, and support horizontal scrolling. I'll probably take this route, then. Thanks for confirming!

There are a lot of values you might be interested in hhea table

I might experiment with ttf-explorer and learn about these, but no need to expose here.


make device(NN::AbstractExplicitLayer) instead of error

close https://github.com/LuxDL/LuxDeviceUtils.jl/issues/24

@avik-pal can you approve workflows?


Tracking: online scaling in compute node

To support scaling in our system, we decide to generally follow the design in Re-Introduce Configuration Change based on Pause Barrier. After consistent hash has been utilized in most of the critical places in our system (#3543), it's high time we start doing this!
This task can be roughly divided into several steps below.

[ ] Support creating and dropping actors in existing fragments.
The minimal scaling granularity will be decided as a fragment, in this way we can support finer-grained scaling requests and implement it with more ease: It's easy to find that complex scaling can be formed by a series of fragment scaling.

[ ] #3751
[ ] #3752
[ ] Support connecting or disconnecting an actor from the upstream and downstream of the graph.

[ ] Improve parallel unit management in meta service.
Based on the step above, the compute node is able to scale the number of actors in each fragment. However, whether a fragment can scale or where the new actor will be scheduled should be determined by the parallel unit management in meta service. Currently, we use a fixed number of parallel units for each compute node and always utilize all of them for parallelized fragments, which should be tweaked to be more flexible.

[ ] Prune the differences between Hash and Single parallel unit.
[ ] More flexible parallel unit allocation or fragment scheduling.
[ ] Utilize parallel units of newly joined compute nodes.

[ ] Really take advantage of scaled actors with correct data distribution.
Needless to say, the ultimate goal of scaling is to harness the computing of distributed systems to fit the user-required throughput. So it's not enough that we're able to create or drop actors independently, but we also need to distribute data correctly and evenly with the new configuration. Thanks to consistent hash and unified storage accessing layer of state table, it's not that hard to implement this. However, due to Hummock's special transaction design and the concurrent checkpoint introduction, we still have to handle the consistency carefully.

[ ] Implement pause and resume with barrier for source and chain.
[ ] Rehash strategy for the vnode mapping to keep locality as much as possible.
[ ] Support updating partition on configuration change for each operator.

[ ] Unify other configuration changes with the scaling pipeline.
We may add fail-over and actor migration support before this task is done. However, some of these configuration changes can be treated as a specific form of scaling. For example, migrating an actor from one node to another is simply a scale-in and scale-out within a single barrier, where the partitions of other actors are untouched.

[ ] Actor migration based on scaling.
[ ] Source split change based on scaling.
[ ] ...

[ ] Interface with cloud manager.
After online scaling is fully implemented, we can interface with the cloud manager and make the whole thing automated by some scaling policies.

Support connecting or disconnecting an actor from the upstream and downstream of the graph.

Isn't this already covered by AddOutput and Stop?

Support connecting or disconnecting an actor from the upstream and downstream of the graph.

Isn't this already covered by AddOutput and Stop?

Exactly. However, they're only used for creating and dropping materialized views. We should reuse them to support creating and dropping parallel units.

What should the interface be for this? I guess you are referring to having a high-level interface in meta like:
// in meta/..
fragment.add_parallel_units(par_unit_ids: &[usize]) // -> create_actors, delete_actors, add outputs to upstream, stop prev outputs from upstream
fragment.remove_parallel_units(par_unit_ids: &[usize])

Currently, we need to wait until new actors are created, before we can send AddOutput barrier messages? Or is there a form of synchronization for this in the LocalStreamManager?

Furthermore, what should be the behaviour for stateful operators? Should it always replace all of the current actors? Or should we allow existing actors to continue?

In the latter case,  we need an `UpdateVnodes` barrier message, which if it matches the actor ID of the executor, will trigger update of vnodes of the state table. The state table will need to flush its previous state, ensuring `!state_table.is_dirty()`.
Some of the keys (for scale up) may no longer be relevant to the node. We could rely on LRU to evict these unused keys or explicitly evict them by iterating through all the keys in the application cache and evict the ones whose vnodes are in the removed_vnodes set.
After resume barrier, we can make use of the new vnodes in the state table.

I guess for the time being we can stop all actors and create new ones for the entire fragment. It's unproven whether its necessary to reuse existing actors. Actor startup should be fast and cache can be populated easily from block cache.

I guess you are referring to having a high-level interface in meta like:

Exactly.

Currently, we need to wait until new actors are created, before we can send AddOutput barrier messages?

Yep. This is very similar to creating materialized views. Currently, we first build the actors on the worker nodes and then issue a command to the global barrier manager. Therefore, the consistency is kept.

whenever there are new compute nodes added, we can scale up to the new parallel units

Yes. This will be included in the step "Utilize parallel units of newly joined compute nodes."

Should it always replace all of the current actors? Or should we allow existing actors to continue?

In the original design by @fuyufjh, we will drop all of the current actors for simplicity. However, after we've unified the state interface with StateTable, updating the partition info (vnodes) can also be simple so I think we can reuse the existing actors.

Actor startup should be fast and cache can be populated easily from block cache.

Not sure how much it will cost, while keeping the cache in the original actors can always be better.

Should it always replace all of the current actors? Or should we allow existing actors to continue?
In the original design by @fuyufjh, we will drop all of the current actors for simplicity. However, after we've unified the state interface with StateTable, updating the partition info (vnodes) can also be simple so I think we can reuse the existing actors.

Agree. Actually, my initial design is to reuse the existing actor and ignore the data that is not owned by it anymore, which will not affect anything and will be evicted out soon or later in theory. But please feel free to simplify the design.


OTA-559: pkg/manifest: Add 'overrides' handling

Centralize this aspect of manifest filtering, so it can be shared between the cluster-version operator (where it currently lives) and oc (where we want manifest extraction to understand this sort of condition).

/cc

grumbles about repos that do not respect gh reviews
/lgtm


Testing/frontend and controllers

Set up tsconfig and package.json to correctly read and run jest tests in a node environment with .js, .jsx, .ts, and .tsx with react testing library, and supertest. Added necessary testing libraries and types for typescript. Wrote unit tests for two frontend components, as well as multiple back end controllers. Wrote integration tests for existing API calls, and wrote templates for upcoming ones.
All active tests currently pass. Skipped tests are either incomplete, or failing for unresolved reasons. These tests are still under development.

Also I changed the npm test script to not run a build. I did this because it quadrupled how long it takes to run the full suite of tests. This change can be reverted.


fix(reflection): ensure complete stripping of relative paths with multiple leading slashes

This PR addresses an issue where relative paths with leading slashes and dots were not being stripped correctly. The problem arises when the 'path' contains multiple leading slashes like ../../, as the current logic strips it to /../, which is incorrect and prevents the entity from being discovered.
This code modification ensures that any dots followed by slashes are stripped to provide the full path without any dots and slashes at the beginning.
Please note: that the current behavior is such that if you pass ./my/path the result is /my/path However, with the updated code, the result will be my/path This change is made because, in the end, we use the resulting path to check if the source contains the path using endsWith, and the leading slash is unnecessary for this purpose.
Update
I added a slash again after @B4nan clarified a case that we need it in this thread
so the result now for ./my/path will be /my/path

Thanks!


Resize in a WordPress post?

Hi,
I'm trying to use Plain Draggable in a WordPress page (can't show it because it's still only on my local drive). I'm using Scrips N Styles to allow me to add CSS and JS to the page.
I'm following your JSFiddle from here: https://jsfiddle.net/byaje56n/
And the closed thread: resize element? #7
Anyway, all is working fine outside of WordPress.
In WordPress all is fine as well, except when I switch to responsive.
When I'm in responsive mode and begin to drag the handle, the box immediately expands down below the bottom of the window. See the attached image (two screenshots combined).

I cannot figure it out.
Here's what's in the main html:

Here's what's in the CSS:
#mainBx {
    position: relative;
	height: 200px;
  }

#box {
	background-color: transparent;
	border-style: solid;
	border-width: 1px;
	border-color: #000000 !important;
	display: flex;
  }

#handle {
    /* Disables panning and selecting on touch devices */
	touch-action: none;
	user-select: none;
	cursor: pointer !important;
	position: absolute;
    background-color: #43ba8e;
    width: 30px;
    height: 30px;
    left: 400px;
    top: 200px;
  }

Here's what's in the JS before body closing:
window.addEventListener('load', function() {
  'use strict';

  let handle = new PlainDraggable(document.getElementById('handle'));
  let box = document.getElementById('box');

  function resize() {
    let rect = box.getBoundingClientRect();
    box.style.width = handle.rect.right - rect.left + 'px';
    box.style.height = handle.rect.bottom - rect.top + 'px';
  };

  handle.onMove = resize;
  resize();

});

Hi @LetsHaveASquint, thank you for your comment.
So, you have to reproduce a matter to inspect any problem.
I copied your code to JSFiddle on your behalf.
https://jsfiddle.net/poku2re7/
Then it seems to work fine.
Could you explain about that?
And, can you update this to reproduce the issue?

Also, what is the "responsive mode"?
Do you mean that you specified viewport breaking in CSS for RWD (Responsive Web Design)?

Hi.
Responsive mode when inspecting in the browser (to simulate other devices, screen sizes, etc.)
Thanks for putting it on Fiddle! I did not try because I didn't think it would help.
The Fiddle does not reproduce my issue exactly, but I can use it do give you an idea.
In the Fiddle, change the #mainBx height to 600px and also the #handle top to 600px.
Then Run.
It starts fine, but when you move the handle you'll see that the bottom of the box drops down.

I see.
Maybe you are using Google Chrome, and Google Chrome has "Device Mode" in DevTools.
You called "Device Mode" by "responsive mode". That's right?
And, "Response Viewport Mode" in "Device Mode" in DevTools of Google Chrome is used for RWD.
Anyway, I updated the code for 600px on your behalf. And I fixed the code for scrollable viewport.
https://jsfiddle.net/xrp53chb/
The cause of this issue is "scroll value", it is not "responsive". Also, it is not only Y axis.
Note that those bear no relation to PlainDraggable.
PlainDraggable is a library to allow HTML/SVG element to be dragged.

Yes. I think that solves it. Thanks!
And thanks for the tutorial too.

:smile:


Fix missing static dependencies for wmagent package

Fixes #11583
Status
ready
Description
With the current PR we add some missing static dependencies for the wmagent package, which are crucial for the deployment through pypi or locally.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None
External dependencies / deployment changes
None

hi @amaltaro I just changed to the reduced set of couchapps you pointed. Can you take another look? Thanks.
BTW:
looking into the t0_agent list few lines bellow I find three more:
src/couchapps/WMStats+
src/couchapps/LogDB+
src/couchapps/UserMonitoring+

Do you confirm, we do not need them for wmagent?

For the record, the issue this PR is supposed to fix is still sitting in the ToDo status. Please do make sure to set them to "In Progress" whenever you start working on them.


Bug: Default Nested Route (index.vue) Not Loading

When using nested routes with a default child (index.vue), the child component fails to load.
This issue is caused by an extra /. appended to the child route's path.

To Reproduce
https://stackblitz.com/edit/nuxt-starter-4vjb8d
Remove the module from nuxt.config to see the difference
Expected behavior

hello
https://s00d.github.io/nuxt-i18n-micro/guide/faq#❓-what-if-a-route-doesn-t-load

Same problem even after adding a route name to the children (index.vue), did you check the stackblitz ?
The problem is that the default child path is renamed (/. is appended) :
-| profiles/
---| [id]/
-----| index.vue // This one is not loaded by default on route /profiles/[id]
---| [id].vue

I checked it, and it's a different error. Can you explain why you need this at all? I don’t understand why anyone would do this or how it could be useful. It looks more like a bug than something intentional.

fixed. try v1.38.1


Dockerizeit

Hi,
I have created a Dockerfile for the tools.

I've also set-up an automatic build on dockerhub, is you want to take a peak: https://hub.docker.com/r/mattions/maftools/

Closing this one, 'cause superseded by #6


Named captures conversion to grok pattern_definitions format

Description
This PR contains a utility class for taking any regex string and pulling out the named captures groups from it for the grok pattern_definition format. It then replaces the original named captures group with grok syntax %{SYNTAX:SEMANTIC}. It creates random pattern names to go with the PATTERN_NAME regex format of pattern definition declaration
Issues Resolved
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #586 (19febe0) into main (42c5954) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #586   +/-   ##
=========================================
  Coverage     92.12%   92.12%
  Complexity      569      569
=========================================
  Files            71       71
  Lines          1727     1727
  Branches        144      144
=========================================
  Hits           1591     1591
  Misses          105      105
  Partials         31       31

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 42c5954...19febe0. Read the comment docs.


Not possible to apply custom height to Progress

components: Progress
reactstrap version 8.8.1 (since 8.5.0)
import method - irrelevant
react version 16.14
bootstrap version 4.5.3

What is happening?
It's not possible to apply custom height to Progress component as style prop is applied to the inner progress-bar element instead of the root progress element.

It's broken since 8.5.0 (likely because of #1771). Seems like #1970 in 8.7.0 tried to fix that but it didn't.
What should be happening?
It should be possible to specify height with CSS styles as per Bootstrap doc:

The above should be equivalent to:
<Progress value={25} style={{ height: "1px" }} />

Steps to reproduce issue
https://codesandbox.io/s/reactstrap-progress-bug-tuqb1?file=/src/App.js

We should revert #1771 and expose a progressStyle prop or something to support it.

We should revert #1771 and expose a progressStyle prop or something to support it.


Task history breaks if you specify an empty string as a parameter value

The task history interface currently uses the id_to_name_and_params function to parse the task_id into a (task_family, {params}) tuple.
Unfortunately, the parsing patterns used is not robust to empty parameter values (e.g. task_id = 'Foo(bar=bar, baz=)' as the value token is omitted.
Does anyone have an easy fix for this, otherwise I'll try to submit a PR sometime soon?

No, there's no easy fix. It's just broken. :(
We would very happy to review a PR removing the use of that function. :)

ugh i've maintained for a long time that we need to kill the id_to_name_and_params function.
maybe i should just go ahead and do it. i hate it

Fixed by https://github.com/spotify/luigi/pull/1309


Question: About the process of obtaining EEGCLIP's Top-k Accuracy

Hello. I have a question about the evaluation of EEGCLIP.
EEGCLIP learns to have high similarity between 1:1 pairs of EEG-Images, and when obtaining top-1, 3, and 5 accuracy,
is it measured by seeing whether the pairs are exactly matched or whether there are identical classes within k?
(Other papers utilizing the CLIP structure between EEG and images sometimes use the latter method,
so I would like to ask you about the exact evaluation method.)

Hi @gyuseok0917 , top-1 accuracy is equivalent to the accuracy that we measure in general. The reset Top-5 or Top-k checks whether they have a match in Top K predicted classes or not.


Mapnik python3

Fixes #243.
Add a docker-compose file to spin up the environment to run the mapnik source tests
against Python3.5

It doesn't harm anything, but do we want to spin up RabbitMQ as part of the docker compose step?  Also, we git clone girder_worker, but don't install or use it.  I think it would be better to do nothing with RabbitMQ or girder_worker OR to install and start girder_worker in a docker_compose service so it is available if we want it.

@manthey You are right. This confused me. I fixed it.


Chore/tweaks

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Improve code example in README

It's a bit difficult to parse the example in the README. A few suggestions:

Using multiple DSLs in the example detracts from showcasing the API. For example, the SQL and the Pandas APIs do similar things, so it would be better to use only 1 for clarity.
Add comments. I'd include one at the top to explain what specifically the prediction pipeline is doing, and then sprinkle some to explain key parts of the API. For example, I'm curious whether the operator decorator does something to maintain resource allocations, or if the model reaquires the GPU on each invocation. Also, some of the kwargs could be clarified (e.g. update_mode='replace').
Re-format the example to match the rest of the codebase (uses double quotes whereas the readme example uses single quotes).

Thanks, @pschafhalter! #99 addresses most of your feedback.
The only thing that we didn't do is remove the Pandas DSL -- we currently require users to retrieve data (usually with SQL queries) and manipulate it in Pandas, since most users are comfortable with Pandas. Your feedback is great, and we'll definitely think more about simplifying the API, but it's not something we can support out of the box.


Fix rendering of 3D model

The texture orientations were incorrect since OpenGL expects the 0.0 to be at the bottom of the y-axis.

Thanks!


ci(releases): leverage semantic-release to deploy beta and stable versions to the app/play store

Description
The idea is to have semantic-release auto push builds to beta and from beta to stable without manually pushing builds in the play store to the production. This may be a little hard for the app store since it seems that I have to manually submit an update for review.
Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[x] ✅ Build configuration change
[ ] 📝 Documentation
[ ] 🗑 Chore

:tada: This PR is included in version 2.7.13-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.7.13-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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

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


[ENG-1132] Add draft/register component

Ticket: [https://openscience.atlassian.net/browse/ENG-1132]
Feature flag: n/a

Purpose
Add register component.
QA
n/a

Pull Request Test Coverage Report for Build 3598

34 of 39 (87.18%)  changed or added relevant lines in 6 files are covered.
14 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.04%) to 75.752%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/registries/addon/drafts/draft/-components/register/component.ts
22
27
81.48%

Files with Coverage Reduction
New Missed Lines
%

lib/registries/addon/drafts/draft/controller.ts
1
81.63%

lib/osf-components/addon/components/registries/draft-registration-manager/component.ts
6
78.38%

lib/osf-components/addon/components/registries/finalize-registration-modal/manager/component.ts
7
74.0%

Totals

Change from base Build 3596:
-0.04%

Covered Lines:
8234

Relevant Lines:
9541

💛  - Coveralls

Closed in favor of ember-osf-web#814.


Update history view

Update the history view to use Element.select() so that it updates when the underlying DAO changes.

I signed it!


Save image and signature as one

I am currently using this SignaturePad. My goal is to have an image of file/document to be signed. What I want is to save the image and the signature as one image file.
What is the current behavior?
When I click save, I only get the signature alone.
What is the expected behavior?
When I click save, It should save the image and the signature as one jpeg or png.

My Fiddle linked in #511 could solve this
https://jsfiddle.net/HugeHugh/mhp5rxqk/

It is not from this library but I made my own react component. In case someone needs it.
https://codesandbox.io/s/canva-with-background-image-uf652c


Fail to require (in cjs) CSS modules from an npm package

Describe the bug
The background is I have some existing packages whose generated code is in CommonJS + CSS modules. E.g.
"use strict";
var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
exports.circularFont = void 0;
const circular_font_module_scss_1 = __importDefault(require("./circular-font.module.scss"));
exports.circularFont = circular_font_module_scss_1.default.circularFont;
//# sourceMappingURL=index.js.map

This file uses require() to load CSS Modules.
In Vite, it fails to be loaded, however, an import works.
Reproduction
https://github.com/Jinjiang/reproductions/tree/vite-cssmodules-20230523
Steps to reproduce
pnpm install
pnpm dev

Then open browser, the console panel will show up:
import a css module {foo: '_foo_iyjzy_1', bar: '_bar_iyjzy_5'} // works
require a css module {__esModule: true} // not
{foo: '_foo_iyjzy_1', bar: '_bar_iyjzy_5'} // works
undefined // not
{foo: '_foo_1clpo_1', bar: '_bar_1clpo_5'} // works
{foo: '_foo_iyjzy_1', bar: '_bar_iyjzy_5'} // works

System Info
$ npx envinfo --system --npmPackages '{vite,@vitejs/*}' --binaries --browsers

  System:
    OS: macOS 13.4
    CPU: (8) arm64 Apple M1
    Memory: 69.14 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.15.0 - ~/.asdf/installs/nodejs/16.15.0/bin/node
    Yarn: 1.22.19 - ~/.asdf/shims/yarn
    npm: 8.5.5 - ~/.asdf/plugins/nodejs/shims/npm
  Browsers:
    Safari: 16.5
  npmPackages:
    vite: ^4.3.8 => 4.3.8

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

In the development stage, you can use vite plugin<EMAIL_ADDRESS>to solve this problem. It provide esbuild plugin which can solve the commonjs import problem during esbuild pre-build stage.
import cjs2esm from 'vite-plugin-cjs2esm'
// https://vitejs.dev/config/
export default defineConfig({
  // ...
  plugins: [
    // ...
    cjs2esm()
  ],
  // for pre-build
  optimizeDeps: {
    esbuildOptions: {
      plugins: [esbuildPlugin()]
    }
  }
})

@haijie-x thanks for the information. I tried to install this package and added vite config file you provided. Then I got another error:
Error:   Failed to scan for dependencies from entries:
  C:/Users/zhaoj/code/reproductions/index.html

  X [ERROR] The JSX syntax extension is not currently enabled

    html:C:/Users/zhaoj/code/reproductions/index.html:1:0:
      1 │ <script type="module" src="index.js"></script>
        ╵ ^

  The esbuild loader for this file is currently set to "js" but it must be set to "jsx" to be able to parse JSX syntax. You can use "loader: { '.js': 'jsx' }" to do that.

    at failureErrorWithLog (C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:1636:15)
    at C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:1048:25
    at runOnEndCallbacks (C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:1471:45)
    at buildResponseToResult (C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:1046:7)
    at C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:1058:9
    at new Promise (<anonymous>)
    at requestCallbacks.on-end (C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:1057:54)
    at handleRequest (C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:723:19)
    at handleIncomingPacket (C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:745:7)
    at Socket.readFromStdout (C:\Users\zhaoj\code\reproductions\node_modules\.pnpm\esbuild@0.17.19\node_modules\esbuild\lib\main.js:673:7)

Is there anything I missed? Or do you have any idea how to make it works?
Thanks.

@Jinjiang Thanks for your feedback, please try the latest package version v1.0.6, a minor issue has just been fixed.

@Jinjiang Thanks for your feedback, please try the latest package version v1.0.6, a minor issue has just been fixed.

I just tried it and it works.

Cool. It works on 1.0.6 as you mentioned. Thanks so much.

Hi, I'd like to reopen this issue since:

the plugin @haijie-x mentioned is still in debugging
even this plugin can help, I still feel the root cause of this issue is about the native process of CSS/SCSS files in Vite, not a missing plugin to transform CJS code to ESM since other CJS syntax could be well-transformed natively.

Thanks.

This seems to be a regression from 4.2.0 caused by https://github.com/vitejs/vite/pull/12343.
We should still use export * + export default for CSS modules files.

@sapphi-red thanks for pointing this out. I further found it works on v4.1.x 😅


Version mis-match

Even after installing version 3.0.3 when we run the command "handlebars -v" it outputs 3.0.1.

This broke after we updated to use es6 scoped variables. Will be fixed in the next release.

Released in 4.0.0


Run WASM binary in the rodata section

Feature
We are using the WAMR v1.3.x version, and see that the WASM binary can only be put in the data section, or to be more precise the WASM binary is only able to be put into RAM instead of ROM.

In some low-cost hardware solutions, the RAM is too low to run multiple WASM binary, and I also try to XIP-AOT, but its size looks like much larger than the WASM binary(some AOT data also needs to be put into RAM?). Because they are low-cost hardware solutions, so ROM space should also be saved.

Is there any method to run the WASM binary in the rodata section? Or do you have any plans for this?

Benefit
When this feature is implemented, the low-cost hardware solution can save much RAM for the applications and run more WASM binary at the same time.
Implementation
No implementation, but if I could do something, please tell me.
Alternatives
No.

Is there any method to run the WASM binary in the rodata section? Or do you have any plans for this?

i don't think wamr provides a suitable running mode for the use case right now.
i'm not aware of anyone working on it either.
maybe it isn't too difficult to make the classic interpreter avoid in-place modifications.
it might be a bit cumbersome to deal with value-polymorphic instructions though.
cf. https://github.com/yamt/toywasm/blob/master/doc/annotations.md#type-annotations-for-value-polymorphic-instructions

It is actually possible to run the FAST interpreter from ROM. It uses more memory though.


Test for Send/Sync/other traits with where Self: Send + Sync + ...

I think it is better to add a where clause to the struct/enum/union definition which is required to be Send/Sync/any other trait.
First, of all, it becomes part of the item declaration and second, it doesn't require compiling the crate with cfg(test) for verifying the implementation of the auto traits.
Compare this (taken from this paragraph):
#[test]
fn test_send() {
    fn assert_send<T: Send>() {}
    assert_send::<MyStrangeType>();
}

#[test]
fn test_sync() {
    fn assert_sync<T: Sync>() {}
    assert_sync::<MyStrangeType>();
}

To this:
struct MyStrangeType
where
    Self: Send + Sync
{
    // ...
}

This style doesn't conflict with clippy and rustc lints.
So how about amending that paragraph with the new guideline?

This suggestion conflicts badly with trivial_bounds. The following compiles even though the type is neither Send nor Sync.
#![feature(trivial_bounds)]

struct MyStrangeType
where
    Self: Send + Sync,
{
    ptr: *const u8,
}

I think that this particular case should be added to the Drawbacks section of the rfc at least. This is indeed unfortunate, with my proposal the issue would be detected only upon the first type usage...

it doesn't require compiling the crate with cfg(test) for verifying the implementation of the auto traits.

A better solution for this would be:
const _: () = {
    fn assert_send<T: Send>() {}
    let _ = assert_send::<MyType>;
};

A better solution for this would be:

Well, nope, even this should be enough:
const _: () = drop::<MyStrangeType>;

I think the current guideline is the approach I prefer most, so I'll go ahead and close this issue.


move space to proper location

It had "subda y=" instead of "subday ="

@johnpaulcook : Thanks for your contribution to the SQL documentation! The author, @edmacauley, has been notified to review your proposed change.

Thanks for catching that typo.  Looks good.  #sign-off


panic in "cursors.(*IntegerArray).Len(...)"

Steps to reproduce:
I am porting the contents of a mariadb containing electrical power meter measurements to influxdb.
The data is coming in statsd and is still being fed to mariadb currently. I then set another statsd exporter  in parallel which sends data to telegraf with statsd plugin which in turn feeds it to influxdb v2.6.1. I use both influxdb UI and grafana to see the measurements over time.
This all goes well in principle. The bucket is set to never delete data.
I also wrote a script (attached here: convert_mariadb_influxdb.py.gz) to push the ~2 years of measurements (of around 1 point per minute) of 2 different devices from mariadb to influxdb.
For that, I stopped telegraf, cleaned the bucket, and run the script until it was done, and then started telegraf again.
This works all great: all data is now in influxdb (the one from the script and current ones fed from telegraf), I can see it using infxludb UI and grafana.
The system runs for several days, all fine. Then I decided to restart influxd service (systemctl restart influxdb).
Intermediately after the db is restarted (correctly), grafana and influxdb UI show correctly data up to 12h ago, but fails to show data properly if I set the graph to show data 24h or older.
Every time I try to get the larger timespan of data (let's say show me data for last month), it fails in both grafana nd influxdb UI, and I see this panic of influxdb in journald:
Jan 30 19:09:27 localhost influxd-systemd-start.sh[2287937]: ts=2023-01-30T19:09:27.554914Z lvl=info msg="Execute source panic" log_id=0fi0xAqW000 service=storage-reads error="panic: runtime error: invalid memory address or nil pointer dereference" stacktrace="goroutine 7425 [running]:
runtime/debug.Stack()
	/go/src/runtime/debug/stack.go:24 +0x68
github.com/influxdata/flux/execute.(*executionState).recover(0x400687a6c0)
	/go/pkg/mod/github.com/influxdata/flux@v0.191.0/execute/recover.go:32 +0x1e0
panic({0xffff97a41260, 0xffff98f587f0})
	/go/src/runtime/panic.go:838 +0x204
github.com/influxdata/influxdb/v2/tsdb/cursors.(*IntegerArray).Len(...)
	/root/project/tsdb/cursors/arrayvalues.gen.go:227
github.com/influxdata/influxdb/v2/tsdb/engine/tsm1.(*integerArrayAscendingCursor).reset(0x400474cf50, 0x173e8ea8e718340b, 0x40038fd290?, {0x0?, 0x40065f1590?, 0x67?}, 0x40056a8cf0)
	/root/project/tsdb/engine/tsm1/array_cursor.gen.go:333 +0xf4
github.com/influxdata/influxdb/v2/tsdb/engine/tsm1.(*arrayCursorIterator).buildIntegerArrayCursor(_, {_, _}, {_, _, _}, {_, _, _}, {_, ...}, ...)
	/root/project/tsdb/engine/tsm1/array_cursor_iterator.gen.go:46 +0x35c
github.com/influxdata/influxdb/v2/tsdb/engine/tsm1.(*arrayCursorIterator).Next(0x4006a06e70, {0xffff97e00858, 0x40038fd290}, 0x400573e250)
	/root/project/tsdb/engine/tsm1/array_cursor_iterator.go:67 +0x210
github.com/influxdata/influxdb/v2/storage/reads.(*multiShardArrayCursors).createCursor(0x400573e240, {{0x0, 0x0, 0x0}, {0xffff652118a0, 0xb, 0x3ff760}, {0x40065f1590, 0x5, 0x5}, ...})
	/root/project/storage/reads/array_cursor.go:118 +0x158
github.com/influxdata/influxdb/v2/storage/reads.(*windowAggregateResultSet).createCursor(0x40065f13b0, {{0x0, 0x0, 0x0}, {0xffff652118a0, 0xb, 0x3ff760}, {0x40065f1590, 0x5, 0x5}, ...})
	/root/project/storage/reads/aggregate_resultset.go:100 +0x8c
github.com/influxdata/influxdb/v2/storage/reads.(*windowAggregateResultSet).Next(0x40065f13b0)
	/root/project/storage/reads/aggregate_resultset.go:84 +0xf4
github.com/influxdata/influxdb/v2/storage/flux.(*windowAggregateIterator).handleRead(0x40057b0200, 0xffff97e00858?, {0xffff97e0ca58, 0x40065f13b0})
	/root/project/storage/flux/reader.go:742 +0x340
github.com/influxdata/influxdb/v2/storage/flux.(*windowAggregateIterator).Do(0x40057b0200, 0xffff97cadfc0?)
	/root/project/storage/flux/reader.go:688 +0x2b0
github.com/influxdata/influxdb/v2/query/stdlib/influxdata/influxdb.(*Source).processTables(0x400393d600, {0xffff97e00858?, 0x40038fd290}, {0xffff97df4188, 0x40057b0200}, 0x0?)
	/root/project/query/stdlib/influxdata/influxdb/source.go:69 +0xb8
github.com/influxdata/influxdb/v2/query/stdlib/influxdata/influxdb.(*readWindowAggregateSource).run(0x400393d600, {0xffff97e00858, 0x40038fd290})
	/root/project/query/stdlib/influxdata/influxdb/source.go:303 +0xd4
github.com/influxdata/influxdb/v2/query/stdlib/influxdata/influxdb.(*Source).Run(0x400393d600, {0xffff97e00858, 0x40038fd290})
	/root/project/query/stdlib/influxdata/influxdb/source.go:50 +0x7c
github.com/influxdata/flux/execute.(*executionState).do.func2({0xffff97e028b8?, 0x400393d600})
	/go/pkg/mod/github.com/influxdata/flux@v0.191.0/execute/executor.go:535 +0x310
created by github.com/influxdata/flux/execute.(*executionState).do
	/go/pkg/mod/github.com/influxdata/flux@v0.191.0/execute/executor.go:515 +0x398
"

So it seems restarting the process is breaking something in the state ot database or god knows.
Expected behavior:
Data to be displayed fine after process restart, as it did before I restarted the process.
Actual behavior:
After process restart, data older than 24h seems to be failing to be shown, influxdb panics.
Environment info:
The host holding the database is a RPI4 with btrfs disks in RAID to have duplicate data.
# uname -srm
Linux 5.10.0-18-arm64 aarch64

# influxd version
InfluxDB v2.6.1 (git: 9dcf880fe0) build_date: 2022-12-29T15:52:06Z

Fixed: https://github.com/influxdata/influxdb/pull/24787


Error in plugin hardhat-foundry: User-configured sources path (./contracts) doesn't match path configured in foundry (contracts)

Component
Other (please describe)
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (e4a2915 2022-06-19T02:24:29.337547Z)
What command(s) is the bug in?
No response
Operating System
macOS (Intel)
Describe the bug
I have checked the corresponding files according to this error ,  i.e. hardhat.config.ts & foundry.toml
here is hardhat.config.ts :
'''paths: {
sources: "./contracts",
tests: "./test",
artifacts: "./artifacts",
cache: "./cache",
},
'''
here is foundry.toml :
'''
default = { libs = ["node_modules", "lib"] }
[profile.default]
src = './contracts'
out = 'out'
libs = ['node_modules', 'lib']
test = 'test/foundry'
cache_path  = './cache_forge'
'''
i have ensured both of them are using './contracts ' , but the error still persists .

FYI I ran into the same issue with VS code Hardhat plugin, uninstall & reload & reinstalling the plugin solved the issue for me

I was seeing this error as well with the VS Code Solidity (by Nomic) plugin, uninstalling, reloading, and then reinstalling the plugin worked for me.

please reopen this in https://github.com/foundry-rs/hardhat repo if still an issue. Thank you!


Changed npmignore to add the whole test directory and remove innecessary directories

The test directory isn't needed at all when installed this package as a dependency and are 8MB we could save from network and disk. Also the .git directory is ignored by default, so there's no need to add it.

Please, also update 1.x releases so we can benefit from the space reduction in other projects already using the package.

This has been tackled properly in the upstream project (https://github.com/jquery/esprima).


feat(Usage Reports): add "created_by_email_id" to Offer schema

PR summary

updated offers to have the CreatedByEmailID field
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Current vs new behavior

updated offers to have the CreatedByEmailID field
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Test results:
•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••
Ran 109 of 109 Specs in 3.477 seconds
SUCCESS! -- 109 Passed | 0 Failed | 0 Pending | 0 Skipped
PASS
ok      github.com/IBM/platform-services-go-sdk/usagereportsv4  5.164s

@Jdatechong the builds are finally green, but I just noticed you used an old version of the generator for this PR (released on Apr 10). Could you re-gen your code by using the current latest, please? This applies to your other PRs too, but I'll leave comments just to make sure we won't miss anything. Thanks in advance and sorry for the late notice!

@pyrooka SDK has been regenerated with version 3.96.0

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


Restore some features that appear in files and file lists

Fixes #3945
Missing:

[ ] forked-to
[ ] fork-source-link-same-view
[ ] any more features affected? Probably every isRepoTree/isSingleFile

Test 1

Visit https://github.com/sindresorhus/eslint-plugin-unicorn/tree/main/docs
Notice edit-files-faster and latest-tag-button
Enter the folder
The same features are still working
Open a markdown file
Notice view-markdown-source (wrong position due to https://github.com/sindresorhus/refined-github/pull/4243)

Test 2

Visit https://github.com/sindresorhus/refined-github/tree/main/source/features
Open a tsx file
Notice copy-file and rgh-feature-description

Test 3

Visit https://github.com/sindresorhus/refined-github/tree/main/source
Enter a folder
Notice download-folder-button and default-branch-button

So far I found
same-page-definition-jump
html-preview-link
list-prs-for-file

It's starting to feel like it's a lot 😂 I'm glad I'm adding the selector checker so I don't have to clutter every init with if !exists(), return

[ ] forked-to
[ ]  fork-source-link-same-view

@fregante whats the plan for these 2?

As mentioned, all isRepoTree/isSingleFile are affected, but I'll merge this for now to create a release today.

As mentioned, all isRepoTree/isSingleFile are affected, but I'll merge this for now to create a release today.

same-page-definition-jump

How is that affected? It uses delegate, it never had to be called multiple times

Its not called multiple times. It never gets activated in the first place. The same way all the other features didn't load unless you refreshed the page.


Deprecation warning when trying to trans() with a null value in replacements

Laravel Version: 9.10.0
PHP Version: 8.1.5

Description:
Trying to feed trans() a second argument that is an array with a key and a null value results in a deprecation warning:
local.WARNING: ErrorException: mb_substr(): Passing null to parameter #1 ($string) of type string is deprecated in /app/vendor/laravel/framework/src/Illuminate/Support/Str.php:941
While that case isn't described in the Laravel documentation, it used to work and still does. I also believe it's reasonably common to occur, especially when just feeding the values from the database into the translator.
Steps To Reproduce:

Configure the deprecations log as per docs
Run the following:

trans('validation.after', [
	'date' => null,
]);

See a deprecation warning:

[2022-04-30 20:42:31] local.WARNING: ErrorException: mb_substr(): Passing null to parameter #1 ($string) of type string is deprecated in /app/vendor/laravel/framework/src/Illuminate/Support/Str.php:941
Stack trace:
#0 /app/vendor/laravel/framework/src/Illuminate/Support/helpers.php(418): Illuminate\Foundation\Bootstrap\HandleExceptions->Illuminate\Foundation\Bootstrap\{closure}()
#1 /app/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(106): with()
#2 /app/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(71): Illuminate\Foundation\Bootstrap\HandleExceptions->handleDeprecation()
#3 /app/vendor/laravel/framework/src/Illuminate/Foundation/Bootstrap/HandleExceptions.php(229): Illuminate\Foundation\Bootstrap\HandleExceptions->handleError()
#4 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->Illuminate\Foundation\Bootstrap\{closure}()
#5 /app/vendor/laravel/framework/src/Illuminate/Support/Str.php(941): mb_substr()
#6 /app/vendor/laravel/framework/src/Illuminate/Support/Str.php(1011): Illuminate\Support\Str::substr()
#7 /app/vendor/laravel/framework/src/Illuminate/Translation/Translator.php(220): Illuminate\Support\Str::ucfirst()
#8 /app/vendor/laravel/framework/src/Illuminate/Translation/Translator.php(194): Illuminate\Translation\Translator->makeReplacements()
#9 /app/vendor/laravel/framework/src/Illuminate/Translation/Translator.php(124): Illuminate\Translation\Translator->getLine()

Thanks for reporting this. I've sent in a PR for this: https://github.com/laravel/framework/pull/42216


lwIP Library: Build system generates wrong output when PROJECT is defined in a parent Makefile

I tried to build a lwIP example in VS Code and noticed the build error which states the liblwip_soft.a is not found. Dug down and found that VS Code's build task defines the PROJECT item while calling the makefile, lwIP's makefile tries to redefine the PROJECT item but it seems it can not without the override keyword.
Output which indicates the error:
  ...
  CC    C:/MaximSDK/Libraries/CMSIS/../lwIP/netif/ppp/polarssl/des.c
  CC    C:/MaximSDK/Libraries/CMSIS/../lwIP/netif/ppp/polarssl/md5.c
  CC    C:/MaximSDK/Libraries/CMSIS/../lwIP/netif/ppp/polarssl/sha1.c
  CC    C:/MaximSDK/Libraries/CMSIS/../lwIP/Maxim/mxc_eth.c
  AR    C:/MaximSDK/Libraries/lwIP/bin/softfp/lwIP_FreeRTOS.a

  arm-none-eabi-gcc.exe: error: C:/MaximSDK/Libraries/lwIP/bin/softfp/liblwip_softfp.a: No such file or directory

Thanks @ahmetalincak.  I did some clean-up of the lwip library Makefiles.  It should fix the issue.
Your review and testing for #669 would be greatly appreciated.


in 'Getting Started' – let's NOT hash the password (it's already hashed)

Bug discovered, here:
https://github.com/Laravel-Backpack/CRUD/blob/de5668b0b3742877ed6577a5972ac85326ddd46b/src/resources/views/ui/inc/getting_started.blade.php#L42-L44
Summary and findings
☝🏼 In the Getting Started card guide include, (3.) prescribes this extra hashing of $entry->password inside of setupCreateOperation().
In trying and testing this, I found that a user created while this code was in place could not, in fact, log in using the provided password.
Upon further testing and inspection of both $entry->password and also request('password'), what seems to be the case is that $entry->password has already been hashed (by laravel?), and so invoking \Hash::make() on this value is hashing a hash, thus breaking this user's ability to log in with the originally provided password.

Proposed resolution:
Simply remove this recommendation or prescribed code block

or, annotate somehow if it is specific to the version of Laravel... is it needed in Laravel 9 and below, but not in Laravel 10??

Php, Laravel, and Backpack version(s) context / report =>
### PHP VERSION:
PHP 8.3.1 (cli) (built: Dec 21 2023 17:49:39) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.3.1, Copyright (c) Zend Technologies
    with Zend OPcache v8.3.1, Copyright (c), by Zend Technologies

### LARAVEL VERSION:
<IP_ADDRESS>

### BACKPACK PACKAGE VERSIONS:
backpack/backupmanager: v5.0.0
backpack/basset: 1.2.2
backpack/crud: 6.5.1
backpack/generators: v4.0.2
backpack/theme-coreuiv4: 1.1.1

Hey @emjayess
Thanks for reporting your findings & proposing a solution. I appreciate your efforts and time.
My will colleague @pxpm will review it.
Cheers!

Sorry @emjayess it took me so much time to get back here, I totally missed this. 😞
I've just fixed it in backpack/crud:6.7.14
Thanks for the heads up 🙏


Energy efficiency

I deployed plain nanoweb on a micro-controller and I'm observing it takes a lot of power while being idle, it continuously varies from 5 to 20 mA. How to make it more energy efficient?

I think the problem is Micropython / uasyncio related and we can't do anything about that in Nanoweb code.

You are correct, unfortunately - it's indeed python itself and related wifi driver... Thanks, I'm closing the issue.


Space-view screenshotting on Web

(this issue assumes https://github.com/rerun-io/rerun/pull/8258 has been merged)

https://github.com/rerun-io/rerun/pull/8258 introduced egui-based screenshotting of space views. However, it is not implemented on web. For that to work we need to:

https://github.com/emilk/egui/issues/5425
https://github.com/emilk/egui/issues/5424 - this is optional, and probably the most work. When implemented, we can remove our own crates/viewer/re_viewer_context/src/clipboard.rs

https://github.com/rerun-io/rerun/pull/8472 implemented save-to-file one web
Copy to clipboard still needs to be implemented


JBPM-4958 and BZ-1160144 Update process instances and tasks search

Allow searching by task id and process instance id if search criteria is only numbers
Search for process definition id using exact match

@manstis or @ederign are you guys able to help with this one? thanks

+1 to merge.

Merged into 6.4.x.


Example on streaming h264

Thanks for the project.
Is it possible to directly feed h264 chunks instead of reading from file?
Purpose is to mux h264 into mp4 file. h264 chunks coming from https://github.com/pion/webrtc

Is it possible to directly feed h264 chunks instead of reading from file?

Sure, check out this comment. It basically allows you to demux raw video frames and do whatever you want with frames afterwards, like remuxing them into an mp4 file in your case.
Let me know if that answers your question.

Thank you for your reply. Quick question. From  the official ffmpeg compilation page they say that nasm and yasm need to be included for performance reasons. For the bindings are they required/included?
Thanks.

Can you link to that documentation?
The bindings only use the ffmpeg you have installed, they don't include any external lib. They're only required if the way you use the bindings require nasm or yasm.

Hello,
here is the link:
https://trac.ffmpeg.org/wiki/CompilationGuide/Centos
I tried to make install-ffmpeg and it complained that nasm/yasm is not installed so I had to compile the from source. My os did not have nasm/yasm. Maybe your OS has them already and did not complain.

Ha ok, that's a dependency you need to build ffmpeg. This is not link to these bindings 👍


PyTorch Profiler docs are out of date

📚 Documentation
Tips on how to run the PyTorch profiler in the lightning docs are only relevant for the legacy profiler.
Details on the modern pytorch profiler (which integrates with tensorboard) are here.
These changes should be reflected in the Lightning docs.
cc @borda @rohitgr7 @carmocca @kaushikb11 @ninginthecloud

Thanks for letting us know @scottgigante-immunai
Are you interested helping us improve these docs?

Unfortunately not something I have time for, sorry! Appreciate all of your work 🙏

Hi @awaelchli ! I'd love to take this up if possible!

@aseemk98 great! Feel free to send a PR with the updates. Are you familiar with the PyTorch profiler?

@awaelchli No, I've never used it before. But I'll go through it.

I am interested in working on this issue, assign it to me if possible!!

I am interested in working on this issue, assign it to me if possible!!

cool! :rabbit:

Hey @awaelchli
I quickly checked the docs and they look ok.
Given the time that has passed, I assume that the issue has been fixed but was forgotten to close.

Thank you @Andrei-Aksionov, yes looks like it, hakuna matata.
If anyone finds typos or incorrect references, feel free to directly open a PR with the correction.


Fix release version in footer

This has been broken since we moved to EKS and the SHA is no longer provided.
We can use the SENTRY_RELEASE environment variable which is defined for every app and takes its value from the container image's tag.
If for whatever reason the image tag is not defined it will display null, which should make it clearer (instead of displaying development) that this data is not being pulled in successfully.
Before:

After (tested in Integration):

Trello card: https://trello.com/c/uoKDUcbV/3182-fix-broken-version-footer-in-publishing-apps-2
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
Follow these steps if you are doing a Rails upgrade.

Looks good and nice idea of using the SENTRY_RELEASE!

I cannot take the credit - this was @robinjam 's suggestion! 🥇


[PLT-1450] cardano-node-emulator generator generate cardano-tx

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[ ] Commit sequence broadly makes sense
[ ] Key commits have useful messages
[ ] Formatting, PNG optimization, etc. are updated
[ ] Important changes are reflected in changelog.d of the affected packages

PR

[ ] Self-reviewed the diff
[ ] Useful pull request description
[ ] Reference the ADR in the PR and reference the PR in the ADR (if revelant)
[ ] Reviewer requested

@berewt Seems everything is working for this PR. Just darwin CI has an unrelated issue. I'll force merge it?

Yes I think we can force merge this one. The darwin build pass locally.


[ADAM-851] Slienced Parquet logging.

Fixed the ParquetLogger utility so that it silences org.apache.parquet.hadoop
instead of parquet.hadoop. All is quiet again. Resolves #851.

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

Rebased.

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

Thanks!


Error when running gridsome build

Hi, I hope this is the right place to ask for help. I'm using vue-easy-slider in a Gridsome website and it works like a charm when running the site locally. With gridsome develop I can run the site on my local dev and the slider is fully functional.
I put the slider in it's own component btw. It looks like this:
<template>

    <slider animation="normal" interval="8000">
      <slider-item v-for="edge in $static.testimonials.edges" :key="edge.node.id">

{{edge.node.quote_by}}

      </slider-item>
    </slider>

</template>

<static-query>
query {
  testimonials: allTestimonial {
    edges {
      node {
        id
        title
        quote_by
        content
      }
    }
  }
}
</static-query>

When I want to deploy the website by running gridsome build the slider causes the following errors:
$ gridsome build
Gridsome v0.7.14

Initializing plugins...
Load sources - 0.11s
Create GraphQL schema - 0.12s
Create pages and templates - 0.06s
Generate temporary code - 0.03s
Bootstrap finish - 1.55s
Compile assets - 8.08s
Execute GraphQL (25 queries) - 0.06s
Write out page data (25 files) - 0.01s
Could not generate HTML for "/":
ReferenceError: document is not defined
    at addStyle (node_modules/vue-easy-slider/dist/vue-easy-slider.esm.js:715:0)
    at assets/js/vendors~page--src--pages--index-vue.1fbf38b4.js:703:12
    at a.__vue_inject_styles__ (node_modules/vue-easy-slider/dist/vue-easy-slider.esm.js:751:0)
    at a.hook (node_modules/vue-easy-slider/dist/vue-easy-slider.esm.js:661:0)
    at Ft (/PATH_TO_WEBSITE/node_modules/vue/dist/vue.runtime.common.prod.js:6:11191)
    at Ze (/PATH_TO_WEBSITE/node_modules/vue/dist/vue.runtime.common.prod.js:6:25133)
    at a.e._init (/PATH_TO_WEBSITE/node_modules/vue/dist/vue.runtime.common.prod.js:6:32564)
    at new a (/PATH_TO_WEBSITE/node_modules/vue/dist/vue.runtime.common.prod.js:6:30340)
    at Vi (/PATH_TO_WEBSITE/node_modules/vue-server-renderer/build.prod.js:1:66307)

Do you have any idea what might cause this problem? Or do you suppose it's a Gridsome error?

OK, there's generate HTML error. I'll try Gridsome later.


refactor: remove frontend v2 in insert executor and fix some ut

What's changed and what's your intention?
As title.
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)

Checklist

[x] I have written necessary docs and comments
[x] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

LGTM, seems it has some conflicts with #2548

Yes, I will resolve the conflicts after #2548 merged.


Update comments.json with french translations

Hello,
Hope this french translation will be pushed soon to take benefit of it :)

It seems we've already merged a PR to update these translations. Please re-open a PR with revised changes if you'd like to make an amendment 🙂


Sample mono repo conversion (Bamboo && .net)

We get "build party": Bamboo creates a lot of builds when you create new branches (which in the customer case is a bit what we want because we had too few bamboo builds and instead had to manually package bumps everywhere).
Local compilation takes more time because you do not have pre-compiled packages that relieve the build (I have seen a mix of monorepo with build-cache packages where the packages reference versions in source control so you can get faster build locally by re-implementing npm / NuGet / maven though it's quite hairy to set up). The added compilation is neglible in this case.
Working on different services with separate branches becomes much more difficult.
Making changes to shared packages becomes much easier.
Harder to view "solution changes", i.e. subfolder changes in visual studio.
One project is partially loosely coupled (using some swagger generated APIs and one shared library) and add a lot of noise to the git history

The migration has been appreciated since the solution has simplified life for the people working on the codebase. Embracing a modular monolith approach has been beneficial for the project.


Cannot detect already installed ufw firewall

Deployment fails with fatal: [xxxxxxxxx.com]: FAILED! => {"changed": false, "msg": "No firewall detected, install one before proceeding (firewalld||ufw||iptables)"}
ufw was installed from https://github.com/weareinteractive/ansible-ufw

https://github.com/kyl191/ansible-role-openvpn/commit/ca6470e00dcb526ed4266920f6ed5dad46dc7710 was just merged, try again?


test: pipe stderr from go vet

Go vet outputs errors to stderr.
Without this, go vet result comparison is always true.

forgot we have set -e flag.


[Improvement] Remove warnings when compiling Gravitino

Issue: [#1809] Remove Warnings When Compiling Gravitino
Description:
When compiling the Gravitino project, several warnings related to unchecked operations and casts are being produced. These warnings indicate potential issues with type safety and unchecked operations, which can lead to runtime errors or unexpected behavior.
Details:
Location of Warnings:
Multiple occurrences in DTOConverters.java, AuditDTO.java, MetalakeDTO.java, CatalogDTO.java, SchemaDTO.java, ColumnDTO.java, and TableDTO.java.
Examples include unchecked calls to methods and unchecked casts, particularly with raw types and generics.
Impact:
The compiler's -Werror option is set, which treats warnings as errors. This prevents the project from compiling successfully until these warnings are resolved.
Steps to Reproduce:
Compile the Gravitino project with the -Xlint:unchecked option enabled.
Observe the warnings and errors in the compilation output.
Proposed Solution:
Type Safety:
Review and refactor the code to use generics correctly, ensuring type safety and eliminating unchecked operations.
Unchecked Casts:
Correct or suppress unchecked casts where possible, ensuring that the type conversions are safe and valid.
General Code Review:
Conduct a thorough review of the relevant files to ensure compliance with best practices and to resolve any potential issues that might lead to runtime errors.
Additional Information:
Removing these warnings is crucial as per the best practices and will help maintain code quality and reliability.
Related Issues:
None directly related, but fixing these warnings will improve overall code quality and maintainability.

There are some unsuccessful checks, will fix them!!


Bad fork_url provider: RelativeUrlWithoutBase

Component
Forge
Have you ensured that all of these are up to date?

[ ] Foundry
[ ] Foundryup

What version of Foundry are you on?
forge 0.2.0 (3c49efe 2022-07-14T00:05:10.018576Z)
What command(s) is the bug in?
yarn deploy (scaffold-eth2)
Operating System
macOS (Intel)
Describe the bug
[⠊] Compiling...
No files changed, compilation skipped
The application panicked (crashed).
Message:  Bad fork_url provider: RelativeUrlWithoutBase
Location: /Users/runner/work/foundry/foundry/utils/src/lib.rs:927
This is a bug. Consider reporting it at https://github.com/foundry-rs/foundry
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1: __mh_execute_header
at :
2: __mh_execute_header
at :
3: __mh_execute_header
at :
4: __mh_execute_header
at :
5: __mh_execute_header
at :
6: __mh_execute_header
at :
7: __mh_execute_header
at :
8: __mh_execute_header
at :
9: __mh_execute_header
at :
10: __mh_execute_header
at :
11: __mh_execute_header
at :
12: __mh_execute_header
at :
13: __mh_execute_header
at :
14: __mh_execute_header
at :
15: __mh_execute_header
at :
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.

your version is outdated, the new error message should include the URL, is the URL valid?

Hey @abhilashi—I tried reproducing with the latest foundry version but can't—I get the proper error message. Please check that:

Your URL is valid
It is complete (has http:// or https://

Closing as it doesn't seem like an actual bug. Please feel free to reopen if this persists.


Wrong config reading order in flatpak linux version

Contour Terminal version
0.4.3
Installer source
something else (please specify below)
Operating System
Linux Mint 22
Architecture
x86-64
Other Software
No response
Steps to reproduce
Change config in ~/.config/contour/contour.yml and see it ignored
Expected Behavior
Configs in ~/.config/ folder should have priority over configs in  ~/.var/app/org.contourterminal.Contour/config/
Actual Behavior
The ~/.var/app/org.contourterminal.Contour/config/contour/contour.yml config has priority over ~/.config/contour/contour.yml config
Additional notes
Flatpak version

Hi @ukiyocode,
The issue arises because the Flatpak environment sets the XDG_CONFIG_HOME environment variable to ~/.var/app/org.contourterminal.Contour, making ~/.var/app/org.contourterminal.Contour/config/contour/contour.yml the default configuration path. This path is used and created if it doesn't exist. To use a custom configuration, you can specify the config file explicitly by running: contour config ~/.config/contour/contour.yml

Ah sorry my bad. I first installed it through nix home manager but it didn't work (probably needed nixGL), but it still created config in ~/.config. So i was confused when i was changing it and nothing happened.

No worries, flatpak gives us some trouble from time to time with its weird environment xD
I am closing this issue


Crash Bug

BetterDiscord crashes when watching a screenshare and the streamer Alt+Tabs.

It doesn't anymore. Update to v1.2.0.

Alright I'll update and see.


Cannot lock running datastore after starting confirmed commit

Hi Michal,
after starting a confirmed commit a lock of the running datastore is rejected.
connect --login user
edit-config --target candidate
commit --confirmed
lock --target running
ERROR - There is an ongoing confirmed commit.

From my point of view this should be allowed and accepted. What do you think?
BR,
Peter

Okay, this specific case should work. Please test the fix, I did not bother to write a test because it seemed not worth it.


Add non standard types

Current Behavior
TBD
Steps To Reproduce
TBD
Anything else?
See https://github.com/CollectionBuilder/collectionbuilder-csv/issues/74 for further reference

not necessary as this is only needed in a box on the standard start page


dunst: Also install dunstify

Motivation for this change
Dunst was lacking dunstify which is really useful to use non-standard features of the notification daemon.
Things done

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

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

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

Please consider to put this behind an option flag as it is not guaranteed to build with every version of libnotify which is why upstream does not build and install it by default.

@jfrankenau Fixed and rebased


Generic transport trait

Here is a crate containing a generic transport trait to be used as the transport for MoQ.
This is largely inspired by h3::quic, with a few changes to make it simpler.
Currently, the traits are not required to be Send, but it is required by MoQ, so maybe we could also add that constraint on the traits.
Furthermore, we could merge SendStream and SendStreamUnframed to make it simpler.
I have a quiche-based implementation of this trait and an update of the relay that work correctly.
A next step would be to add setting priorities/urgency through the trait

Merged in https://github.com/kixelated/webtransport-rs


Add possibility to define custo kms key for server side encryption

what

Add possibility to define custom kms key for server-side encryption

why

its useful when you want to create you on custom managed KMS key

looks like pipeline is broken

/rebuild-readme

/terraform-fmt

@dmitriy-lukyanchikov thanks for the PR, LGTM.
Can you please run the following commands in the repo root:
make init
make github/init
make readme

It will add some new GitHub actions and workflows that we are adding to all repos.
Thanks

@aknysh hello, looks like its failing anyway, dont know why

/rebuild-readme

/test-all

/test all


seminiferous tubule multinucleated giant cells

Consider adding:
seminiferous tubule multinucleated giant cells
see https://ntp.niehs.nih.gov/nnl/male_reproductive/testis/setubmgcel/index.htm "Multinucleated giant cells in seminiferous tubules are a specific form of degenerating germ cell, in contrast to nonspecific germ cell degeneration "
syn: seminiferous tubule symplasts
Many existing annotations under MP:0002216 (abnormal seminiferous tubule morphology)

MP:0020550, placed under abnormal male germ cell morphology


Add thirdweb inAppWallet connector

Adds a connector for thirdweb's in-app wallet
unlike other connectors, made thirdweb an optional peer dependency
added docs

Closing for now. Can re-open when deps are minimized.


Atom crashing after start

Hi!
After installing atom-ctags through apm install, Atom crashes after a few seconds.
Deleting Atom-ctags fixes the problem, but after reinstall the problem comes up again.
OS: Mageia 4.1
Atom: 0.207.0 (happened also with 0.206.0)
Atom-ctags version: 4.1.2
This is what I found in dmesg (3 consecutive starts):
[ 3986.288171] atom[4927]: segfault at 0 ip 00007f05887e3789 sp 00007f0589575b40 error 4 in ctags.node[7f05887e0000+a000]
[ 4343.543522] atom[6165]: segfault at 0 ip 00007fce8bc63789 sp 00007fce8c9f5b40 error 4 in ctags.node[7fce8bc60000+a000]
[ 4836.282177] atom[6628]: segfault at 0 ip 00007f0196c2b789 sp 00007f01979bdb40 error 4 in ctags.node[7f0196c28000+a000]
Cheers!

Did you try install atom-ctags through atom setting view?

Yes, I also tried through Settings -> Install and the same issue happens.

I have played with it a little more and it seems that adding a directory with lots of data as project folder makes atom-ctags crash.
The directory I had was about 1.2GB big containing different sources (mostly java) and a few other resources (xmls, gzips, pdfs).
Maybe adding folders of such size is not very common, but a warning or error message would be helpful in such cases (with possibly disabling the package, as the user won't have a chance to remove the project folder in atom because it continuously crashes).
Cheers!

I have a similar situation (on OS X).  The repo is about a gigabyte, across 7300 files. Most of that is in a log directory, and in .git/objects

According to #107, can you please try remove .tags file and try if atom start normal? BTW, please tell me the size of your .tags file.

Not, the OP, but removing the .tags file did allow the project to open. My .tags file was 15,333,771 bytes. I received this message when I opened the project after removing the .tags: "Stopped: Build more than 5 seconds, check if /Users/kian/Documents/repo/jiff3 contain too many file.
Suggest that add CmdArgs at atom-ctags package setting, example:
--exclude=some/path --exclude=some/other"
I think I'll add some exclude paths, notably ./log and ./.git

Same problem, with a repo that has a directory containing about 1 GB worth of data. In my case, though, deleting the tags file and uninstalling/reinstalling didn't help -- I can't run atom on this project with atom-ctags enabled. That's a bummer because the package had been working pretty well!


⚠ Bofrost.fr has degraded performance

In 45c1e6c, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1165 ms

Resolved: Bofrost.fr performance has improved in d73a505 after 7 minutes.


📣 Update public.ecr.aws/docker/library/golang Docker tag to v1.21.3

This PR contains the following updates:

Package
Type
Update
Change

public.ecr.aws/docker/library/golang
stage
minor
1.20.4-alpine3.18 -> 1.21.3-alpine3.18

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


How to inclue css file from public in index.html?

Describe the bug
Hello, it's not a bug but a painful issues for me 😟
I had some css(font-awesome) file in public dir, i just want add to index.html:
<!DOCTYPE html>

        <link href="<%= BASE_URL %>/static/font-awesome/css/fontawesome.min.css" rel="stylesheet">
        <link href="<%= BASE_URL %>/static/font-awesome/css/brands.min.css" rel="stylesheet">
        <link href="<%= BASE_URL %>/static/font-awesome/css/solid.min.css" rel="stylesheet">
        <link href="<%= BASE_URL %>/static/font-awesome/css/regular.min.css" rel="stylesheet">

I do not want these css build into chunks 😄，but i got some warning:

I try to inclue css in main.js using xxx.css?url, warning is loss bu css build into chunks.
I find is set BASE_URL to not empty,  got warning.
Is there a suitable solution fix my problem, thanks.
Reproduction
https://stackblitz.com/~/edit/vitejs-vite-ojktgp?file=index.html&terminal=dev
Steps to reproduce
npm i && vite build
System Info
System:
    OS: Windows 11 10.0.22621
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-11300H @ 3.10GHz
    Memory: 2.78 GB / 15.79 GB
  Binaries:
    Node: 21.4.0 - E:\software\nodejs\node.EXE
    Yarn: 1.22.19 - E:\software\nodejs\global\yarn.CMD
    npm: 8.4.1 - E:\software\nodejs\global\npm.CMD
    pnpm: 8.14.1 - E:\software\nodejs\global\pnpm.CMD
  Browsers:
    Edge: Chromium (121.0.2277.98)
    Internet Explorer: 11.0.22621.1
  npmPackages:
    vite: ^5.0.12 => 5.0.12

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

是我不熟悉 vite 导致的乌龙😂
其实只需要正常引入，打包后会自动修正资源的引入路径。


Split TopLevelExportDefs away from LinkedClass

Side-effects for TopLevelMethodExportDefs in IRChecker:

Allow them on all class kinds.
Allow names containing __ for non JS classes.
Disallow references to JS class captures (this was a bug).

Split away from #4111. To be merged now, or not :)


Contributing fish completion?

Inspired by the zsh completion, I wrote fish completion for git ignore.
Is there a docs repo where I can contribute this?

Paste the script here and I'll add it. I used to have a repo that mirrored the docs, but gitbook.com got sensitive about changes that weren't exactly right.

complete -f -c git -n '__fish_git_using_command ignore' -a '(__fish_print_gitignore_list)'

function __fish_print_gitignore_list
  if ! set -q __FISH_PRINT_GITIGNORE_LIST
    set -g __FISH_PRINT_GITIGNORE_LIST (curl -sL https://www.gitignore.io/api/list)
  end
  echo $__FISH_PRINT_GITIGNORE_LIST | string split ","
end

Thanks @zubin I added that here: https://app.gitbook.com/@dvcs/s/gitignore-io-docs/use/advanced-command-line#zubin


rfc2629.xslt xml stylesheet reference?

In a generated version of the XML file, the following stylesheet reference is included at the top:
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.2.9 -->

This was submitted for publication and the result is found here:
https://tools.ietf.org/id/draft-pusateri-dnssd-update-proxy-00.xml
Which when viewed in a browser, is broken because it doesn't know where to find rfc2629.xslt but even if the file was local, the XML file can't be displayed in a modern browser due to unsafe load rules:
Unsafe attempt to load URL file:///Users/pusateri/doc/draft-ietf-dnssd-update-proxy/rfc2629.xslt from origin null. Domains, protocols and ports must match.
draft-ietf-dnssd-update-proxy.xml:2

So should an online version be included here?
Or should the xml-stylesheet be removed from the XML?

I put in that feature about seven years ago.  I think I know why the rules in the browsers changed, but I have no idea why they ended up the way they are now and particularly how different they are between browsers.
For me, this feature still works in Firefox when the files are local, so I use that to look at XML files.
The online link you gave also works in Safari, but with some breakage (it doesn't know as much XSLT as Julian's XSLT presumes).  You also used stand_alone: no (which for historical reasons is still the default), so the references don't work.
My recommendations summarized:

use stand_alone: true in the YAML header
use Firefox to look at the generated XML
use the most recent versions of rfc2629.xslt rfc2629-other.ent rfc2629-xhtml.ent rfc2629.dtd, placed in the same directory where the .xml is.

Thanks. Just verified this works ok with stand_aone: true using Firefox. Where do I find the most recent versions of rfc2629.xslt rfc2629-other.ent rfc2629-xhtml.ent rfc2629.dtd? It isn't obvious looking at  search results.

And why not reference stable online versions with href instead of a local version?

And why not reference stable online versions with href instead of a local version?

Can I make that work?  I don't think so.

[...] Where do I find the most recent versions of rfc2629.xslt rfc2629-other.ent rfc2629-xhtml.ent rfc2629.dtd? It isn't obvious looking at search results.

I think I'll delegate this question to Julian @reschke — he should know.

And why not reference stable online versions with href instead of a local version?

Can I make that work? I don't think so.

Wouldn't it make the version work at:
https://tools.ietf.org/id/draft-pusateri-dnssd-update-proxy-00.xml

That already works.  Maybe I don't follow.

That already works. Maybe I don't follow.

No, you're right. I was confused by an earlier discussion with Henrik. Thanks!

The reason the references don't work is that the browser refuses to load them:
[Error] Unsafe attempt to load URL https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.2136.xml from origin https://tools.ietf.org. Domains, protocols and ports must match. (draft-pusateri-dnssd-update-proxy-00.xml, line 2, x2)

stand_alone: yes solves this by resolving these references at XML generation time (which is also needed if you want to modify anchors).  Obvious, Henrik @levkowetz cut put them up on tools.ietf.org as well and you could reference them from there using XML_RESOURCE_ORG_HOST=tools.ietf.org and continue to use stand_alone: no.  But that won't work on datatracker, etc.

Thanks. I'm happy with stand_alone: yes
I was not aware of that switch.

And it does seem like a better default.

The latest release is always in http://greenbytes.de/tech/webdav/rfc2629xslt.zip, as explained in https://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html.

bq. The online link you gave also works in Safari, but with some breakage (it doesn't know as much XSLT as Julian's XSLT presumes).
I don't have a Safari to test with. If you tell me what happens, I might be able to fix it. It definitively worked a few years ago.

The XSLT errors seem to center around the date calculation:

(The same page works in Firefox.)
In Safari, the console unfortunately only has error messages about the literature references (separate problem, see above), nothing about the date processing.

Now I recall, this is a known issue. See https://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html#xslt.engines.browser and https://bugs.webkit.org/show_bug.cgi?id=4079. The issue might go away when a concrete date is given so that the XSLT doesn't have to ask the OS.

Thanks -- I have added myself to the Webkit bug (and probably everybody else interested in this should, too).

So the status about the XML display in browsers is:

Firefox 65 fully works via http:// and via file:///
Safari 12, Chrome 73, Opera 58 work via http://, but with limited date processing

Bibxml references only work if included via stand_alone: true in the YAML header.
Prerequisite is that the four files rfc2629.xslt rfc2629-other.ent rfc2629-xhtml.ent rfc2629.dtd are in the same directory as the XML files.  This is the case on http://tools.ietf.org/id — thanks to Henrik Levkowetz — so XML files in the Internet-Draft directory can be viewed right there in the above browsers.  Fresh versions of these files (e.g., for local use) can be obtained from
http://greenbytes.de/tech/webdav/rfc2629xslt.zip thanks to Julian Reschke.
Thanks to Tom Pusateri for causing this little status refresh.  I'm closing the ticket now.

FYI, on macOS, where only Firefox seems to work to display .xml files correctly, the XML file type is not associated with the Firefox Application and so you have to choose "Show All Applications" and then select Firefox to open the XML file from the Finder.

Chromium browsers should be fine as well wrt date processing.


Fix typos for Digital Millennium Copyright Act

Why:
The less typos, the easier read.
What's being changed:
Fixes typos for Digital Millennium Copyright Act.
URLs on review apps on heroku

https://docs-688--dmca-typos-in-site-p.herokuapp.com/en/free-pro-team@latest/github/site-policy/github-enterprise-subscription-agreement#352-copyright-infringement-and-dmca-policy
https://docs-688--dmca-typos-in-site-p.herokuapp.com/en/free-pro-team@latest/github/site-policy/github-supplemental-terms-for-microsoft-volume-licensing#252-copyright-infringement-and-dmca-policy

cf. https://github.com/contact/dmca
Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Thanks @tnir 🌟 I'll get this updated and merged!


Deploy to Web Server

From the README file, it states to copy the content of dist folder to your webserver.
But there seems to be no dist folder

you have before to build the angular project with : https://github.com/chat21/chat21-web-widget#build-for-production

Thanks

And also the build for production fails to compile the "vendor.bundle.js" file which is required
Please help

please paste the error

So i use the command below to build for production and i get only four bundles rendered. After its been deployed on the webserver, it provides an error indicating that vendor.bundle.js isnt available which of course it wasn't rendered
$ ng build --prod --base-href --output-hashing none
Your global Angular CLI version (9.1.0) is greater than your local
version (1.7.4). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
Date: 2020-05-31T20:54:33.548Z
Hash: e4e7830ce68f84576b0e
Time: 72393ms
chunk {0} main.bundle.js (main) 2.07 MB [initial] [rendered]
chunk {1} polyfills.bundle.js (polyfills) 173 kB [initial] [rendered]
chunk {2} styles.bundle.css (styles) 0 bytes [initial] [rendered]
chunk {3} inline.bundle.js (inline) 796 bytes [entry] [rendered]

also i use the command below to build for local development and i get only five bundles rendered
$ ng build
Your global Angular CLI version (9.1.0) is greater than your local
version (1.7.4). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
Date: 2020-05-31T20:56:26.317Z
Hash: 8e3ae240bb37cca0b2e5
Time: 19099ms
chunk {inline} inline.bundle.js, inline.bundle.js.map (inline) 3.89 kB [entry] [rendered]
chunk {main} main.bundle.js, main.bundle.js.map (main) 848 kB [initial] [rendered]
chunk {polyfills} polyfills.bundle.js, polyfills.bundle.js.map (polyfills) 549 kB [initial] [rendered]
chunk {styles} styles.bundle.js, styles.bundle.js.map (styles) 14.7 kB [initial] [rendered]
chunk {vendor} vendor.bundle.js, vendor.bundle.js.map (vendor) 6.87 MB [initial] [rendered]

This is the error after i integrate the chat widget into my page

No help here