Failed to resolve module specifier "vue"

Describe the bug
I can't deploy production ready version of histoire. When I run npm run story:preview, I see this error in browser:
Uncaught TypeError: Failed to resolve module specifier "vue". Relative references must start with either "/", "./", or "../".

Additionally, while building, I see errors like this:
vite v2.9.14 building for development...
transforming (379) node_modules/histoire/dist/bundled/components/base/BaseCheckbox.js'setupVue3' is not exported by '../../../../$histoire-generated-global-setup-resolved'
'setupVue3' is not exported by '../../../../$histoire-generated-global-setup-resolved'
'setupVue3' is not exported by 'src/histoire.setup.ts'
'setupVue3' is not exported by 'src/histoire.setup.ts'
'setupVue3' is not exported by '../../../../$histoire-generated-global-setup-resolved'
'setupVue3' is not exported by '../../../../$histoire-generated-global-setup-resolved'
'setupVue3' is not exported by 'src/histoire.setup.ts'
'setupVue3' is not exported by 'src/histoire.setup.ts'
Use of eval is strongly discouraged, as it poses security risks and may cause issues with minification
✓ 392 modules transformed.

Everything is ok when I type npm run story:dev.
Reproduction
histoire setup.ts
import "./lib-components/assets/css/colors.css";
import "./lib-components/assets/css/shadows.css";
import "./lib-components/assets/css/sizes.css";
import "./lib-components/assets/css/spaces.css";
import "./lib-components/assets/css/zIndexes.css";

import { defineSetupVue3 } from "histoire/client";
import Maska from "maska";

import {
  FontAwesomeIcon,
  FontAwesomeLayers
} from "@fortawesome/vue-fontawesome";
import { library } from "@fortawesome/fontawesome-svg-core";
import { fas } from "@fortawesome/free-solid-svg-icons";
import { far } from "@fortawesome/free-regular-svg-icons";
import { fas as fasPro } from "@fortawesome/pro-solid-svg-icons";
import { far as farPro } from "@fortawesome/pro-regular-svg-icons";
import { Dropdown, Menu, Tooltip, VClosePopper, VTooltip } from "floating-vue";
import vClickOutside from "click-outside-vue3";
import { directiveFn } from "@/lib-components/plugins/focusable";
import { AvailableLanguagesEnum } from "./entry";
import mitt from "mitt";
import makeI18n from "@/i18n";
export const i18n = makeI18n(AvailableLanguagesEnum.pl);
import { config } from "@fortawesome/fontawesome-svg-core";
config.autoAddCss = true;

library.add(fas);
library.add(fasPro);
library.add(far);
library.add(farPro);
export default defineSetupVue3(({ app }) => {
  app.use(i18n);
  app.use(Maska);
  app.component("VDropdown", Dropdown);
  app.component("VTooltip", Tooltip);
  app.component("VMenu", Menu);
  app.component("vClickOutside", vClickOutside);

  app.component("fa", FontAwesomeIcon);
  app.component("fal", FontAwesomeLayers);

  app.directive("focusable", directiveFn);
  app.directive("tooltip", VTooltip);
  app.directive("close-popover", VClosePopper);
  app.directive("click-outside", vClickOutside);

  const emitter = mitt();
  app.config.globalProperties.eventBus = emitter;
});

histoire.config.ts
import { defineConfig } from "histoire";

export default defineConfig({
  setupFile: "/src/histoire.setup.ts",
  tree: {
    groups: [
      {
        title: "Variables",
        id: "Variables"
      },
      {
        title: "Components",
        include: (file) => !file.title.includes("Serialize")
      },
      {
        title: "UI",
        id: "UI"
      }
    ]
  }
});

System Info
"vue": "^3.2.37",

node v16.14.2

  System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (16) x64 AMD Ryzen 7 5700U with Radeon Graphics
    Memory: 19.10 GB / 30.70 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 102.0.5005.61
    Firefox: 103.0
  npmPackages:
    @vitejs/plugin-vue: ^2.3.3 => 2.3.3
    histoire: ^0.8.4 => 0.8.4
    vite: ^2.9.9 => 2.9.14

### Used Package Manager

npm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/histoire-dev/histoire/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/histoire-dev/histoire/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://histoire.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/histoire-dev/histoire/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/histoire-dev/histoire/discussions).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

@Akryum
Reprodcution project:
https://github.com/Qualterink/error-vite-histoire-build

Clone it.
Npm i
Try npm run story:build
Try npm run story:preview -> in browser check console

This looks to be caused by rollup-plugin-peer-deps-external which externalize vue

Thank you. Your release to 0.9.1, solves the build problem.


bug415

Fixes #415
Describe the changes you have made in this pr -
added an if statement to check if there were no tags.
Screenshots of the changes (If any) -

Coverage remained the same at 83.922% when pulling 979eb04a45978cf20888ef2bbd54c60b1d30153d on shubhankarsharma00:bug415 into 532317c9d8d6b7d71e1b8035f741191301e7ba23 on CircuitVerse:master.

Great


Updated page not found documentation and examples

Changed documentation and examples after comments from working group and @joelanman.
The most common page not found will be for reasons we do not know, this is now the default example and one that appears first in the documentation.
The page not found because of a user mistake has been deleted because nobody has been able to show how we would confidently know it is because of a user mistake. This means all the examples are content patterns.
There is a new example for when a user tries to go to a real URL but the page cannot be displayed.

You can preview this change here:
Built with commit 2cf1e89c2242ee5852056c0b56029c798b2f4065
https://deploy-preview-463--govuk-design-system-preview.netlify.com

@amyhupe I have made the changes and updated the pull request.

The first example should have the code block closed. Other than that, this looks great to me.

@amyhupe I think I have fixed that. Let me know.

@amyhupe @stevenaproctor You can't currently close a codeblock that's HTML only, we might consider making nunjucks versions of these pages at a later date, shouldn't block this PR

@dashouse I have updated the code to revert back to how it was.


New method to find ASAT output files that are generated by Maven.

After adding CheckStyle, PMD and FindBugs to a bigger repository (dagger), I've noticed that our previous assumption that the output files are in the main target does not work for bigger repositories. This is because bigger repositories have multiple pom files in their project. This causes multiple output files to be generated (in different packages) instead of just one.
I've changed the way how we look for the output files. This new method uses the ProjectInfoFinder to find all output files, while also looking for the classes in the project.
I ran the new version on dagger again and it produced a visualization, though for some reason Maven didn't want to produce output files for FindBugs.
I've also changed the following in the pom file:

Version --> 1.0 to 1.1
Added description of the tool.
Added name of the tool.

Questions, comments and suggestions are all welcome.

The changes that you've made look good and should be working. I can't really test it because my Mac does not really want to run our project in Eclipse. It would be nice if someone else can actually verify that it is working

I've changed the way how we look for the package name for a class. The previous way does not work if the developer wrote JavaDoc before above the line where the package name is defined.

Nice work on looking for multiple output files, correcting to our official project name (UAV), and the some more cleanup of the code. :+1:  I will merge it.


test: bench

Summary
Related Links

Checklist

[ ] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

!bench

!bench


To specific python version in installer.sh

Hey,
in the file installer.sh I had problems, because in line 65 the command is python3.10 -m venv .
This created errors on my machine as I have Python 3.11.3 installe, so python3.10 isn't working.
Changing the line to python3 -m venv . solved the problem and should be future proof (as long as 3 is the main version).

yesterday I created a pull request that fixes this issue: https://github.com/JustTemmie/steam-presence/pull/10

fixed by #10


Send to front

Add ability to perform the following actions on a canvas node:

[x] Send to front

Will send a node to the front

Released in 0.0.2


Update configure-vmware-hcx.md

changing fleet to AV64

@jjaygbay1

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

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

The published article has been updated to reflect the changes made in this PR: https://learn.microsoft.com/azure/azure-vmware/configure-vmware-hcx#create-a-service-mesh


feat: update attributions

updates the attributions
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 41.62%. Comparing base (d2d9888) to head (db030c2).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4780   +/-   ##
=======================================
  Coverage   41.62%   41.62%
=======================================
  Files         105      105
  Lines        9858     9858
=======================================
  Hits         4103     4103
  Misses       5402     5402
  Partials      353      353

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


PigTimer

Reworked the custom timer interface.
All below commands work in tells (keep them private!) or regular say (share with your friends!)
  /t PigTimer-duration
  /t PigTimer-duration-label

or
/say PigTimer-duration
/say PigTimer-duration-label
where
  "PigTimer" is the identifying marker
  "duration" can be in time formats:
       hh:mm:ss
       mm:ss
       seconds
  "label" can contain any character, number, or underscore, but cannot have blank spaces

  "PigTimer", "duration", and "label" should be separated by a - dash

Examples:
  PigTimer-30                                30 second timer, with no label
  PigTimer-10-TenSeconds            10 second timer, with label
  PigTimer-10:00-TenMinutes        10 minute timer, with label
  PigTimer-10:00:00-TenHours       10 hour timer, with label
  PigTimer-120-description          120 second timer, with label 'description'
  PigTimer-6:40-Guard_George        6 minutes 40 second timer, with label 'Guard_George'
  PigTimer-1:02:00-LongTimer         1 hour, 2 minute timer, with label 'LongTimer'

The selection of "PigTimer" as the marker is in keeping with the whole PigParse theme, but is obviously somewhat arbitrary, and could be literally anything else.  It could also by synonym'd, like (PigTimer|.pt), for example.

Other than the comments above, this is a good change!


Add area lights to PBR lights extension

I've been experimenting with exporting the area lights in my scenes, but am having some issues with the unit conversion for strength. According to Blender docs, strength is measured in Watts, except for sun/mesh lights which use Watts/m^2
https://docs.blender.org/manual/en/dev/render/cycles/nodes/types/shaders/emission.html
Is there a standard unit I should be using for the GLTF format? My end goal is to get this scene into Three.js.
Intensity in Three.js is measured in Lumens https://github.com/mrdoob/three.js/issues/6259, further evidence is in https://github.com/mrdoob/three.js/pull/6255 that intensity is in lumens when physicalFalloff is set to true. However converting from Watts -> Lumens would give pretty high values for intensity.
Here is my PR for adding area lights to the exporter: https://github.com/KhronosGroup/glTF-Blender-Exporter/pull/135. So far I've left the raw strength value as is which gives me this (Blender Cycles on the left, ThreeJS on the right):

Hi @tehbelinda — the KHR_lights extension is currently a draft document and completely experimental, there is no decision (yet) of the standard units in the glTF spec for example. I think your suggestion of adding area light is worth considering though, could you write that in the discussion of the extension? Discussions are happening here: https://github.com/KhronosGroup/glTF/issues/945

Closing this issue out, as the upcoming KHR_lights extension does not yet cover area lights. I expect there may be more advanced lighting extensions later, e.g. perhaps related to Adobe Dimension. Would encourage you to provide roadmap feedback on the glTF repository if this is still something you're interested in. Thanks!


python.pkgs.catalogue: Remove dubplicate argument pytestCheckHook

Motivation for this change
Fix staging evaluation.
Things done

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

[ ] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] 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)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

duplicate of #97050 guess I should have just merged mine 9 hours ago...


Menu: Fix order of interfaces in groups

Issue:
I have recently noticed that sometimes interfaces in groups are ordered neither by their descriptions nor by their device names (e.g. optXX) making this part of the menu look messy. However, all the other interface lists in the menu (Firewall Rules, DHCPv4/6, Router Advertisements) seem to be properly ordered by the corresponding descriptions.
Investigation:
There is a place in the code where all interface lists are ordered before inserting in the menu and it looks ok:
https://github.com/opnsense/core/blob/89a2a8d51bf20f765adf8275de3c4ff66ac04c8c/src/opnsense/mvc/app/models/OPNsense/Base/Menu/MenuSystem.php#L246-L248
Next only groups and non-grouped interfaces are inserted in the menu. It also looks ok:
https://github.com/opnsense/core/blob/89a2a8d51bf20f765adf8275de3c4ff66ac04c8c/src/opnsense/mvc/app/models/OPNsense/Base/Menu/MenuSystem.php#L252-L267
Finally, the remaining (grouped) interfaces are inserted in the menu. The problem here is that the interfaces are inserted in the order of the keys in $ifgroups making the results of natcasesort over $iftargets useless:
https://github.com/opnsense/core/blob/89a2a8d51bf20f765adf8275de3c4ff66ac04c8c/src/opnsense/mvc/app/models/OPNsense/Base/Menu/MenuSystem.php#L269-L288
Solution:
The solution this PR proposes is to run the foreach cycle over the $iftargets['if'] instead or $ifgroups to keep the order ensured by natcasesort. I know it looks like there could be only one foreach cycle over $iftargets['if'] instead of two, but it won't work because the underlying logic of the class provides for groups being inserted before nested interfaces.
Another solution is to merge two foreach loops into one and use an extra array to trace group items.
Screenshots:
Before:

After:

@fichtner Reworked the solution, now only one foreach loop over $iftargets['if'] is required.

@vnxme how about https://github.com/opnsense/core/commit/d485b40096a50ab03d72651e9042826002ae01ea ?


Modified all the docs in the repository.

[x] What does this PR do?
Updates docs as per latest changes. Removes a lot of redundant information, adds relevant information, and creates a smoother workflow.
[x] What issue/task does this PR references?
Issue 2261: https://openshift.io/openshiftio/openshiftio/plan/detail/2261
[ ] Are the tests Included?
NA

@jarifibrahim and @michaelkleinhenz please take a look and let me know if any changes are required. Thank you.

@Preeticp Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 and visit http://localhost:5000 to access it.

@Preeticp Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 and visit http://localhost:5000 to access it.

[test]

@Preeticp Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 and visit http://localhost:5000 to access it.

@Preeticp Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 and visit http://localhost:5000 to access it.

@Preeticp Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2666 and visit http://localhost:5000 to access it.


feature Convert subqueries into algebraic expressions and …

…put them into the query tree
Proposed changes
Issue Number:
Problem summary
1.Originally, each expression would generate a scope, but now each node will generate a scope, reducing the repeated generation of scopes.
2.Added convert subqueries to algebraic expressions
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[x] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Please rebase master to re-run P0 test

I suggest first supporting analyzing and unnesting one type of subquery, e.g., converting InSubuqery to joins. Thus we could have a unit test to review the framework and main steps of unnesting subqueries.


Create S3 sink app for Kinesis

Moving this PR over to snowplow/master
Here's my preliminary implementation of a kinesis -> s3 raw event sink, re #506.
This is my first "from scratch" scala application so feel encouraged to rip it apart with constructive criticism and suggestions.
What I did:

Forked upworthy/amazon-kinesis-connectors to grab their pomfile, then modified it to work with the github maven plugin. For now I'm hosting the amazon-kinesis-connectors mvn repo on github. What's the best place to host this? -- this was my first experience packaging something in maven, not nearly as easy as rubygems or nodejs libs ;)
Used the Java amazon-kinesis-connectors library to build an app that pulls from a kinesis stream and flushes out to s3 every so often.
I copied the naming scheme in the example kinesis connector for files that are stored in S3. Would be nice to go to a year=YYYY/month=MM/day=DD/hour=HH scheme and have ETL jobs that support this.

Things I'm not sure about:

My built.sbt -- does this conform to the project guidelines ? Is this a sane way of doing it?
For some reason that I can't decipher there's an issue when I run sbt assembly on my box, something about the scala version. When I run  java -jar target/scala.2.9.1/kinesis-s3-sink it whines Error: Could not find or load main class com.snowplowanalytics.snowplow.sinks.kinesiss3.SinkApp ... Something I could fix with some googling but any hints? Have been using sbt run in the meantime.
I didn't really write a Scala wrapper for amazon-kinesis-connectors library as was suggested in the ticket, mostly because I wasn't sure what the "prettiest" way to do it was. Instead I just used the library as is, hope that's okay otherwise I could use some guidance as to how to write the Scala wrapper.
Because I'm new to Scala I'm pretty sure my code looks very Javaish. Any suggestions on how to make this code more Scala-idiomatic would be appreciated.
Class structure + naming conventions + project directory structure

TODOs I can think of:

Add a README.md
Add support for specifying access keys in the config file -- right now it's hardcoded to use DefaultAWSCredentialsProviderChain which uses the first of: Environment Variables - AWS_ACCESS_KEY_ID and AWS_SECRET_KEY, Java System Properties - aws.accessKeyId and aws.secretKey, Instance profile credentials delivered through the Amazon EC2 metadata service
Add support for some of the other relevant configuration options.
Add comments and method doc
Probably refactor this code based on feedback

The AWS permissions required to run this app are:

CloudWatch -- I tested with full access
DynamoDB -- I tested with full access. Needs to be able to create table, write to that table. The Kinesis library does checkpointing by creating a Table called "application-name" and periodically updating a key that stores the checkpoint.
Kinesis -- I tested with read/write access to a specific stream. Needs at least permission to read from the stream specified in the config.
S3 -- I tested with read/write access to a specific S3 bucket. At least permission to write to the configured S3 bucket.

Also I plan on rebasing this branch over-and-over as I clean up so if you fork from it be prepared to diverge :)

Closing since this has been merged into the next release.

:+1:


Webview packaging issue on the GitHub CI

There seems to be an issue with the GitHub Workflow that builds and package the extension after each commit: Rollup fails at resolving a path, and therefore fails at bundling the webview into a single HTML file. For this reason, the VS Code extension that can be downloaded from this repository is not working at the moment, as it is unable to load the file when creating the webview, which remains empty (out/webview/webview.inlined.html).
I do not experience this bug locally. Maybe it has to do with the version of Rollup used in the GitHub Workflow?
The exact error is visible in the logs of the GitHub Workflow, in the Build i-LaTeX step, e.g., https://github.com/exsitu-projects/ilatex/runs/6223585813?check_suite_focus=true.

The issue was caused by a typo in the path to cropperjsApi, which caused Rollup to fail remotely, but not locally—perhaps because MacOS does not deal with case-sensitive paths the same way Ubuntu does. It was fixed by ec6af8f0e140573acf9174f497789a37073004a0.


Ignore non-UTF-8 sequences in couchbase.log

errors='replace' replaces any invalid bytes with the Unicode replacement characters which is typically printed as <?>.

Nice patch, Vesko. Thanks for the contribution. I should have opened the file this way first time around. :-)


Improve deadletter sample

Addresses https://github.com/Azure/azure-sdk-for-net/issues/26564

API change check
API changes are not detected in this pull request.


New version on Cocoapods

Hi
I'm using the version of your library that's available on Cocoapods. I recently noticed a bug, that has been resolved in the current version available on your GitHub.
Is it possible to release a new version of your library on Cocoapods ?
Thanks

Sorry for the delay, just released 1.3.0 containing a whole bunch of bug fixes.


Grammar Browser VS Nodejs has different results

I am trying to get my grammar tested on a node environment but I got stuck because some strings that are valid on the browsers are not valid on node (v6.10.2). Also, when the grammar is supposed to generate some errors, on the browser the parser fire the error on the correct token instead on nodejs it gives me the wrong token.
I could try to provide a minimal example if I am able/allowed to.
Although, I wonder if there's been a case like this before (I couldn't fine an issue related to this problem).

Hello @ematipico
I have not encountered such a thing, particularly when the invalid behavior is on node.js
as travis runs both the unit tests and the examples tests on node 6/8/9, while
only the unit tests are being run in browsers (via selenium).
A minimal example would be needed to investigate this...

Please re-open once you have some way to reproduce it which I can debug 😄

Sure no problem. As I work in a closed environment, by policy I can't share all the code. Once I will be able to provide a repo to reproduce the issue I will get back to you.
Thank you very much for your feedback

If you get a small input reproducing the issue you can use that as the basis
to minimize the source code (removing parser rules not needed for the small input).


Code needs to be cleaned up

Code has a lot of unnecessary comments and dead code, needs a through clean up.

merged commit a7f1440 does a comprehensive cleanup

Release 0.9.7 will have comprehensive cleanup.

V 0.9.9 ready. Cleanup


Add botstats function

An function with some botstats should be added

:tada: This issue has been resolved in version 0.1.0 :tada:


[FEATURE] Support updating setting  attributes with persistent mapping

Is your feature request related to a problem? Please describe.

I want to edits settings attributes, like fields or questions, when they have a mapping attribute, and be able to log records. At the moment, this will fail because the mapper tries to assign values to questions or fields that have been deleted.
Describe the solution you'd like

An ideal solution would update the Settings.mapping within the setter methods so that delete attributes are removed from the mapping.
Describe alternatives you've considered

You can do this, but it either wipes the mapping, or is difficult to rebuild the mapping.
from random import randint
from datasets import load_dataset

ds = load_dataset("argilla/magpie-ultra-v0.1", split="train[:100]")
settings = rg.Settings.from_hub("argilla/magpie-ultra-v0.1")
settings.questions = [rg.TextQuestion(name="my_comment")]
settings.mapping = {}
dataset = rg.Dataset(name=f"magpie-ultra-{randint(0, 100000)}", settings=settings)
dataset.create()
dataset.records.log(ds)

Additional context

@frascuchon I will close this issue because we no longer rely on mapping in rg.Settings.from_hub


Chapter 19 tensorflow_serving_deploying_Problem

In Exporting SavedModels part, the code: (that is on this book2th)
saved_model = tf.saved_model.load(model_path)
inputs = keras.layers.Input(shape=...)
outputs = saved_model(inputs, training=False)
model = keras.models.Model(inputs=[inputs], outputs=[outputs])

The error appear:
"tensors, but found {}".format(keras_symbolic_tensors))
tensorflow.python.eager.core._SymbolicException: Inputs to eager execution function cannot be Keras symbolic tensors, but found [<tf.Tensor 'input_1:0' shape=(None, 28, 28, 1) dtype=float32>]

I don't know how to solve this problem even after searching online. Thanks for your help.

Hi @klyuhang9 ,
Thanks for your feedback. It seems that the TensorFlow team has simplified loading SavedModels into Keras models: now you just need to run tf.keras.models.load_model(model_path)!
Here's a small Colab notebook to demonstrate this.
I also noticed that it's no longer necessary to specify training=False.
I'll update the book and the notebook.
Hope this helps!

@ageron
Thanks, the problem solved by the way you mentioned.
By the way, I may find that （also in this section) "install tensorflow-serving-api" is suitable for the virtual environment that installed tensorflow-cpu; If the virtual environment that installed tensorflow-gpu, we need to install  "tensorflow-serving-api-gpu", otherwise the former will affect the use of GPU to run programs on tensorflow.

Great, I'm glad this solved the problem.
Thanks for your feedback regarding the CPU/GPU problem, I'll look into it.
Note that starting in TF 2.1 (and in TF 1.15, but not in TF 2.0), pip install tensorflow will install a version of TensorFlow that supports both CPU and GPU: it will first look for a GPU, and if it does not find one, it will fallback to CPU. If you need a smaller installation footprint and you don't care about GPU, then you can install pip install tensorflow-cpu which only supports CPU.
I'm guessing that the same will be true with tensorflow-serving-api.
Hope this helps.


Trying to figure out how to use new adapters architecture

Hi Hubot devs,
I've been using hubot before the changes on the adapters, and I'm trying to use it again now that adapters have been moved out of the core.

Also you can't use the new adapter system yet as Hubot v2.0.0 hasn't been cut.


update label instances

Fixes #28
This update gives text fields unique ids so that their labels can be appropriately associated with them.
Additionally, this PR also changes the examples of the .container class to not use labels as the first element, as labels were inappropriate for these markup patterns.  They have been replaced by paragraph elements.

@ggassmann if section and heading elements were appropriate here, then yes those would be useful elements to use.
However, being that this is a page that demonstrates how to use these styles, semantically it wouldn't make sense to change them for the current document as that would create a document outline that doesn't match the visual order.
e.g. if the visual headings were changes to h3s, as would be the next heading level down in the document outline, you'd have:
h2: Containers
  h3: Container.is-center
   p: Good morning. Thou hast had a good night's sleep, I hope.
  h3: Container.is-dark
   p: Good morning. Thou hast had a good night's sleep, I hope.
   p: Good morning. Thou hast had a good night's sleep, I hope.
   p: Good morning. Thou hast had a good night's sleep, I hope.

That said, the element that wraps this entire area of content is a section and the h2 is used appropriately to convey this information.  So an ideal usage for these containers is already in place on the page.

@ggassmann if section and heading elements were appropriate here, then yes those would be useful elements to use.

@scottaohara Sorry, I was referring to the HTML 5  and  tags.

I understand.
My response still applies as neither of which are particularly appropriate for this test page, but could be for other uses.

Thanks 🙇
I learned a lot about Semantic HTML from conversation in this PR. 🖊 📚
LGTM 🎉

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


NA OFI: Add support for new tcp provider

With latest Libfabric v1.7.0 a new TCP provider has been introduced. According to the official man pages it should provide better performance with respect to the old sockets provider and in the long term it should replace it completely.
At the moment mercury doesn't expose this provider. Actually if you try to use ofi+tcp, internally mercury will use the old ofi+sockets provider.

That's correct, we haven't enabled it as we need to evaluate which features are supported or missing but I do expect it will replace the sockets provider.

Merged in #282


Box plot: Y axis zoom slider behaviour is inverted

Steps to reproduce:

Open a table
Add both plot
Use Y axis zoom slider

Expected results: Zoom slider behaviour should be consistent with the axis direction.
Actual results: Behaviour of the zoom slider is inverted: dragging its upper end zooms lower values, dragging lower end zooms higher values:

DG 1.15.3


Fixed error wile parsing AMF object.

AMF0_TYPE_OBJECT_END handled incorrectly

Good catch ! Seems like I missed it when cleaning from https://github.com/noirotm/flvmeta/blob/master/src/amf.c#L497
There might be more.


[$500] Request Money - Billable toggle is not enabled by default after setting it up for that

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.91-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:
Pre-requisite: user must be logged in with a collect workspace admin on OD and an employee of the same workspace on ND.

As the admin on OD, go to workspace settings.
Go to "Expenses" tab and change "Re-bill expenses to clients" to "Default to Billable"
As the employee on ND, go to workspace chat.
Initiate a manual money request.
Enter the amount and click on "Next".
Click on "Show more".

Expected Result:
The billable toggle should be enabled by default.
Actual Result:
The billable toggle is disabled by default.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/115492554/6619aa13-57b2-4d6a-97a3-750c2b118ef6

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0194bef3b8abca9d9f
Upwork Job ID:<PHONE_NUMBER>460920832
Last Price Increase: 2023-10-26

Yup, a dupe. Closing this one.


Install nodejs in docker container

so that node/npm packages can be installed downstream to facililate
dependent build pipelines.
We leverage this ability at Stanford.

Thanks for the pull request, @stvstnfrd! I've created OSPR-3716 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams.
Feel free to add as much of the following information to the ticket:

supporting documentation
edx-code email threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will still be done via the GitHub pull request interface. As a reminder, our process documentation is here.

@stvstnfrd Thank you for your contribution. @nedbat Can you give this a look?

@abutterworth @davidjoy @Tj-Tracy Can one of you node-knowledgable weigh in here? I'm not familiar enough with the options.

@nedbat Ping.
At this end of the day, I'll do whatever,  as long as it ends up in a workbench w/ node installed,
so just let me know what you prefer.

@davidjoy Can you weigh in here when you have a chance?

@natabene Requested changes have been made. I'll squash commits prior to merge.

@stvstnfrd Please squash and we will merge.


getting doc nbs to work

The docs/*ipynb notebooks aren't working out of the box. I needed to add:
import os, sys
path = os.path.realpath('.')
sys.path.append(path+ "/gen_doc")
from nbdoc import *

base = path+"/../" # root of fastai_v1
sys.path.append(base)
#print(sys.path)

# this is needed to get the sub-packages to load
!touch {base}"__init__.py"
!touch {base}"fastai_v1.py"
!ln -fs {base}"dev_nb" {base}"fastai_v1"
!touch {base}"fastai_v1/__init__.py"

perhaps this can be done behind the scenes?
I needed to get it working as I'm experimenting with a faster stripout process.
Also in docs/fastai_v1.nb_001b.ipynb:
show_doc_from_name('fastai_v1.nb_001b','DeviceDataLoader.progress_func')
Class DeviceDataLoader doesn't have a function named progress_func.

Yeah, like I said in the doc, for now you need to have:

the nbdoc.py file in the folder of your notebooks,
a simlink to the package folder you want to document in the folder of your notebooks.
I did this for the example folder (don't know if the simlink will work for everyone since it's a windows one), didn't try for fastai_v1 yet since we don't have a real module.

I think you should stick to the documentation notebooks for now (so the ones in example/) the fastai ones were early examples, and I should probably delete them.

Perfect, thank you for telling me which doc notebooks I can experiment with, @sgugger.
This one fails too:
http://localhost:8889/notebooks/br/fastai/master/docs/example/notebook_documentation.ipynb
in the last cell:
from gen_doc.convert2html import convert_nb
convert_nb('gen_doc.nbdoc.ipynb')
---------------------------------------------------------------------------
TemplateNotFound                          Traceback (most recent call last)
<ipython-input-8-9a90b9b678a5> in <module>()
      1 from gen_doc.convert2html import convert_nb
----> 2 convert_nb('gen_doc.nbdoc.ipynb')

/mnt/disc1/fast.ai-1/br/fastai/master/docs/example/gen_doc/convert2html.py in convert_nb(fname)
     36     new_name = re.sub(r"(.*)\.ipynb",r"\1.html",str(fname))
     37     with open(new_name,'w') as f:
---> 38         f.write(exporter.from_notebook_node(nb)[0])
     39
     40 def convert_all(folder):

~/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/nbconvert/exporters/html.py in from_notebook_node(self, nb, resources, **kw)
     83         self.register_filter('highlight_code',
     84                              Highlight2HTML(pygments_lexer=lexer, parent=self))
---> 85         return super(HTMLExporter, self).from_notebook_node(nb, resources, **kw)

~/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/nbconvert/exporters/templateexporter.py in from_notebook_node(self, nb, resources, **kw)
    293
    294         # Top level variables are passed to the template_exporter here.
--> 295         output = self.template.render(nb=nb_copy, resources=resources)
    296         return output, resources
    297

~/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/nbconvert/exporters/templateexporter.py in template(self)
    109     def template(self):
    110         if self._template_cached is None:
--> 111             self._template_cached = self._load_template()
    112         return self._template_cached
    113

~/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/nbconvert/exporters/templateexporter.py in _load_template(self)
    264         self.log.debug("Attempting to load template %s", template_file)
    265         self.log.debug("    template_path: %s", os.pathsep.join(self.template_path))
--> 266         return self.environment.get_template(template_file)
    267
    268     def from_notebook_node(self, nb, resources=None, **kw):

~/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/jinja2/environment.py in get_template(self, name, parent, globals)
    828         if parent is not None:
    829             name = self.join_path(name, parent)
--> 830         return self._load_template(name, self.make_globals(globals))
    831
    832     @internalcode

~/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/jinja2/environment.py in _load_template(self, name, globals)
    802                                          template.is_up_to_date):
    803                 return template
--> 804         template = self.loader.load(self, name, globals)
    805         if self.cache is not None:
    806             self.cache[cache_key] = template

~/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/jinja2/loaders.py in load(self, environment, name, globals)
    406             except TemplateNotFound:
    407                 pass
--> 408         raise TemplateNotFound(name)
    409
    410     def list_templates(self):

TemplateNotFound: nbextensions.tpl

I do have the template here:
/home/stas/anaconda3/envs/pytorch-dev/lib/python3.6/site-packages/jupyter_contrib_nbextensions/templates/nbextensions.tpl
And I have everything installed as the doc suggested.
Thanks.

perfect - it set \ when we need / on unix, fixed:
https://github.com/fastai/fastai_v1/commit/bf88b9a0f02b380c7918188f6b755e98e95eb896
thanks for your support, @sgugger

Ah, sorry about that. Will keep in mind to use Pathlib or os.path.join in the future.


test file naming convention

We have a mix of different naming conventions for test code and I find it makes it really hard to navigate using Go-to-file. And it's sometimes confusing that, for example, namespaces.ts doesn't implement anything about namespaces, it tests them. Yes, the folder tells you, but like I said, go-to-file experience is annoying. We have a lot of test-.ts, but we're inconsistent. I propose that we use test-.ts throughout. We also have some casing differences that we might as well sort out at the same time, I think.

yeah I agree that having some differentiator would be a good idea. I personally like the .test.ts suffix. This is the pattern used a lot of the JS/TS world(That or .spec.ts). But if we prefer test- I'll live :)

That's fine with me too, I just picked something we already had in a bunch of places. I'm easily convinced as long as there's some differentiator :)

I prefer .test to .spec though. .spec seems unnecessarily technical and unclear IMHO, but I know it's common in JS community.

Yeah, fine with either, using .test.ts with autorest. Used to do .spec.ts for previous projects as it goes with the behavior testing naming of describe, it , expect


Rack explosions have no visual effect.

This happens a lot with ACF explosions unless they're done /exactly/ right.  Unfortunately, I don't know what 'exactly right' actually is.  When a rack is shot and explodes, the damage is still dealt but there's no smoke.

Not exactly a priority / important bug, imo. Iirc grenades, mines and satchel charges had the same issue before, was it a similar problem?

seems this happend only on carcon map (cre8ve main map) - on other seems works fine... still needs more testing to be sure

I can confirm that this has also happened on gm_construct_flatgrass_v6.

When rack explosions are invisible, are any of the other ACF effects also invisible?  This means tracers, smoke from smoke launchers, tank shell explosions...?

In my case, all effects were visible except for the detonation of the rack.


SVG is wider than the line

Hey, thanks for the library!
I am having a small problem where the rendered SVGs are wider than the leader lines.
For example, this is the SVG size of the diagonal line:

Another example with a short line:

I'd love some help with this as it is adding scrollbars to my page.

Hi @ofir-o, thank you for the comment.
The SVG element needs the size to draw the line that contains the path (cubic curve and its segments), mask, anchor, etc.
You can change the path for the size of the SVG. For example: https://jsfiddle.net/Lj0m5egb/


Landing Page and ART search issue

During this morning call, we were looking for a GO-term in ART. We noticed the number of results was 128 but ART was showing only 2 results. Same behavior on the noctua landing page (see update below).
After checking the API calls:

Query 1: http://barista-dev.berkeleybop.org/search//models?offset=0&limit=50&term=GO:0036498&expand&count
Query 2: http://barista-dev.berkeleybop.org/search//models?offset=0&limit=150&term=GO:0036498&expand

It appears the API is indeed returning (at least) 128 models. In effect, the second query seems to indicate even more (around 150) but possibly there was some redundancy in the various matches and this hopefully goes down to 128. Possibly NLP and ART are only using one of the models field, but not all ?
Action items (see update below)

[ ] make sure both ART and NLP are using the full list of models from the API query 2 (e.g. models[0].query_match, ... models[x].query_match etc)
[ ] double check the full concatenated list of matching models, and once duplicates are removed, hopefully confirm that we do have 128 models; if we don't, this would indicate a bug at the API level
[ ] @vanaukenk @ukemi confirm this is working on this case (GO:0036498) on both NLP and ART; try to double check on some other random search

After the merge, now the results are not sorted by date DESC. I think now its hard to find models for recent @balhoff @lpalbou


Bug in the Datasmith Export of animation to Unreal

As confirmed by @MichaelBelousov there is a bug in the export of the itwin animation as a combined mesh.
It doesnt export growth simulations correctly as described and shown in the discussion:
https://github.com/iTwin/itwinjs-core/discussions/4599

We launched the iTwin Exporter for Datasmith last year as a Technology Preview; we received great feedback from early adopters. One of the most significant drawbacks of the iTwin Exporter for Datasmith that we received feedback about was that the file format is unsuitable for large-scale infrastructure projects. One of the core tenets of the iTwin Platform is scalable support for large-scale modern infrastructure projects. With this limitation identified, we have developed the 3DFT technology, which supports large-scale infrastructure model streaming in Unreal Engine.
To get started with 3DFT, register an application on the iTwin Platform by following these steps.
You can get more information about how to load your iTwin in Unreal at our Unreal plugin's page


remove "appSettings": [{"href": "#"}], from apptop_signin_custommenu-en.shtml

Moved from GCCode: https://gccode.ssc-spc.gc.ca/iitb-dgiit/nw-ws/sgdc-cdts/issues/104
@StdGit created the issue
"appSettings": [{"href": "#"}],
https://ssl-templates.services.gc.ca/app/cls/WET/gcintranet/v4_0_31/cdts/appTop/apptop_signin_custommenu-en.shtml

@shawnthompson commented:
@StdGit Why would we want to do this? Don't we need the "appSettings": [{"href": "#"}] in the example?

@MaximMartel Could you confirm this issue is still valid for version 4.0.39 ? Thanks.

@StdGit Can we get more details for this issue?

@StdGit Can we get more details for this issue?

All samples were revamped which addresses this issue. Closing.


Update / Create docs for onboarding fix-team members to HackerOne

There is a useful HackerOne feature where folks can be granted access to just one specific H1 issue, which can be useful when members of a fix team are highly involved in the response process.
To ensure this is done consistently and fix-team members are well-supported, let's create some docs for how to do it right.

Is this issue still active?


support for material-ui v5

Is this project working on supporting material-ui v5? I feel the only change would be to update dependencies. It shouldn't impact the actual code.

Hi @MridulaKamath I will cap the version to v4 on the current major and then release an update that requires v5. I am sure there will be some slight changes and don't want those to affect existing v4 users. I am just waiting for it to hit release candidate

Also there are breaking changes. Some components moved from labs to core.

@cliedeman Thanks for the quick reply. I forgot that the pickers did get moved.
I'll be closing this, as I've received an answer to my question. Thanks!


Proof unable to sort old dataset

Versions
GRSISort: v<IP_ADDRESS>
ROOT: 6.14/06
OS: centos 7
Bug Description
I am analyzing a GRIFFIN dataset taken in Sept. 2019 using a pre-existing selector. This dataset was analyzed as part of C.Porzio's Ph.D so everything should be working but I am unable to consistently sort the analysis trees. I installed the same versions of ROOT and GRSISort on a different host and upon running the proof session via:
grsiproof ../data/analysis-trees/analysis14660_000.root selectors/S1716Sept2019Selector.C
I get the following errors
************************* END COMPILATION ******************************
 +++ Starting PROOF-Lite with 8 workers +++
Opening connections to workers: OK (8 workers)
Setting up worker servers: OK (8 workers)
PROOF set to parallel mode (8 workers)
Loading Libraries
Reading TGRSIRunInfo from file "../data/analysis-trees/analysis14660_000.root"
Read singleton 0x5631f963e880 from ../data/analysis-trees/analysis14660_000.root
Title: 72 Ga beam
Comment: 72Ga beam - implantation
		RunNumber:          14660
		SubRunNumber:       000
		RunStart:           Mon Sep 30 14:25:58 2019
		RunStop:            Mon Sep 30 14:47:22 2019
		RunLength:          1284 s
../data/analysis-trees/analysis14660_000.root: adding ppg
Currently Running: selectors/S1716Sept2019Selector.C

Info in <TProofLite::SetQueryRunning>: starting query: 1
Info in <TProofQueryResult::SetRunning>: nwrks: 8
Error in <TApplication::ProcessLine>: macro selectors/S1716Sept2019Selector.C not found in path selectors:/home/vagrant/grsi-group/v<IP_ADDRESS>/GRSISort/myAnalysis
Looking up for exact location of files: OK (1 files)
Looking up for exact location of files: OK (1 files)
Info in <TPacketizer::TPacketizer>: Initial number of workers: 8
Validating files: OK (1 files)
0.1: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
0.2: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>: 02 events	|>...................| 0.00 %
 +++ Message from master at mass72 : marking mass72:-1 (0.1) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at mass72 : marking mass72:-1 (0.1) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("mass72")->GetSessionLogs()->Display("*")

Info in <TProofLite::MarkBad>: 02 events	|>...................| 0.00 %
 +++ Message from master at mass72 : marking mass72:-1 (0.2) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at mass72 : marking mass72:-1 (0.2) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("mass72")->GetSessionLogs()->Display("*")

Info in <TProofLite::MarkBad>: 02 events	|>...................| 0.00 %
 +++ Message from master at mass72 : marking mass72:-1 (0.4) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at mass72 : marking mass72:-1 (0.4) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("mass72")->GetSessionLogs()->Display("*")

0.3: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
0.5: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>: 02 events	|>...................| 0.00 %
 +++ Message from master at mass72 : marking mass72:-1 (0.3) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at mass72 : marking mass72:-1 (0.3) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("mass72")->GetSessionLogs()->Display("*")

Info in <TProofLite::MarkBad>: 02 events	|>...................| 0.00 %
 +++ Message from master at mass72 : marking mass72:-1 (0.5) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at mass72 : marking mass72:-1 (0.5) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("mass72")->GetSessionLogs()->Display("*")

[TProof::Progress] Total 37289002 events	|>...................| 0.00 %

Whereupon the terminal instance locks up and freezes. The only way I can recover is to forcibly kill the running instance of proof through another terminal session.
I get a similar error when running the code with the most up-to-date version of GRSISort and root. Are there any changes I need to make to an old selector to have it run on a modern version of GRSISort? I suspect part of the locking up is the memory leak issue from v3.X so the modern versions shouldn't have that issue.
Another Example of Issue
Using the same host as Carlotta and the exact installs I am able to sort the first subrun in the run, albeit with many error messages, but am not able to sort any of the other subruns. The output for the third subrun follows:
************************* MACRO COMPILATION ****************************
************************* END COMPILATION ******************************
 +++ Starting PROOF-Lite with 8 workers +++
Opening connections to workers: OK (8 workers)
Setting up worker servers: OK (8 workers)
PROOF set to parallel mode (8 workers)
Loading Libraries
Reading TGRSIRunInfo from file "../data/analysis-trees/analysis14660_002.root"
Read singleton 0x5c20860 from ../data/analysis-trees/analysis14660_002.root
Title: 72 Ga beam
Comment: 72Ga beam - implantation
		RunNumber:          14660
		SubRunNumber:       002
		RunStart:           Mon Sep 30 07:57:23 2019
		RunStop:            Mon Sep 30 08:01:25 2019
		RunLength:          242 s
../data/analysis-trees/analysis14660_002.root: adding ppg
Currently Running: selectors/S1716Sept2019Selector.C

Info in <TProofLite::SetQueryRunning>: starting query: 1
Info in <TProofQueryResult::SetRunning>: nwrks: 8
Error in <TApplication::ProcessLine>: macro selectors/S1716Sept2019Selector.C not found in path selectors:/home/cporzio/GRSISort/myAnalysis
Looking up for exact location of files: OK (1 files)
Looking up for exact location of files: OK (1 files)
Info in <TPacketizer::TPacketizer>: Initial number of workers: 8
Validating files: OK (1 files)
0.0: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>: 80 events	|>...................| 0.00 %
 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.0) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.0) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("megalania.triumf.ca")->GetSessionLogs()->Display("*")

0.7: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>: 80 events	|>...................| 0.00 %
 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.7) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.7) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("megalania.triumf.ca")->GetSessionLogs()->Display("*")

0.5: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>:
 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.5) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.5) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("megalania.triumf.ca")->GetSessionLogs()->Display("*")

0.6: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>:
 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.6) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.6) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("megalania.triumf.ca")->GetSessionLogs()->Display("*")

0.2: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>: 80 events	|>...................| 0.00 %
 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.2) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.2) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("megalania.triumf.ca")->GetSessionLogs()->Display("*")

0.1: caught exception 'bad_alloc' (memory leak?) <undef> -1..........| 0.00 %
Info in <TProofLite::MarkBad>:
 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.1) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.1) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("megalania.triumf.ca")->GetSessionLogs()->Display("*")

Info in <TProofLite::MarkBad>: 80 events	|>...................| 0.00 %
 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.3) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Message from master at megalania.triumf.ca : marking megalania:-1 (0.3) as bad
 +++ Reason: undefined message in TProof::CollectInputFrom(...)

 +++ Most likely your code crashed
 +++ Please check the session logs for error messages either using
 +++ the 'Show logs' button or executing
 +++
 +++ root [] TProof::Mgr("megalania.triumf.ca")->GetSessionLogs()->Display("*")

terminate called after throwing an instance of 'std::bad_alloc'=====>| 99.38 % [74014.3 evts/s, 8.4 MB/s, time left: 1.3 s]]]]
  what():  std::bad_alloc

No output file was written for this subrun. I tried cleaning all instances of proofserv and rerunning the sort but that did not change the outcome.
Is there anything else I should look at? Otherwise I am not sure how to approach this issue.

Did you get any grsisort.log output file or other log files written? What is in the files in $HOME/.proof/whatever-path-your-running-this-in/session-host-numbers/worker-0.0.log?
It seems that in both cases it's a bad_alloc that's crashing the selectors. So for some reason a memory allocation failed. Could this be a memory issue? Have you checked the output of top in another console/terminal while you're running this selector?

Using v3 of GRSISort:
What is in the files in $HOME/.proof/whatever-path-your-running-this-in/session-host-numbers/worker-0.0.log?
When the subrun sorts this is the file:
17:15:07  3528 Wrk-0.0 | Info in <TProofServLite::Setup>: fWorkDir: /home/vagrant/.proof
17:15:07  3528 Wrk-0.0 | Info in <TProofServLite::SetupCommon>:  0 global package directories registered
17:15:08  3528 Wrk-0.0 | Info in <TProofServLite::HandleProcess>: calling fPlayer->Process() with selector name: S1716Sept2019Selector.C+
17:19:27  3528 Wrk-0.0 | Info in <TProofPlayerSlave::AssertSelector>: Processing via filename (S1716Sept2019Selector.C+)
17:19:27  3528 Wrk-0.0 | Info in <TEventIter::TEventIter>: fPackets list 'ProcessedPackets_0.0' created
17:19:27  3528 Wrk-0.0 | Info in <TProofPlayerSlave::Process>: save partial results? 0  per-packet? 0
input list size = 8
FeedbackList: Collection name='FeedbackList', class='TList', size=0
TAnalysisOptions: ^[[1;34mfBuildWindow: ^[[0;36m200
^[[1;34mfAddbackWindow: ^[[0;36m300
^[[1;34mfSuppressionWindow: ^[[0;36m300
^[[1;34mfSuppressionEnergy: ^[[0;36m0
^[[1;34mfStaticWindow: ^[[0;36m0
^[[1;34mfWaveformFitting: ^[[0;36m0
^[[1;34mfIsCorrectingCrossTalk: ^[[0;36m0
^[[m
pwd: OBJ: TNamed        pwd     /vagrant/analysis
TPPG: ODB cycle:
Code       Duration
Empty
PROOF_MaxSlavesPerNode: TParameter<long>        PROOF_MaxSlavesPerNode = 0
PROOF_QueryTag: OBJ: TNamed     PROOF_QueryTag  mass72-1668014106-3499
PROOF_QuerySeqNum: TParameter<int>      PROOF_QuerySeqNum = 1
PROOF_Ordinal: OBJ: TNamed      PROOF_Ordinal   0.0
No g-values!creating histograms ...
done
17:19:31  3528 Wrk-0.0 | SvcMsg in <TProofPlayerSlave::CheckMemUsage>: Memory 14486608 virtual 14289140 resident event 0
17:19:35  3528 Wrk-0.0 | Info in <TEventIterTree::GetTrees>: the tree cache is in learning phase
17:19:36  3528 Wrk-0.0 | Error in <TTree::SetBranchAddress>: unknown branch -> TSceptar
Starting to sort: /vagrant/analysis/../data/analysis-trees/analysis14660_000.root
17:19:36  3528 Wrk-0.0 | Info in <TProofServLite::RestartComputeTime>: compute time restarted after 0.862234 secs (100 entries)
17:29:46  3528 Wrk-0.0 | SvcMsg in <TProofPlayerSlave::CheckMemUsage>: Memory 14563648 virtual 13594908 resident event 37289002
Successfully read 502 TChannels from^[[1;36m /vagrant/analysis/../data/analysis-trees/analysis14660_000.root^[[m

^[[1mRooFit v3.60 -- Developed by Wouter Verkerke and David Kirkby^[[0m
                Copyright (C) 2000-2013 NIKHEF, University of California & Stanford University
                All rights reserved, please read http://roofit.sourceforge.net/license.txt

17:30:24  3528 Wrk-0.0 | Error in <TProofServLite::HandleSocketInput>: caught exception 'bad_alloc' (memory leak?) while processing dset:'TDSet:AnalysisTree', file:'/vagrant/analysis/../data/analysis-trees/analysis14660_000.root' - check logs for possible stacktrace - last event: 37289001
17:30:24  3528 Wrk-0.0 | Info in <TProofServLite::Terminate>: starting session termination operations ...
17:30:24  3528 Wrk-0.0 | Info in <TProofServLite::Terminate>: data directory '/home/vagrant/.proof/data/0.0/0.0-mass72-1668014107-3528' has been removed
Terminate: termination operations ended: quitting!

Could this be a memory issue? Have you checked the output of top in another console/terminal while you're running this selector?
I watched top while this was running and proof used 90% of the available memory and 95% of the available CPU.

Using v4 of GRSISort:
There are more errors in the selector compilation:

Warning in <TStreamerInfo::CompareContent>: The following data member of
the in-memory layout version 5 of class 'TGriffin' is missing from
the on-file layout version 5:
   vector<TGriffinHit> fGriffinLowGainHits; //
Warning in <TStreamerInfo::CompareContent>: The following data member of
the in-memory layout version 5 of class 'TGriffin' is missing from
the on-file layout version 5:
   vector<TGriffinHit> fGriffinHighGainHits; //
Warning in <TStreamerInfo::CompareContent>: The following data member of
the in-memory layout version 5 of class 'TGriffin' is missing from
the on-file layout version 5:
   TTransientBits<unsigned char> fGriffinBits; //
Warning in <TStreamerInfo::CompareContent>: The following data member of
the in-memory layout version 5 of class 'TGriffin' is missing from
the on-file layout version 5:
   vector<TGriffinHit> fSuppressedLowGainHits; //
Warning in <TStreamerInfo::CompareContent>: The following data member of
the in-memory layout version 5 of class 'TGriffin' is missing from
the on-file layout version 5:
   vector<TGriffinHit> fSuppressedHighGainHits; //
Warning in <TStreamerInfo::BuildCheck>:
   The StreamerInfo of class TSuppressed read from file ../data/analysis-trees/analysis14660_000.root
   has the same version (=1) as the active class but a different checksum.
   You should update the version to ClassDef(TSuppressed,2).
   Do not try to write objects with the current class definition,
   the files will not be readable.

And the memory usage increases to 97%, and the terminal session locks up. I suspect the selector is incompatible with v4.

So these warning are about the incompatibility of the analysis root-file with the newer version. Essentially the data members of the TGriffin and TGriffinHit classes have changed and now ROOT/GRSISort doesn't know how to read everything.
The 97% memory usage definitely point to an issue with the size of everything used in the selector. How many workers are you running? And how big are the histograms in the selector? For a test I would reduce all bins by a factor 10, and see if that makes it work.

So these warning are about the incompatibility of the analysis root-file with the newer version. Essentially the data members of the TGriffin and TGriffinHit classes have changed and now ROOT/GRSISort doesn't know how to read everything.

I unpacked the MIDAS files again with the current version of GRSISort and everything worked. Thanks.

How many workers are you running? And how big are the histograms in the selector?

I was running 6 workers and the histograms were 8k bins. I decreased the size and moved the computation to a host with more memory. I still get errors once everything finishes but the output file looks fine. I think I was running out of system memory which caused many issues.

Okay, sounds like you solved the problem.


Implement Series.copy

Implement Series.copy and add Examples to Frame.copy also
>>> s = ks.Series([1, 2], index=["a", "b"])
>>> s
a    1
b    2
Name: 0, dtype: int64
>>> s_copy = s.copy()
>>> s_copy
a    1
b    2
Name: 0, dtype: int64

Codecov Report

Merging #869 into master will decrease coverage by 2.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #869      +/-   ##
==========================================
- Coverage   94.27%   92.11%   -2.16%
==========================================
  Files          34       34
  Lines        6201     6202       +1
==========================================
- Hits         5846     5713     -133
- Misses        355      489     +134

Impacted Files
Coverage Δ

databricks/koalas/missing/series.py
100% <ø> (ø)
:arrow_up:

databricks/koalas/frame.py
94.36% <ø> (-1.59%)
:arrow_down:

databricks/koalas/series.py
95.18% <100%> (-0.15%)
:arrow_down:

databricks/koalas/usage_logging/__init__.py
24.54% <0%> (-72.73%)
:arrow_down:

databricks/koalas/usage_logging/usage_logger.py
50% <0%> (-50%)
:arrow_down:

databricks/koalas/__init__.py
77.5% <0%> (-7.5%)
:arrow_down:

databricks/conftest.py
91.48% <0%> (-6.39%)
:arrow_down:

databricks/koalas/namespace.py
85.01% <0%> (-1.31%)
:arrow_down:

databricks/koalas/plot.py
93.33% <0%> (-0.96%)
:arrow_down:

... and 3 more

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 a05cb46...ddcff79. Read the comment docs.

Thanks! merging.

@ueshin Thanks :)


Create up.txt

:pray:

Here's official website of the University: http://up.wroc.pl/en/

@tomwyr Pull request merged. Thank you!


Display gradient in elevation profile

Hi!
I have a suggestion for a feature that I consider would be very useful.
When evaluating some tracks I like to see the gradient to get an idea of how hard it will be. Using the current elevation profile sometimes hard to get a good idea of how steep the track is.
My suggestion is to add a new mode to the elevation profile with colors based on the gradient, similar to the output generated at https://www.trackreport.net/

Hi, at the bottom right of the elevation profile, there is a button to change from surface data to slope data. Have you tried it? I plan to further improve this soon.

I spent some time trying to find something like this, and I searched the docs too, but I couldn't find it.
This is what I what I was looking for! thanks!


A11y_AzureDataStudio_Delete connection_Usability:Once connection is deleted the Deletion status message is not announced by screen reader

GitHub Tags:
#A11yusable; #A11yTCS; #A11ySev4; #DesktopApp; #BM-AzureDataStudio-Win32-Feb2022; #Azure Data Studio; #Win32;  #NVDA; #Screen Reader; #Benchmark; #JAWS;
Environment and OS details:
Azure Data Studio Version: 1.42.0 (user setup)
Windows 11 Enterprise Version	22H2
Installed on	28-12-2022
OS build	22621.1413
Experience	Windows Feature Experience Pack 1000.22639.1000.0
NVDA Version 2023.1
JAWS Version 2023
Pre-Requisite:

Install Azure data studio From here https://learn.microsoft.com/en-us/sql/azure-data-studio/download-azure-data-studio?view=sql-server-ver16&tabs=redhat-install%2Credhat-uninstall
Once installation done , Install MySQL Extension in Azure data studio
Tab Till  new connection and press enter
Enter a valid server name username and password and press connect

Repro Steps:

Launch Azure Data Studio. and Turn on nVDA
Select the Connections icon (if not already selected) from left bar.
Right click on any of the servers from the Servers viewlet and select "Delete connection"
The selected connection should be deleted
5.Verify that once connection is deleted the status is announced by screen reader or not

Actual Result:
Once connection is deleted the Deletion status message is not announced by screen reader
Issue repro with JAWS
Expected Result:
NVDA should announce Deletion status message.
Attachment:

Primary bug:https://github.com/microsoft/azuredatastudio-mysql/issues/193


[Bug]: S220 Solocam does not stream to home-app

What happened?
I cannot view any livestream in the Home app.
After a view minutes "No response" appears and nothing happens.
Sometimes a snapshot from a view days ago appears, but in front of this is a banner with „Camera is not responding“.

Device Type
Station (Supported)
Plugin Version
beta (Best Effort)
HomeBridge Version
v1.6.x (Supported)
NodeJS Version
v18 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
[11/24/2023, 12:03:59]  [EufySecurity]  INFO    Carport station livestream (P2P session) for Carport has started.
[11/24/2023, 12:03:59]  [EufySecurity]  INFO    Carport station livestream for Carport has stopped.

config
{
    "platform": "EufySecurity",
    "ignoreStations": [],
    "ignoreDevices": [],
    "cleanCache": true,
    "username": "****",
    "password": "****",
    "country": "DE",
    "deviceName": "",
    "_bridge": {
        "username": "0E:C0:AB:19:4B:3A",
        "port": 38360
    }
}

I have the exact same issue.

Now works with the newest v2.3.9 - hksv Version


[@rancher/components] add docs on how to build and release the shared lib

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Duplicates #5930


random browser version doesn't match actual one

This is the code I'm using:
ua = ua_generator.generate(platform = 'windows', browser = 'chrome')
ua.headers.accept_ch('Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List')
driver.execute_cdp_cmd('Network.setExtraHTTPHeaders', {'headers': ua.headers.get()})

But this creates a problem and mismatch between the generated browser version and the actual one. This makes the package practically unusable.  You can see in the example that the generator made Chrome to be of version 95, but the actual version is 124. I'm not sure how to fix this. your generator should be aware of the real browser version and generate matching strings. Otherwise this creates a mismatch that can be easily detected.

Hello,
I don't know which client you are using, but I can say that this issue is not caused by the library. Based on my tests, the values generated by the ClientHints and Headers classes seem consistent. The ua-generator only produces strings and cannot affect the Client Hints values obtained from JavaScript environments (as mentioned in the image).
Additionally, the "Sec-CH-UA-Full-Version" header is not generated by this library. It has been deprecated by the W3C and replaced with "Sec-CH-UA-Full-Version-List". You need to manually set the "Sec-CH-UA-Full-Version".

I'm using Chrome and you can see that in the headers. The values that ua generates are consistent and this isn't my point.
My point is that applying everything to the headers and UA creates an inconsistent result bc Chrome reveals its real version when asked and through JS and the bottom line is an inconsistent results that defeats the purpose. If I do that I'm going to be blocked at once detected as a bot. The main question is - how to make sent fields consistent using the package? the example I sent was created by https://browserleaks.com/client-hints where I tested the sent results and revealed the mismatch. The question is how can we fix this?

I'm using Chrome and you can see that in the headers. The values that ua generates are consistent and this isn't my point. My point is that applying everything to the headers and UA creates an inconsistent result bc Chrome reveals its real version when asked and through JS and the bottom line is an inconsistent results that defeats the purpose. If I do that I'm going to be blocked at once detected as a bot. The main question is - how to make sent fields consistent using the package? the example I sent was created by https://browserleaks.com/client-hints where I tested the sent results and revealed the mismatch. The question is how can we fix this?

Hello,
Starting from version 0.5.0, the functions that provide raw Client Hints values have been made public. Now, you can set the Client Hints values from clients like Selenium. However, you need to update the ua-generator first.
I tested it, and it worked.
ua = ua_generator.generate(platform='windows', browser='chrome')
driver = webdriver.Chrome()
driver.execute_cdp_cmd('Network.setUserAgentOverride', {
    'userAgent': ua.text,
    'userAgentMetadata': {
        'brands': ua.ch.get_brands(),
        'fullVersionList': ua.ch.get_brands(full_version_list=True),
        'fullVersion': ua.ch.get_browser_version(),
        'platform': ua.ch.get_platform(),
        'platformVersion': ua.ch.get_platform_version(),
        'architecture': ua.ch.get_architecture(),
        'model': ua.ch.get_model(),
        'mobile': ua.ch.get_mobile(),
        'bitness': ua.ch.get_bitness(),
        'wow64': ua.ch.get_wow64(),
    }
})

perfect! now everything is consistent

I'm glad to hear that. Well, closing then.

I actually have one small request. 99% of Chrome versions vary today between 120-124, but you choose a random equally from 90-124 (see below).  So will you be able to either get rid of anything below 120 or even better, give a min-max range to choose from? this way you'll just generate a random between desired versions. This will also spare the need to update your package all the time since right now you have to choice about Chrome version changes if they release 125 and so on.

I actually have one small request. 99% of Chrome versions vary today between 120-124, but you choose a random equally from 90-124 (see below). So will you be able to either get rid of anything below 120 or even better, give the caller a min-max range to choose from? this way you'll just generate a random between desired versions. This will also spare the need to update your package all the time since right now you have to choice about Chrome version changes if they release 125 and so on.

The main purpose of creating this library was actually to generate valid user-agent values. The versions were not of much importance. However, it would really be nice if the version customization could be implemented. There is already another request (#6) regarding the customization of versions, but I haven't had the time to address it.

"The main purpose of creating this library was actually to generate valid user-agent values"
well "valid" doesn't mean that you simply pick random figures without considering reality. And if the reality is that 99% of Chrome versions are > 120, then you cannot by all means choose version 90 as probability equal to 124, but this is what happens today. I think that if you want a quick and dirty solution - but still better than today - simply release a version with only versions 120-124.
As for other fields, I think over there is the same story. 95% of all Windows are > version 10, so you cannot pick version 6 or 6.1 equally as the others, but this is again what's happening today. Same thing with WOW64 which is almost nonexistent. So I do believe to turn the package from a toy to something which can be used in production code, these changes are necessary and in fact not difficult to make. For example you can easily add weights (=percentages) to all the versions you have and when you pick a random figure their weights are taken into account for example:
def getWeightedValueFrom(list):
      return random.choices([pair[0] for pair in list], weights = [pair[1] for pair in list], k = 1)

Thank you for your suggestions. I will consider them next time.

I understand the option to select a range of versions. But I don't get why you would want weighted values. Isn't the point of the random generator to uniformly generate all possible combinations of browser, device, platform? Maybe its because what I'm thinking is when you're webscraping you want to spread out your ua usages linearly as your number of queries increases, and not have a couple that are used in high frequency. @iamdual

I understand the option to select a range of versions. But I don't get why you would want weighted values. Isn't the point of the random generator to uniformly generate all possible combinations of browser, device, platform, version? Maybe its because what I'm thinking is when you're webscraping you want to spread out your ua usages linearly as your number of queries increases, and not have a couple that are used in high frequency to avoid being blocked @iamdual

Yes, I agree, but it is also true that the usage rate of the latest versions is higher than the others. However, I would like to remind you that this feature is completely optional.


A operator can overflow into non base36 numbers

Using the A operator passing Z and anything greater than 1 can produce midi, udp, comment or door operators; adding 6 to Z produces a 0, is this a bug ?
It produces some intresting results, but I'm not sure if this is intentional or not ?

overflow.orca.txt

I guess I didn't think it a problem, but with :, and ; locking ports, I've decided to limit to y, z, *, a, b... So Az1 = * and Az2 = a

Thanks, it feels better having A only produce valid numerical outputs.


Improved LALR conflict reporting code

This patch fixes "shift/reduce conflict" message printed when there is in fact reduce/reduce conflict. It also adds some
code comments and pulls message constructing code into separate function.

No, you can't just ignore reduce/reduce errors, you have to fail with an exception.


BUG: stable docs has incorrect version number

Same issue as https://github.com/astropy/specutils/issues/1092, I suspect there is a shallow clone somewhere that trips over the version number generation

That was fixed a while ago in https://github.com/astropy/regions/pull/514.  I just need to make a new release.  I'll probably do that very soon so there will also be Python 3.12 wheels.

Version 0.8 and this is fixed:
https://astropy-regions.readthedocs.io/en/stable/


Textures missing on iOS in HTML5 export

Godot version: 3.1.2.stable on macOS 14.6
OS/device including version: iOS 13.3 (iPhone XR, iPad 2018). Also reported on Android, but I have no details there.
Issue description: A MeshInstance with a SpatialMaterial and an albedo texture renders fine in desktop browsers, but with a missing texture on iOS Safari.
Steps to reproduce: Create a MeshInstance with a texture, add a light and a camera. Export as HTML5. Test on iOS. Or look at the demo: https://combatwombat.github.io/godot-texture-test/
Minimal reproduction project: https://github.com/combatwombat/godot-texture-test

I am running with the same problem and seems to I found something. Try to import texture in different preset mode
(there are 4 presets available)

For me it works well with:

2D, Detect 3D
2D

Probably 2D Pixel may works as well, but for me it sometimes does not work.
Read about importing textures: https://docs.godotengine.org/en/3.1/getting_started/workflow/assets/importing_images.html

I don’t see a problem using iPhone XS Max iOS 13.3

Ha, reimporting as "2D" worked, thanks @Ajver :)
It's still a bug I think but at least there's a workaround.

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?

Can anyone still reproduce this bug in Godot 3.2.3 or any later release?

Yes, (above is iOS 14.2 on iPhone 7, below is firefox)

@kquote03 @combatwombat Can you reproduce this if you keep the default texture import settings but change Compress from VRAM Compressed to Lossless? We need to pinpoint the exact setting which causes this bug.

I changed this setting as instructed , then deleted the model and material file in my project, dragged and dropped the glb file into the godot project. Sadly this made no effect

@kquote03 @combatwombat Can you reproduce this if you keep the default texture import settings but change Compress from VRAM Compressed to Lossless? We need to pinpoint the exact setting which causes this bug.

For reference here's what it should look like:

Btw I tried the godot texture test website linked in the original comment, and for some reason it worked for me

Maybe it's a separate issue?

I changed this setting as instructed , then deleted the model and material file in my project, dragged and dropped the glb file into the godot project. Sadly this made no effect

You changed the Texture3D import default, which is used for 3D textures. Instead, you should have changed the import default on Texture2D or ImageTexture. A Texture3D is not a 2D texture applied on a 3D surface. It's a texture with actual 3-dimensional data (which you can view as a set of 2D texture layers).

@Calinou Yeah I had a feeling I did something wrong, anyways I went and checked the texture import settings and it was already on lossless. Image and Bitmap import settings dont have a compression option

@Calinou Yeah I had a feeling I did something wrong, anyways I went and checked the texture import settings and it was already on lossless. Image and Bitmap import settings dont have a compression option

The Texture import defaults don't reflect flags that are automatically chosen when the texture is detected to be used in a 3D context. To force lossless compression on a texture used in a 3D context, you need to select it in the FileSystem dock and change its options in the Import dock.

I think the issue with older iphones is from using the sRGB option. sRGB should be diasbled and detect 3D should be turned off. This is why the 2D import default tends to work on these devices as well.

@Calinou Alright I re-exported the model from blender in the collada format and re-imported using the following settings:

Sadly it made no change on my iPhone

I think the issue with older iphones is from using the sRGB option. sRGB should be diasbled and detect 3D should be turned off. This is why the 2D import default tends to work on these devices as well.

I'm surprised sRGB textures is causing things to break, as I thought the conversion was purely a CPU-side operation performed at import-time.
Also, isn't the sRGB import option supposed to do nothing when using the GLES2 rendering backend?

I think the issue with older iphones is from using the sRGB option. sRGB should be diasbled and detect 3D should be turned off. This is why the 2D import default tends to work on these devices as well.

It's on newer iPhones as well, this was taken on an iPhone 11

It's on newer iPhones as well, this was taken on an iPhone 11

Which iOS version are you running on that iPhone 11?

@Calinou 15.5


add a helm chart to deploy zot

Signed-off-by: Andreea-Lupu<EMAIL_ADDRESS>
What type of PR is this?

Which issue does this PR fix:
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:

Automation added to e2e:

Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Andreea-Lupu can you also look at whether we can upload the chart here:
https://artifacthub.io/

@rchincha let's store the helm charts in a separate repo, as @Andreea-Lupu suggested, agreed?


Update Native Library Support

Make sure native libraries are placed in the correct directory with the
packaged APK file. Also added support for arm64-v8a architecture.
Change-Id: I567a1e08628e7df75a7e46c3efbee63134b15912

Which directory should native put in?thanks.

@jisqyv Just confirming that this PR is subsumed by the WebRTC commit in gerrit (it looks it to me). That seems like the more correct approach since this would be needed for that change to follow the every-commit-works rule. Otherwise, the libs wouldn't get packaged. What is your plan here?

@ewpatton This change is included in the WebRTC changes. I'm going to close this.


Having trouble compiling

I'm trying to compile a debug version to test some changes with. I had to do a lot of fighting with Visual Studio to end up with:
Error LNK2038 mismatch detected for 'RuntimeLibrary': value 'MT_StaticRelease' doesn't match value 'MTd_StaticDebug' in DS4Emulator.obj --- DS4Emulator --- [User Directories]\DualShock4-emulator\DualShock4-emulator\Source\ViGEmClient.lib(ViGEmClient.obj)
The problem I have is that I cannot change 'StaticDebug' to 'StaticRlease' in the DS4Emulator solution because it causes several errors concerning debug symbols. I'm assuming the ViGEmClient.lib file that came with the source code was compiled as a release which is causing the problem with making a debug build.
Is there a lib file available that was compiled as a debug version with the 'RuntimeLibrary' value 'MTd_StaticDebug'? If there is no other solution to this would I be forced to compile the ViGEm source?

debug.zip
ViGEm lib sources - https://github.com/nefarius/ViGEmClient/tree/master

Did you succeed?

Did you succeed?


Added rapture-core project to community build

Is this all that's required to include a new project in the build? Can someone let me know if this works, and if so I'll add the other Rapture projects? Thanks!

successor: #203


Dispatcher verticles are now worker verticles

Using worker verticles instead of event loop verticle
provides better isolation between consumers.
I added a reproducer for #2263 (thanks Marek)
that is now running in CI during KafkaChannel testing.
I've also improved logging which helped me tracking
down the issue.
As Vert.x's docs says:

Worker verticle instances are never executed
concurrently by Vert.x by more than one thread,
but can executed by different threads at different times.

That's the reason why we're moving to synchronized
and atomic data structures for dispatcher components.
Fixes #2263

/test channel-integration-tests-sasl-plain_eventing-kafka-broker_main

/test channel-integration-tests-sasl-plain_eventing-kafka-broker_main

/test channel-integration-tests-sasl-plain_eventing-kafka-broker_main
/test channel-integration-tests-ssl_eventing-kafka-broker_main
/test channel-integration-tests-sasl-ssl_eventing-kafka-broker_main

/test channel-integration-tests-sasl-plain_eventing-kafka-broker_main

Worked, retesting:
/test channel-integration-tests-sasl-ssl_eventing-kafka-broker_main
/test channel-integration-tests-ssl_eventing-kafka-broker_main

unrelated EOF error https://github.com/knative/pkg/issues/1509:
Error from server (InternalError): error when creating "STDIN": Internal error occurred: failed calling webhook "sinkbindings.webhook.sources.knative.dev": failed to call webhook: Post "[https://eventing-webhook.knative-eventing.svc:443/sinkbindings?timeout=10s](https://eventing-webhook.knative-eventing.svc/sinkbindings?timeout=10s)": EOF

and timeout on KafkaChannel readiness:
kafkachannel.messaging.knative.dev/channel created
subscription.messaging.knative.dev/event-display created
service/event-display created
deployment.apps/event-display created
sinkbinding.sources.knative.dev/bind-heartbeat created
deployment.apps/hearbeat created
error: timed out waiting for the condition on kafkachannels/channel

There are no nodes that your pod can schedule to - check your requests, tolerations, and node selectors (skip schedule deleting pod: test-pods/e7440397-ebcc-11ec-a2fb-666d91f9e04d)

/retest-required

/test channel-integration-tests-sasl-plain_eventing-kafka-broker_main

/test integration-tests_eventing-kafka-broker_main

/retest-required

/lgtm
/approve
Thanks!

/test integration-tests_eventing-kafka-broker_main

/cherry-pick release-1.4

/cherry-pick release-1.5


Add support for rounded timestamps on environment metrics

Description
This PR adds support to the GET /metrics endpoint to round the returned timestamps to the previous hour
closes #6051
Self Check:

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in ce19daf93564918a281c6ad44c1f2d3d906e851e

Processing #6431.


test-fix

The original test empties the class list of the code element it is testing, then checks for the ' failure' string.
This gives a false negative result if the coder creates their solution using jQuery, as jQuery does not add the space unless there is another class already present.
With this fix, both vanilla and jQuery solutions would be tested correctly.

@EricJFisher Hi there, I created this PR to fix an issue described above. Can I expect an action to be taken in the close future or should I close it?

Okay, checked it out and looks good, sorry again for this being overlooked.