[Bug] Race Condition during event handlers initialization

Description
Due to how this library binds event handlers to the google maps object there is a race condition. Events might be fired before react event handler is attached to the map. The simplest example is onProjectionChanged:
Steps to Reproduce
const App = () => {
  const onProjectionChanged = useCallback(function onProjectionChanged() {
    console.log("onProjectionChanged");
  }, []);

  const onBoundsChanged = () => {
    console.log("onBoundsChanged");
  };

  console.log("render app");
  return (
    <APIProvider apiKey={API_KEY}>
      <Map
        zoom={3}
        center={{ lat: 22.54992, lng: 0 }}
        gestureHandling={"greedy"}
        disableDefaultUI={true}
        onProjectionChanged={onProjectionChanged}
        onBoundsChanged={onBoundsChanged}
        onClick={() => console.log("click")}
      />
      <ControlPanel />
    </APIProvider>
  );
};

Try to reload map few times, and onProjectionChanged called not every time.
This happened due to map instance created in one useEffect and events bound in another. They are executed in diffrent async cycles, so map sometimes managed to fire an event before handler attached.
PS I tried to create a codesandbox with an issue, but in the sandbox no events were fired at all https://codesandbox.io/p/devbox/amazing-bohr-v65hqw
Environment

Library version: 0.4.1
Google maps version: 3.55.4
Browser and Version: Chrome 120
OS: MacOs Sonoma 14.1.2

Logs
No response

I can see why it's happening, but I don't have a good Idea how to fix it properly.

the map instance is created in an effect in the useMapInstance() hook and stored in a state variable: https://github.com/visgl/react-google-maps/blob/9422f03d18cafd98ae161706e3ca797a35407db2/src/components/map/index.tsx#L185-L217
that state variable is then passed on to the useMapEvents() hook where event-handlers are attached in another effect-hook: https://github.com/visgl/react-google-maps/blob/9422f03d18cafd98ae161706e3ca797a35407db2/src/components/map/index.tsx#L86-L90

So there could be a very short gap between creating the map instance / the setMap call and adding, since I think the setMap will cause a re-render and the updated map-value will only be available in the next render cycle, which is probably enough time for the maps api to initialize and trigger the initial events.


Deleting an array of problems

When I delete an item of the array, the array of the next item will inherit the position of the deleted item.

Delete array update location failed

@messieurspeng please provide an example with screenshot or code.

After I clicked this method, the dragList array was deleted, but the location was disturbed when the view was updated.
detele(index){      this.dragList.splice(index , 1)  }
array ：
dragList : [ 					{ left : 50 , top : 50 , width : 120 , height : 120 , fontSize : '12px' , name : 'a'}, 					{ left : 50 , top : 200 , width : 100 , height : 100, fontSize : '20px' ,  name : 'b'} 				],

The array information is correct after deleting, but there will be problems in view updating.

same problem here, did you fixed?

I think I know what's wrong in this case. You have to provide the key attribute to each item, otherwise Vue doesn't know how to reorder existing elements.
https://vuejs.org/v2/guide/list.html#key
The following example works correctly:
<VueDraggableResizable v-for="(component, index) in components" :key="component.id" :x="component.x" :y="component.y" :w="component.w" :h="component.h">
    <p>{{ component.text }}</p>
    <button @click="deleteMe(index)">Delete me</button>
</VueDraggableResizable>

<script>
export default {
  data: function () {
    return {
      components: [
        {id: 1, x: 50, y: 50, w: 100, h: 100, text: 'Component 1'},
        {id: 2, x: 150, y: 150, w: 100, h: 100, text: 'Component 2'},
        {id: 3, x: 250, y: 250, w: 100, h: 100, text: 'Component 3'}
      ]
    }
  },
  methods: {
    deleteMe (index) {
      this.components.splice(index, 1)
    }
  }
}
</script>


ARROW-10271: [Rust] Update dependencies

Tested by running tests, benchmarks and examples.
Did this with simd on and off
The main one here is packed_simd > packed_simd_2,
as the former is broken on recent nightlies

I've marked this as a blocker for 2.0. I also tested with nightly-2020-10-10, and tests ran fine.
@andygrove, out of curiousity, is there any reason why datafusion doesn't enable simd by default? Looks like there's no easy way of enabling it, so users could be losing out on the benefits on compute.

@nevi-me @jorgecarleitao I think we're too late to get this into 2.0.0 since the release candidate has already been cut and the voting process has started. I just ran the tests on the release candidate and it looks fine. If I'm understanding correctly, the issue resolved here is only relevant if we move away from the current nightly Rust?

Thanks Andy, it'll affect anyone who uses 2.0 with SIMD and a recent nightly. I don't yet know when pckdsmd broke, so it could be any nightly in the last month maybe.

Got it. If there is a 2.0.1 release then we could consider applying this patch there.


Estimated accuracy of the positions

Dear Sir:
I tried to find the estimated accuracy of the position but I could not find it. For example, the researchers claimed that the estimated accuracy of the positions in the highD datasets is 0.1m.
I wonder what is the estimated accuracy of the positions in the CitySim datasets.
Thank you!

Hello Ximen,
Cause we fly at different hight for a different locations, I will say 10-20 cm will be the range.


Support to format commonjs

Thanks for excellent package.
I needed commonjs format in my project, I just adapted to generate format.

If you accept, which is by default in the "main" of packages.json?
The ES6 format (vuex-i18n.es.js) or the commonjs format (vuex-i18n.cjs.js)
Thank you man, I will disclose here in the community Vue.js Brazil

Hi @ktquez,
Thank you very much for your contribution. I will merge your changes next week once I am back from my holidays. The additions do look good on a quick glance, but I would like to make sure, that we only include the dependencies that are really required and it seems to me that there are somehow too many dev dependencies included. But I will have to examine this a little more closely.
In regards to the main in package.json: I would like to stick with the es6 module system, as to me, this seems to be the future of javascript modules (see also https://auth0.com/blog/javascript-module-systems-showdown/). However, I am very open to changing it, if you have compelling reasons why we should use the commonjs format.


Remove ContinuousBuildProgressEventsCrossVersionSpec from quarantine

The test didn't appear as flaky any more. The corresponding issue https://github.com/gradle/gradle-private/issues/3462 has already been closed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

OK, I've already triggered a build for you.


New command: Create a new untitled Excalidraw file

We should also integrate with the Create: New File... command.

Hi @pomdtr , VS Code dev here. I can help with this if you haven't started yet.

Hi @rebornix ! Thanks for proposing your help, go ahead :)

I did take a stab at it some time ago, but I did encouter a bug when saving the untitled document : the untitled editor was not closing after saving it to a document, leading to two document opened :/

Waiting for this eagerly. You should also specify a setting to set the "default path" where it should store the newly created files.

Emphasis on unsaved/untitled. My ideal workflow is embedding drawings into markdown, so I've no need for saving to its own file

Hi,
I am not sure if it is related to this issue, but I am not able to create a *.excalidraw.svg, *.excalidraw.png, *.excalidraw file using the below command in terminal:
code <file-you-want-to-create>.excalidraw

Please let me know if it is possible.
A workaround for this is to open code in the same directory using code . and then creating a new file inside vscode with the .excalidraw extension.

Yeah there is something wrong in the way the extension handle files. I really want to fix it, but I don't have a lot of time to dedicate to the issue right now. Any help would be appreciated!

Came here to log a feature request for exactly this.
It's a bit of a pain having to create a new file with a specific extension, open it with vscode etc... and it means there's no hotkey assignable shotcut that can be used with automations/layouts etc....

anyone have any update on this request? currently, I have to make a copy an existing .excalidraw file and then I can open it from Excalidraw. I wish I could actually help but I am no programmer.


connects to #773 to remove dams from water layer, keep them in boundaries

Updated docs, updated changelog, updated queries.

:+1:


Our XML parsing crashed

Traceback (most recent call last):
File "/lib/python3.12/xml/etree/ElementTree.py", line 1706, in feed
self.parser.Parse(data, False)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 5808, column 55
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File ".venv/lib/python3.12/site-packages/sitemap_grabber/sitemap_grabber.py", line 114, in _process_sitemap_content
root = fromstring(content)
^^^^^^^^^^^^^^^^^^^
During handling of the above exception, another exception occurred:
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 120, column 78
During handling of the above exception, another exception occurred:

Consider using beautifulsoup and parse it as html?
from bs4 import BeautifulSoup
   import requests

   url = "http://example.com/sitemap.xml"
   response = requests.get(url)
   soup = BeautifulSoup(response.content, 'xml')

   # Extract URLs from the sitemap
   urls = [loc.text for loc in soup.find_all('loc')]

   for url in urls:
       print(url)

or LXML with recover mode?
from lxml import etree
   import requests

   url = "http://example.com/sitemap.xml"
   response = requests.get(url)

   # Use a custom parser with recover mode
   parser = etree.XMLParser(recover=True)
   root = etree.fromstring(response.content, parser)

   # Extract URLs from the sitemap
   urls = root.xpath('//loc/text()')

   for url in urls:
       print(url)

Possibly fixed by https://github.com/simplecto/sitemap_grabber/commit/119bcc1b97bd7a4f5624f2cf33abbf372079a037
we will close and re-open this one if we see more errors around malformed sitemaps.
fyi - the cheap solution was a nested function to fix unescaped entities in the method that parsed the sitemap.


Atomic commit failed: Invalid argument when trying to set Output Mode

I've been playing with Haskell bindings to wlroots and tried to reimplement the rotation example as a test.
When I try to run my test, I get an error: [backend/drm/drm-atomic.c:55] Atomic commit failed: Invalid argument
Full log: http://lpaste.net/5837658220885180416
ltrace -e<EMAIL_ADDRESS> http://lpaste.net/6218130441421979648
dmesg | grep drm:  http://lpaste.net/6845711118548074496
I'm running this on an i3 2350M which has an intel HD 3000
Code is currently not public, but I can easily make it public if anyone wants to have a look at it.
EDIT: Totally forgot, the error happens when I call into wlr_output_set_mode in the handler for the output_add signal (logic taken from https://github.com/SirCmpwn/wlroots/blob/master/examples/shared.c#L590)

This was a missuse of the API on my end.
I had an struct wlr_output_mode on the stack after Marshalling from/to C calls.
Changing this to use the original pointers fixes this issue


Add RocketChat connector

Signed-off-by: Izabela Cardoso<EMAIL_ADDRESS>Signed-off-by: Matheus Miranda<EMAIL_ADDRESS>Proposed changes:

Added RocketChat connector
Updated docs/connector.rst
Updated CHANGELOG.rst

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog

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

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

cool, thanks for this PR! We'll give it a review soon, in the meantime do you mind signing the CLA?

We've updated the connector code to support rocket's realtime API, but it seems that the rocket's lib does not work on python2.7
Since we also maintain this lib, we will fix this error in the next days

It is ready to be reviewed now. We got it working on python 2.7.
Any changes requested let us know :)

Looking good, I made some more changes to adapt to the new structure. I also removed the typing indication for now: although I think it is neat, this should be solved in general for all channels that support it.


Contact button not working

Description
https://user-images.githubusercontent.com/78332454/193448810-c102d009-60eb-424e-8db5-93fcecf67637.mp4
contact button should've link of contact section
Screenshots
No response

pls assign me this @KiranAminPanjwani

Sure, please go ahead! 🤩

Made pr for this issue pls review it and merge it


Monitoring problem

Not sure what I am doing wrong but in the step where I try to connect to http data source for the graphite it says http error not found. I followed the directions exactly and tried to modify troubleshoot but I am not getting very far. I wonder if something changed since 2 years ago?

I wonder it too.


Create Quicksort

#issue4871

[x] I have read CONTRIBUTING.md.
[x] This pull request is all my own work -- I have not plagiarized it.
[x] All filenames are in PascalCase.
[x] All functions and variable names follow Java naming conventions.
[x] All new algorithms have a URL in their comments that points to Wikipedia or other similar explanations.
[ ] All new code is formatted with clang-format -i --style=file path/to/your/file.java

#4871
Explanation at Wikipedia: https://en.wikipedia.org/wiki/Merge_sort


fix: Use first field instead of last field

Description of proposed changes
Assuming the documentation in transform strain names is the goal

If multiple fields are provided, will use the first field that has a non-empty string.

Need a break in the for loop, otherwise "last field" will be used.
Ran across this because I was exploring a ncbi datasets genbank.ndjson file:
cat genbank.ndjson  \
  | ./bin/transform-strain-names  \
    --strain-regex ^.+$  \
    --backup-fields "Isolate Lineage" "Accession" "accession" \
  > genbank_transform_strain_name.ndson

Related issue(s)
Testing

[ ] Checks pass

Might only be relevant if multiple fields are provided here
https://github.com/nextstrain/monkeypox/blob/0ffc8d8451a4250aea95a9240551401575c0f6e6/ingest/config/config.yaml#L14


Max height with scroll bar

This may be a feature request, but may also be a bug.
On my dashboard I have used this card to show the agenda, but at a fixed height and scroll bar using custom card-mod.
This stop working a few versions ago, not sure which one as I can only roll back to 4.3.0 in hacs. I do have the
last version that works for me saved, but don't see the version number in it. https://justpaste.it/8pl6m
I used this code to do so;
style: |
ha-card {
height: 225px;
overflow: scroll
}

This has possibly happened since an option was added to the card to set the height. you will either need to use the card option, or may need to modify your card mod style:
cardHeight: 225px

Works perfectly, thanks.
On Fri, Jul 30, 2021 at 6:37 AM Steven Marks @.***>
wrote:

This has possibly happened since an option was added to the card to set
the height. you will either need to use the card option, or may need to
modify your card mod style:
cardHeight: 225px
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marksie1988/atomic-calendar-revive/issues/462#issuecomment-889804865,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWFPNULCVEQNNKN6Q43A3LT2J6GXANCNFSM5BCKGRUA
.

I used to have the following with no scrollbar:
style: |
  ha-card {
    height: 245px;
    overflow: hidden;
  }

It no longer works either, is there a way to hide the scroll bar with the new option?


Swift 5.0 branch fix build

Fixing the build.

@swift-ci test

The build-script line on macOS is:
/Users/buildnode/jenkins/workspace/swift-clang-PR-osx/swift/utils/build-script --test --validation-test --lit-args=-v --compiler-vendor=apple --reconfigure --verbose-build --build-ninja --build-swift-stdlib-unittest-extra --ios --tvos --watchos --lldb --lldb-no-debugserver --lldb-use-system-debugserver --lldb-build-type=Release --lldb-test-swift-only --lldb-assertions --build-subdir=buildbot_incremental --release --assertions --llbuild --swiftpm --swiftsyntax --playgroundsupport --sil-verify-all --skip-test-ios-host --skip-test-tvos-host --skip-test-watchos-host.

So we will compile enough to expose the problem if I did not revert enough. But I think these two are the only problems.

@swift-ci test linux platform

Did some more spelunking. It looks like the reason why linux is failing is we are testing on the 5.0 branch... the 5.0 branch on Linux is already borked for other reasons.
When I look at the swift-5.0 branch:
https://ci.swift.org/view/swift-5.0-branch/job/oss-swift-5.0-incremental-RA-osx/
There is a really clear blame list that this is breaking the build. See build #35 where these are the only two commits. So this should unbreak the swift-5.0-branch os x build. Since linux is already failing, we shouldn't hold up fixing macOS for that.


Remove HoL 2016 and add in HoL from DCUS 2017

@spara @sixeyed for approval

LGTM, are we eventually adding them to PWD?


[Main] [Performance] Margelo/Expensify - Performance Improvements

cc @Szymon20000 Relevant thread. @roryabraham might have some things to add when he’s back from vacation, but in the meantime, I’ve created this master issue to begin tracking our progress with the performance improvements coming from the engagement with Margelo.

Issues identified

[x] https://github.com/Expensify/App/issues/10789 - @szymon20000
[ ] [Hold Fabric] https://github.com/Expensify/App/issues/10792 - @Szymon20000
[x] https://github.com/Expensify/App/issues/10794 - @Szymon20000 @aldo-expensify
[ ] https://github.com/Expensify/App/issues/10793 - @Szymon20000 @roryabraham
[x] Upgrade RN fork to 0.70 (Convo 1) (Convo 2) (WIP PR) - Tim/Rory
[x] SideBarLinks - @tgolen https://github.com/Expensify/App/pull/10800
[ ] HeaderView Doesn't use onyx context context (I think it's also the case with SideBarLinks) It means onyx will send them another copy of personalDetails as far as I know - available
[ ] CI Tests (reassure, startup time) - (PR) @hannojg
[ ] Replace _.merge function with faster alternative - (PR) - @Szymon20000
[x] Open and close the same chat again and again on Android native and it will gradually slow down for no reason - Christoph (discussion)

I would add:

CI Tests (reassure, startup time)
SideBarLinks
HeaderView Doesn't use onyx context context (I think it's also the case with SideBarLinks) It means onyx will send them another copy od personalDetails as far as I know

Awesome. Added those. Presumably they don't have issues to link yet, right? Outside of SideBarLinks, as @tgolen is working on PRs for that.
P.S - I can co-assign you this tracker now that you've commented. GH wasn't allowing me to do that yesterday.

Upgrade RN fork to 0.70

Finished this last week

@tgolen @Szymon20000 I know a lot of progress has been made on the LHN improvements, is there more to do here or should we check that off?

I have a bunch of random cleanup items, but I feel pretty confident to check it off for now.

Update:

https://github.com/Expensify/App/issues/10794 is done
The value of https://github.com/Expensify/App/issues/10793 is in question/unclear. I think we'll likely want to continue investigating this, but there's a lot of context in this thread
https://github.com/Expensify/App/pull/11327 progress seems to have stalled, waiting for a summary of the CI stability issues from @hannojg
Replace _.merge function with faster alternative – PR merged yesterday and published to npm in<EMAIL_ADDRESS>However, we need to bump the Onyx version in App to see this change take effect.
Open and close the same chat again and again on Android native and it will gradually slow down for no reason – Last we heard, this was no longer reproducible, so I'm checking it off.
HeaderView Doesn't use onyx context context (I think it's also the case with SideBarLinks) It means onyx will send them another copy of personalDetails as far as I know - nobody is assigned to this one, but there have been a few investigations into more low-level Onyx improvements, particularly by @marcaaron. I like the idea of trying to dynamically generate Onyx contexts within withOnyx so that we can use the context API for all subscribers universally.

@roryabraham In my PR to start using the modern "drawer" navigator I refactor the HeaderView a little so that the props are already available and passed via the ReportScreen - just minimizes a connection or two. I think a context based solution would be interesting though but had trouble thinking of how it would work.

In my https://github.com/Expensify/App/pull/11550 I refactor the HeaderView a little so that the props are already available and passed via the ReportScreen - just minimizes a connection or two.

Yeah, we could probably extract that change out of the drawer PR because it's not directly related AFAICT?

Could do that yep

I'd add this PR as well:
https://github.com/Expensify/App/pull/11684
The reason for investigation was this described issue: https://expensify.slack.com/archives/C035J5C9FAP/p1664523169910029?thread_ts=1664522847.768359&cid=C035J5C9FAP

Put up this PR to glean the performance benefits from recent upgrades made in Onyx.

Removing https://github.com/Expensify/App/issues/4656 and instead replacing it with https://github.com/Expensify/App/issues/11997, which will provide us with clear metrics that we can point to when we want to know if we need to improve. The deliverables there are more clear and should help align us on how to make performance improvements.

Added the issue for the comment box freezing the app following quick typing.

https://github.com/Expensify/App/issues/10792 – on HOLD
https://github.com/Expensify/App/issues/10793 – @Szymon20000 will be meeting with the SQLite team sometime this week to investigate potential inefficiencies in the underlying SQLite implementation of quick-sqlite
https://github.com/Expensify/App/issues/11711 – @AndrewGable and @hannojg could probably say more, but my summary is that the original E2E performance test suite worked well locally, but due to use of emulators in CI machines, was too variable/unreliable to be useful. Emulators had unpredictable and substantial variance in performance. Even with the larger GitHub Actions runners, performance of emulators was unreliable. Now @AndrewGable is working on setting up AWS Device Farm w/ real cloud devices to run E2E performance tests and @hannojg is migrating the test suite to Appium to interface with AWS Device Farm. Please correct me if any of that was inaccurate.
https://github.com/Expensify/App/issues/11997 – No update really. We would need an internal infra volunteer to migrate graphs.expensify.com to make it public, so it's possible we'll use some other service to create a separate set of public graphs. Maybe host w/ GitHub Pages for simplicity
https://github.com/Expensify/App/issues/8503 – We've been making steady progress on this. It's also worth noting that some recent benchmarks have raised some concerns about the performance of Fabric. The only example I've seen of a Fabric-enabled app is rn-tester, and it's palpably faster and more responsive with Fabric enabled. We will have to see if that's really the case for our app. We'll still do this migration at some point, but it's possible that more work is required in the upstream to get better performance "out of the box" on Fabric. Long-term, when React 18 is enabled in react-native-web, that should open up new opportunities for better performance as well, and we won't be able to do that w/o Fabric enabled.
https://github.com/Expensify/App/issues/11321 – This PR has been in review for 3 weeks, let's work to get that one merged this week!

https://github.com/Expensify/App/issues/10793 – latest discussion with @Szymon20000 here
https://github.com/Expensify/App/issues/8503 – progress here seems stalled. Maybe we should pass this off so that @hannojg can focus on:

https://github.com/Expensify/App/issues/11711
https://github.com/Expensify/App/issues/11321
https://github.com/Expensify/App/issues/11997

Let's see if we can get @thomas-coldwell engaged in:

https://github.com/Expensify/App/issues/10894
https://github.com/Expensify/App/issues/10792

For https://github.com/necolas/react-native-web/issues/1019, maybe we can get @kidroca working on that piece?
Also @janicduplessis can we work on upstreaming the bidirectional scrolling features in FlatList?

Most of what's written above is still valid this week. I also also linked the tracking issue for KeyboardAvoidingView, as we have about 9 bugs there that have gone stale over the last week.

@janicduplessis has been making progress getting VirtualizedList code merged upstream
@Szymon20000 has been mostly focused on https://github.com/Expensify/App/issues/10793, reviews underway
@hannojg has a few open PRs up for performance improvements, but the Fabric upgrade has been passed off

Removing https://github.com/Expensify/App/issues/8503 because it's being handled by SWM now

Removing https://github.com/Expensify/App/issues/10273 because it was primarily done by @tgolen, not Margelo

Chatted with @JmillsExpensify – this issue is prettymuch serving the same purpose as Margelo's regular slack updates here. Rather than maintaining these multiple sources of truth, I'm actually going to just close this issue for now.


Please include a snippet to use the Application Default Credentials

adg@ had added support for the Application Default Credentials feature. Please add usage instructions in this repro's readme file to help developers who want to use this feature when consuming Google Cloud APIs.
Here are some ruby and node example documentation for reference.
https://github.com/google/google-auth-library-ruby
https://github.com/google/google-auth-library-nodejs

Matyuss

I've looked around but can't see where @adg added Application Default Credentials? @vsubramani, can you point to that?

I think he is referring to this: https://github.com/golang/oauth2/blob/master/google/default.go


Memory leak in kinetic

I'm launching roslaunch own_pkg calibration.launch which includes:

easy_handeye's calibrate.launch;
realsense2_camera's rs_rgbd.launch;
aruco_ros's single.launch;
panda_moveit_config's panda_control_moveit_rviz;
other minor things.

What I see in htop is the RAM filling up (in the arc of at most ~5m, even though the next picture says 22m), eventually using swap and finally crashing the pc. I also tried with 8GB more RAM just to see if it was a stabilization sort of issue but the behaviour is the same. Ordering the processes by memory used I see the problem is happening in something related to rviz:

The behaviour seems like it's a memory leak, and looking for memory leak PRs in RViz I saw #1294 (among other things which are already included in my version) and wanting to test if that fixes the leak I cloned the repo, checked out melodic-devel and git rebase -i kinetic-devel to get a compilable version for kinetic with the things added by the referenced PR (I couldn't manage to cherry-pick...).
pick 29ecde8 enable Travis again
pick 1bef2fb fix various catkin_lint issues
pick 26e920e remove executable flag from .ttf files
pick 0e8c842 suppress spurious warnings
pick a9d63cb update maintainer list
pick 707dc6f suppress cmake warnings
pick f230eab remove support for tf < 1.11.3
pick 6a769aa XML parse error message added (#1317)
pick 47af93a Revert "support multiple material for one link (#1079)"
pick e906f82 simplify material handling
pick 28fb778 support different materials for individual visuals
pick 83ac836 work-around for buggy urdf parser for visual materials

After fixing a compilation error (something with tinyxml2's Error() method, I used the compiler's suggestion) I re-launched my launch file and it seems to still be a problem, so unless I messed up something, this is not the issue I have.
I can provide the launch file and anything else needed, in case, but I'd rather have some help with what I can test to figure out where the root cause of the problem lies.
Also of note, last week I was seeing a QXcbWindow: Unhandled client message: "_COMPIZ_TOOLKIT_ACTION" in the log, which I'm not seeing anymore though.
Your environment

OS Version: Ubuntu 16.04
ROS Distro: Kinetic
RViz, Qt, OGRE, OpenGl version as printed by rviz:
current version from apt which is 1.12.17-0xenial-20190608-123836-0800, with OpenGl version: 3 (GLSL 1.3)

If you suspect rviz, verify the following:

Without rviz running, you shouldn't see the memory leakage anymore, right?
Then, start vanilla rviz and add one display after the other.
If you have found out, which display is the culprit, report back ;-)

I can confirm no issues if RViz is not started. Also while doing this I found the leak isn't triggered if the master is born out of roslaunch instead of independently started via roscore. The culprit seems to be MotionPlanning (there's only TF other than that in the rviz.config that easy_handeye is using).
Also these are displayed when adding that display:

[ INFO] - [/rviz_1563259975465041482::core::RobotModel::buildModel::93]: Loading robot model 'panda'...
[ INFO] - [/rviz_1563259975465041482::core::RobotModel::buildModel::93]: Loading robot model 'panda'...
[ INFO] - [/rviz_1563259975465041482::PlanningSceneMonitor::startSceneMonitor::949]: Starting scene monitor
[ INFO] - [/rviz_1563259975465041482::PlanningSceneMonitor::startSceneMonitor::955]: Listening to '/move_group/monitored_planning_scene'
[ INFO] - [/rviz_1563259975465041482::RobotInteraction::decideActiveComponents::97]: No active joints or end effectors found for group 'hand'. Make sure that kinematics.yaml is loaded in this node's namespace.
[ INFO] - [/rviz_1563259975465041482::RobotInteraction::decideActiveComponents::97]: No active joints or end effectors found for group 'hand'. Make sure that kinematics.yaml is loaded in this node's namespace.

I just checked about the hand config, and it's tied to using panda_arm_hand instead of panda_arm in panda_moveit config (we were talking about it here, so it seems it does have an impact, and I had not fixed it yet). No clue why it seems to be loading the move group twice, is it expected?

I'm afraid you need to narrow down the issue even more. When running panda_moveit_config's demo.launch, I don't see a continuous increase in memory, even over minutes.
What I see, though, is an increase of 2MBytes in the first few minutes (probably due to TF buffers filling up). Then the memory usage settles.

I too don't see a leak with demo.launch, I left it on overnight and in the now it is using the same memory as it was at the start. I'll do more tests on my side and let you know.

The issue isn't there anymore... The only relevant changes are in easy_handeye, among them I moved a dummy publisher from using tf to using tf2. Not sure what else could be the root cause.


[DOCS-347] Update pentester articles round 2.5

Changelog
Including links to pentester articles for Harsh and Farid

Also including content from https://github.com/cobalthq/cobalt-product-public-docs/pull/204/files, as I don't have privileges to modify the file name on Farid's fork

Added
n/a
Updated

Page
Deploy Preview
Comment

Best Practices page
link
Comment

Preview This Change
To see how this change looks in production, scroll down to Deploy Preview. Select the link that looks like https://deploy-preview-<num>--cobalt-docs.netlify.app/
Variables
Help us support a “Write once, publish everywhere” single source of truth. If you see a line that looks like:
{{% asset-categories %}}
You’ve found a shortcode that we include in multiple documents.
You’ll find the content of the shortcode in the following directory:
https://github.com/cobalthq/cobalt-product-public-docs/tree/main/layouts/shortcodes
That shortcode has the same base name as what you see in the PR, such as asset-categories.html.
Checklist for PR Author
[ ] Did you check for broken links and alt text?
Be sure to check for broken links and Alt Text issues. We have a partially automated process,
as described in this section of our repository README:
Test Links and Alt Attributes.

Grr, we still have problems with formatting Markdown tables, and I've already spent an hour trying different solutions. We need to accept this issue, and investigate. I've filed an internal issue for that purpose.

Grr, we still have problems with formatting Markdown tables, and I've already spent an hour trying different solutions. We need to accept this issue, and investigate. I've filed an internal issue for that purpose.

@mjang-cobalt This is solved. The problem was an extra space in Markdown files with shortcodes.

@mjang-cobalt This is solved. The problem was an extra space in Markdown files with shortcodes.

Brilliant, thank you!

@mjang-cobalt Has the Insecure Deserialization article gone through your review? I see that there are many formatting and language issues, and the readability score is 11.22.


Closing image uploader modal on outside click causes console error

Ref: https://github.com/bigbinary/neeto-kb-web/issues/4721

@gaagul _a


[CHALLENGE SUBMISSION] - Day 3

Please provide the following information for your submission:
What is your name?
Abhishek Chaudahry
Where is your GitHub Repo ?
https://github.com/abhishek0220/25daysofserverless/tree/master/challenge_3
What Challenge is this for? (Challenge number between 1 and 25)
3
(Optional) Anything else we should know? e.g., language used, location, blog post?
Pythno, SQL API

From all of us on the Cloud Advocacy team at Microsoft, thank you for creating this issue!
Have a Happy Holiday season!
Feel free to share your solution on Twitter with the tag #25DaysOfServerless

THANK YOU FOR YOUR #25DaysOfServerless SUBMISSION
We checked out your repository. We're thrilled to say your solution is now listed in our Hall of Fame
Thank you for your contributions!
This issue is now resolved! 🎉


This should actually fix the timestamp issue.

Seems like the VPS is running on UTC +2 timestamp, :ohnuu:

not a fan of working around issues this way as it does work in other places, thanks for trying to fix this but i'll look into another way to fix this


Automatically omit internal view component ivars

This changes the logic in safe_instance_variables to automatically
filter out instance variables that start with @__vc since that denotes
an internal ivar that shouldn't be used outside of view component
internals.
This should help prevent any conflicts/issues when view component adds
new internal attributes.

Thanks for this. I think automatically rejecting anything with @__vc is a really good solution, since this is easily the most fragile part of the library through VC updates.


.getInfo().title always  returning null

Everytime I use ".getInfo().title" it returns null I tried multiple songs (wich had youtube titels ofc). ".getInfo().author" and ".getInfo().uri" works fine. I also tried using differend versions of Lavaplayer but this always happens and a VPN.

An old version of my bot that I developed 5 month ago wich worked totaly fine at the time is also not working now.

Can you provide the LP versions you tested with?

I tried Lavaplayer version 1.3.47, 1.3.49, and LATEST (1.3.50 I guess)

This is fixed (with other things) in this fork: https://github.com/Devoxin/lavaplayer/tree/1.3.51
implementation 'com.github.Devoxin:lavaplayer:1.3.53' on jitpack

IntelliJ is not findig a version 1.3.51

Yes because there is no .51
This is another repo, a fork

Oh I think I got it. Its working now. Thank you verry much.


Interpolant function gives only initial value

After running the model, the current remains constant = 1st data point.
The interpolant function does not update the current field.
However, when the interpolant function is tested in stand-alone, it works correctly.
It looks like the interpolant function is not called every time-step or does not update correctly.
Code (Same as the example shown in Loading in current data)
#
# Simulate drive cycle loaded from csv file
#
import pandas as pd    # needed to read the csv data file
import pybamm
# Import drive cycle from file
drive_cycle = pd.read_csv("C:/Users/cheta/Battery/Experimental_Data/US06.csv", comment="#", header=None).to_numpy()

# Create interpolant
current_interpolant = pybamm.Interpolant(drive_cycle[:, 0], drive_cycle[:, 1], pybamm.t)

# Set drive cycle
parameter_values=pybamm.ParameterValues("Chen2020")
parameter_values["Current function [A]"] = current_interpolant

model = pybamm.lithium_ion.SPMe()
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve()
sim.plot(["Current [A]", "Battery vol_tage [V]"])_

Does anything change if you do sim.solve([0, 3600])?

Hi,
Thank you for getting back to me. I tried to solve with
sim.solve([0,3600]), however, the current value is still constant (first
value from the profile)
[image: image.png]

Simulate drive cycle loaded from csv file

import pandas as pd    # needed to read the csv data file
import pybamm
Import drive cycle from file
drive_cycle = pd.read_csv(
"C:/Users/cheta/Battery/Experimental_Data/US06.csv", comment="#", header=
None).to_numpy()
Create interpolant
current_interpolant = pybamm.Interpolant(drive_cycle[:, 0], drive_cycle[:, 1],
pybamm.t)
Set drive cycle
parameter_values=pybamm.ParameterValues("Chen2020")
parameter_values["Current function [A]"] = current_interpolant
model = pybamm.lithium_ion.SPMe()
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve([0,3600])
sim.plot(["Current [A]", "Battery voltage [V]"])
Thanks,
Chetan
On Mon, Jun 5, 2023 at 2:35 AM Ferran Brosa Planella <
@.***> wrote:

Does anything change if you do sim.solve([0, 3600])?
—
Reply to this email directly, view it on GitHub
https://github.com/pybamm-team/PyBaMM/issues/3011#issuecomment-1576226961,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZLOU47DQKPPDPUHCE5C23XJWD5DANCNFSM6AAAAAAYZN7KGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Chetan Dharmadhikari

Hello,
Please find below the minimum working example for this code. You can notice
that the current does not change even when provided as a profile.
Also attached same code

Simulate variable current profile

import numpy as np
import pybamm
current_profile = np.array([1.0,2,3,4,3,2,1])
time_profile = np.array([0.0,10.0,20,30,40,50,60])
current_interpolant = pybamm.Interpolant(time_profile[:],current_profile[:],
pybamm.t)
Set drive cycle
parameter_values=pybamm.ParameterValues("Chen2020")
parameter_values["Current function [A]"] = current_interpolant
model = pybamm.lithium_ion.SPMe()
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve()
sim.plot(["Current [A]", "Battery voltage [V]"])
On Wed, Jun 7, 2023 at 4:10 AM Ferran Brosa Planella <
@.***> wrote:

I can't tell what the problem is. Could you please produce a minimum
working example
https://en.wikipedia.org/wiki/Minimal_reproducible_example that we can
run on our machines and debug?
—
Reply to this email directly, view it on GitHub
https://github.com/pybamm-team/PyBaMM/issues/3011#issuecomment-1580262075,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZLOU4CI7CPAUFW27J3IHTXKBAPHANCNFSM6AAAAAAYZN7KGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Chetan Dharmadhikari

Your MWE works fine for me, so I think you just need to update your version of pybamm

Hi,
I am able to resolve the problem after updating the software. Please close
the issue.
Thank Ms for your help,
Chetan
On Mon, Aug 7, 2023, 7:46 PM github-actions[bot] @.***>
wrote:

It looks like there hasn't been a reply in 30 days, so I'm closing this
issue.
—
Reply to this email directly, view it on GitHub
https://github.com/pybamm-team/PyBaMM/issues/3011#issuecomment-1668751656,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHZLOU5TELFG3GP73A63F4DXUGD6RANCNFSM6AAAAAAYZN7KGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Semantics for Checkbox should react to the three-state mixed state

Continuation of #96218. When a three-state Checkbox is in the mixed state, the semantic flags for it do not update to reflect this.
Minimal example:
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool? isChecked = false;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: ListView(
        children: [
          CheckboxListTile(
            autofocus: true,
            onChanged: (value) => setState(() {
              isChecked = value;
            }),
            title: const Text('Tristate Value Checked'),
            tristate: true,
            value: isChecked,
          ),
          CheckboxListTile(
            value: isChecked ?? true,
            onChanged: (value) => setState(() {
              isChecked = value ?? false;
            }),
            title: const Text('Flag'),
          )
        ],
      ),
    );
  }
}

The tristate Checkbox should set the system object state STATE_SYSTEM_MIXED when it is in the mixed state. Currently, instead, it can be only in the checked or unchecked states dictated by STATE_SYSTEM_CHECKED.
This will require changes to the engine, as well.

/cc @chrisnorman7. Thanks for reporting this!

Closed by #111032

Hi,
Thank you so much for the work you've put ointo this.
Tristate now works perfectly on Windows. Unfortunately the half-checked state is not read by NVDA when running in Chrome.


Feature request: inline spell check as you type

The text field is namaged by Mattermost server. Could you make a issue at the forum?

Note: https://github.com/atom/electron/blob/master/docs/api/web-frame.md#webframesetspellcheckproviderlanguage-autocorrectword-provider

The Mattermost server is relying on the fact that most browsers automatically do spell checking. Since electron's browser does not, the feature will have to be implemented on the electron app's side via JavaScript.

Ah I should've read your second link before posting! haha

Thanks for the suggestion @kethinov ,
We're beginning to move feature requests from GitHub issues to our feature idea forum to keep all feature ideas in one place. Therefore, could we have your help contributing your suggestion in the feature idea forum so it can be discussed, upvoted and considered for a ticket?
Please include a link back to this GitHub Issue. If you're interested in implementing, please say so and we'll prioritize the review.
You get 10 votes in the feature idea forum, and each one influences the future of the project.

Thanks again @kethinov for the suggestion,
I have created a Feature Idea forum post where it can be discussed and upvoted.
Anyone interested in the community is encouraged to participate in the discussion.


Documentation for text highlighting options

There seems to be no documentation on changing text highlighting.
Currently, ale makes some pretty ugly highlight here:

See the section of the documentation on highlighting with :help ale-highlights and the related options linked within. See also :help highlight for the Vim documentation.


141598723: Fixed acceptance test failure

Next time add more to the commit message, like what you did/fixed.


Pipeline should not delete db and sec groups if existing

Signed-off-by: Nikolay Maslarski<EMAIL_ADDRESS>

Coverage remained the same at 93.19% when pulling 17010f89f8f12433d451dc95838d2c1c00d6bfc9 on SAP:fix_deploy_script into 3dffce6ae186e17f00e96330682b3916c699ed7e on cloudfoundry-incubator:master.

Coverage increased (+0.06%) to 93.249% when pulling 957a8c2a94ce0bab4e339e853169cca0d3fe8ddc on SAP:fix_deploy_script into 3dffce6ae186e17f00e96330682b3916c699ed7e on cloudfoundry-incubator:master.

Coverage increased (+0.06%) to 93.249% when pulling 957a8c2a94ce0bab4e339e853169cca0d3fe8ddc on SAP:fix_deploy_script into 3dffce6ae186e17f00e96330682b3916c699ed7e on cloudfoundry-incubator:master.

Coverage increased (+0.06%) to 93.249% when pulling 957a8c2a94ce0bab4e339e853169cca0d3fe8ddc on SAP:fix_deploy_script into 3dffce6ae186e17f00e96330682b3916c699ed7e on cloudfoundry-incubator:master.

Coverage decreased (-5.2%) to 87.944% when pulling 9fff4b8ea608e0da198a7529e8db0a9d60f80c93 on SAP:fix_deploy_script into 3dffce6ae186e17f00e96330682b3916c699ed7e on cloudfoundry-incubator:master.

Coverage decreased (-5.2%) to 87.944% when pulling 9fff4b8ea608e0da198a7529e8db0a9d60f80c93 on SAP:fix_deploy_script into 3dffce6ae186e17f00e96330682b3916c699ed7e on cloudfoundry-incubator:master.

Coverage decreased (-0.03%) to 93.161% when pulling 10c130dcefc8322e902f998bc3a1f98f5f1da519 on SAP:fix_deploy_script into 3dffce6ae186e17f00e96330682b3916c699ed7e on cloudfoundry-incubator:master.

Coverage decreased (-0.03%) to 93.19% when pulling a885570360ce67cd4af29b858575d290c51aea7d on SAP:fix_deploy_script into ca7209135ebdda6ed4418f33453ea9356fc139ed on cloudfoundry-incubator:master.


Sdk validation

Description

Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[x] Refactoring
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] Requires changes in customer code

High-level change(s) description - from the user's perspective
Added method annotations for documentation.
Added ajv validation for SdkBase inputs.
Related Issue(s)
Fixes
Related pull request(s)

Close in favor of #3171


correct way of nesting flexes

I'm trying to create a pane/docking system with egui_flex 0.1.1. What I'm trying to achieve is:

a group of outer flexes that determines the layout of the panes
each pane will display its content, which may use its own flexes but shouldn't affect the size of the panes

Here is a sample of my code:
Flex::vertical().show(ui, |flex| {
    flex.add_flex(egui_flex::item().grow(0.4), Flex::horizontal(), |flex| {
        flex.add_simple(egui_flex::item().grow(0.3), |ui| {
            self.ui_pane(ui, PaneContent::Empty);
        });
        flex.add_widget(egui_flex::item(), Separator::default().vertical());
        flex.add_simple(egui_flex::item().grow(0.7), |ui| {
            self.ui_pane(ui, PaneContent::Empty);
        });
    });
    flex.add_widget(egui_flex::item(), Separator::default().horizontal());
    flex.add_simple(egui_flex::item().grow(0.6), |ui| {
        self.ui_pane(ui, PaneContent::Empty);
    });
});

For some reason the contents keep stretching beyond the boundary of the window itself. I can't figure out what I did wrong just by looking at the examples. I'd appreciate any help.

grow(0.4) will just mean that if there is more space available than needed this item will grow with a factor of 0.4 and the other one with a factor of 0.6. If you want to use this for relative spacing you could give the items a basis of 0, I think then it should work as expected.

Thank you! It worked...for a flash second, and then the executable crashes:

thread 'main' panicked at D:\ProgramData\rust.cargo\registry\src\index.crates.io-6f17d22bba15001f\egui-0.29.1\src\ui.rs:897:9:
assertion failed: 0.0 <= width

Though for that instant it does look like things are arranged correctly. Here is the updated code:
Flex::vertical().show(ui, |flex| {
    flex.add_flex(
        egui_flex::item().grow(0.4).basis(0.0),
        Flex::horizontal(),
        |flex| {
            flex.add_simple(egui_flex::item().grow(0.3).basis(0.0), |ui| {
                self.ui_pane(ui, PaneContent::Empty);
            });
            flex.add_widget(egui_flex::item(), Separator::default().vertical());
            flex.add_simple(egui_flex::item().grow(0.7).basis(0.0), |ui| {
                self.ui_pane(ui, PaneContent::Empty);
            });
        },
    );
    flex.add_widget(egui_flex::item(), Separator::default().horizontal());
    flex.add_simple(egui_flex::item().grow(0.6).basis(0.0), |ui| {
        self.ui_pane(ui, PaneContent::Empty);
    });
});


Port fixes from https://github.com/krottiers/terraform-azurerm-avm-pt…

Description
Bugfix for #44
Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[ ] Azure Verified Module updates:

[x] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[x] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[ ] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
[ ] Update to documentation

Checklist

[x] I'm sure there are no other open Pull Requests for the same update/change
[x] My corresponding pipelines / checks run clean and green without any errors or warnings
[x] I did run all  pre-commit checks

@khushal08 - The proposed change is not currently tested in the deployment validation of the testExamples due to the requirements of an existing er_circuit I believe.


removing repeated data from contributers.js

hope this works well....

There are some conflicts please check once. @Yash-Parwani

I hope this should resolve those conflicts

The reason for the conflict was that someone had updated their data and had copy pasted in the same way the others did which lead to duplication of the data
So i guess that was the reason

Yes. Adding the data in the same line creates the conflicts. @Yash-Parwani
Congrats 🎉, your PR got merged. To be eligible for the swags from iNeuron X ClueLess. Follow this steps.

SignIn / SignUp in ClueLess Website.

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

Congrats 🎉, your PR got merged. To be eligible for the swags from iNeuron X ClueLess. Follow this steps.

SignIn / SignUp in ClueLess Website.
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

profile URL:https://www.clueless.tech/profile/admin/95875897
Pr merged by : @Rajdip019


[website] Add perpetual option to pricing page

Summary
On the last iteration of the pricing model, we stepped in the direction of creating a subscription model to have better revenue planning/expectations based on renewals.
We removed access to perpetual licenses (for new customers) and created the concept of "perpetual in production" that applies to a subscription model.
Not having a perpetual license might have been one of the biggest factors impacting our sales growth, and in fact, we've seen a rise in support requests related to confusions regarding this topic.
Additionally, the MUI Developer survey 2022 is trending to show that more than 70% of users care about having a perpetual license (the rate seems to be bigger between Paid customers).
Problems

Make subscription appealing compared with Perpetual.
Make users know that they can have a Perpetual plan to fallback, in case they feel trapped by a subscription model.
Clear the confusion generated by our subscription model (Most competitors have only Perpetual licenses)

It’d be great if the prototype also accounts for the future possibilities:

Standard and priority support
Number of developers
Custom components list (for users selecting a few components from X portfolio)

Related meetings

https://www.notion.so/mui-org/X-General-Meeting-2022-12-16-dcbff0cc31a148b183dcb63f97ad12e8

Related issues

https://github.com/mui/mui-store/issues/181
https://github.com/mui/mui-store/issues/136

Design

Figma Process
Figma Final

Preview
https://deploy-preview-35504--material-ui.netlify.app/pricing/
Benchmarks
https://shop.highcharts.com/

Updated & consolidated info:
Notion shaping page
Notion project tracking page

some feedback was done synchronously, but with different groups of people, primarily @joserodolfofreitas and @oliviertassinari. Other relevant links and meeting notes are there.

Draft 2
In lieu of coordinating schedules, I put together a Loom presentation (but it had to be in 3 parts 😅 for now).
Loom 1 — Overview and context
Loom 2 — Versions and structural options
Loom 3 — Store considerations
Figma file for contextual comments
🗣 Feedback for this draft:

preferences on page structure between version 1 and 2 (separate pricing factors section vs one section)?
do the described interactions make sense and are they doable?

dynamic pricing
sticky bar when scrolling the detailed chart comparison
passing information from MUI → Store

are we aligned on showing Subscription / Perpetual as equal options in the hierarchy, but using styling and defaults to emphasize one?
are we aligned on showing annual price instead of monthly?
are we aligned on removing the early bird banner at the bottom?
any other comments around structure and hierarchy; style and detailed copy will be addressed in a following draft

@gerdadesign Thanks for sharing this iteration. Thought on moving forward:

I think that we should release a first version, that involves minimal changes, so we can quickly see the effect in the next few days. For example, if needed, I could have bandwidth the next weekend to ship the first version of the perpetual plan.
I left comments on the Figma file.

@oliviertassinari, I believe we have a good first step to start iterating on the details.
https://deploy-preview-35504--material-ui.netlify.app/pricing/
The current solution encompasses the following:

A switch on the Plan's boxes to keep them contextualized and isolated from the community plan.
The switch maintains both options visible, so both options are searchable and easy to spot.
The key information about paid plans was moved up to close the gap between the concept introduction and explanation.
A tooltip with a short explanation of Annual and perpetual.
Currently experimenting with displaying Perpetual with full price while Annual with monthly price.

I'll leave the PR on draft for now because some parts of the code need a small refactory.

I have spent a few hours on this, I have pushed as far as I could, I think that it's good enough.

Looking good so far! I made some small color and shadow adjustments for better contrast as well as more consistent hierarchy in dark. For easier Figma navigation, use cmd+click to deep select the object or frame and in the Figma right panel, select Inspect. That has all the style info.
Dark mode
Light mode

Is there a value to have 3 different sections for Annual vs Perpetual? It seems like we could condense the content into one description for Annual and one for Perpetual. Or one "Annual vs Perpetual" and have a clear & concise description here. Perhaps @samuelsycamore would be helpful to tease out these copy edits?
Additionally, calling out again the use of the Annual title when we show price per month. Is there a reason we want to stick with / month while also showing the Annual title?

Can we rethink the layout/structure of this section? This doesn't feel like the best way to convey this information, in my opinion, and the differences in length in each box leads to it feeling out of balance.

It seems like there's a lot of (perhaps unnecessary) overlap in the content here and in the FAQs further down. Maybe we should consolidate these two sections into one somehow?

Can we rethink the layout/structure of this section?

@samuelsycamore, happy to hear what's your proposal. I ordered and grouped them based on the main questions the customers may have after seeing the price and what I thought was a good flow of reading.
Perhaps, as @gerdadesign suggested, there's a better way to phrase/put the contrast between Annual and Perpetual.

It seems like there's a lot of overlap in the content here and in the FAQs further down. I would think that this section would answer all of the FAQs. Maybe we should consolidate these two sections into one somehow? Could it all be one big FAQ (or Key Information) section?

I don't think the overlap of content is a problem in itself if they are adding up to the same concept and not getting contradictory. The redundancy might even be beneficial if it means we reach users journeying our pricing through different angles.
But I agree that there's an opportunity to improve these two sections. Maybe that's worth its own PR.

Maybe we should consolidate these two sections into one somehow?

Btw @samuelsycamore, they weren't separated before. Do you mean we should show them together as we do now?
(And show the testimonial section only after those two)

Jumping in here quickly, I've just pushed some changes:

Tried to tackle the Key info section by using display: grid instead of the Grid component. By not using flex for this, I think we enable a sort of layout that might help a bit?! Y'all tell me ⎯ it's looking better to me!
Light style tweaks to the tab (so it uses primaryDark when in dark mode).
Light arrangement tweaks to the FAQ section ⎯ I'm hoping the content order there wasn't specific!

shadow adjustments for better contrast

@gerdadesign Interesting, I also feel that the contrast was a bit too light.

[ ] The shadow could help, I think to try.

It's a good idea to display Perpetual first on the widget.

@joserodolfofreitas I felt that it was making a lot more sense, it communicates to the users it's taking a step back, in terms of renewals but also updates.

I love that it has an animation when using the tabs component

I wanted to use Joy UI initially, but because of the context isolation, everything was broken. I considered MUI Base but felt that Material UI's focus indicator was going to be great. For customization, the DX with Joy UI and Material UI felt the same, I think that it really depends on which one is closer to your target. Material UI has min-width, and min-height values which made it a bit painful. The keyboard as well:

[ ] We need to fix the indicator during the first render, it flashes. Here is the initial render:

it's not the most optimized in terms of height.

This was the primary driver for the position of the blocks and the content itself inside these blocks. We can definitely try different variations but we can't have big gaps like in the screenshot.

It seems like there's a lot of overlap in the content here and in the FAQs further down

[ ] I can find one that overlaps, with the required quantity. I think that it's OK but we can improve it, by using the same copy and making the header clearer.

they weren't separated before

The motivation to split them was two folds: 1. visual balance 2. breaking down the content to be easier to process. I think that there are 3 different things:

Which plan to I pick
What is specific about each plan

I think that the FAQ is ok for frequent but not too frequent questions. This feels like one of the most important aspects of the pricing.

I know I'm late to the party and it might not be that relevant for this specific PR but what about browsing it from the store directly? Will we add 2 more products (Pro perpetual and Premium perpetual) or will we have the option within the existing products? The way it currently does not allow us to select the perpetual option from the store, but only from the pricing page.


Incorrect value for some language attributes in som TS files

It seems like there are some problems with a few of the language strings in some ts files:
<TS version="2.1" language="l-screenshot_el">
<TS version="2.1" language="lumina-config_fa">
<TS version="2.1" language="lumina-config_el">
<TS version="2.1" language="lumina-desktop_fa">

I just re-synced all the various translation files with the latest sources.
Please re-test this and see if those files still have any issues.

Still there.
I tried changing "l-te_da" to "da" in one of the files and upload to weblate but it does not change it on weblate.

Fixed!
https://github.com/trueos/lumina/commit/3a2f9cf23880d4d6849924dce97dc3277a25711f

There is also:
l-te_da
l-te_el


DRAFT: home page Wormhole change

Description
On Home page

Replaced Wormhole text
Removed parralax wormhole image
Added KlimaDAO youtube video

Related Ticket
Resolves #492
Changes
| Before  | After  |
|||
-->
Checklist

[X] Building the site with npm run build-site works without errors
[X] Building the app with npm run build-app works without errors
[X] I formatted JS and TS files with running npm run format-all

I used this to prepare the youtube code: http://youtubeembedcode.com/en/
With the following configuration:

@jabby09 There is a comment in figma about the fonts. I am not sure if I am supposed to change them or not.

@biwano yes I saw that comment. If you using the same font and styling that already exists on the Klima website we should be good. I think what is best is get this into dev and a link I can share with our content lead for confirmation.

Hi! You can check the changes in the Vercel deployment associated with this PR. The link is above.

@Atmosfearful Thanks for commiting the locales.

@Atmosfearful @biwano will this auto deploy to Stage and Production?
This issue and PR is closed but the site is not update yet.

@Atmosfearful @biwano will this auto deploy to Stage and Production?
This issue and PR is closed but the site is not updated yet.

It should. If I remember correctly, it is not immediate. There is an automatic deployment twice a week.


Rename quickstart.md to quickstahrt.md

Why:

What's being changed:

Check off the following:

[x] All of the tests are passing.
[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

[image: Google]
Share entertainment & stay connected with your family
ACCEPT INVITATION
https://families.google.com/join/promo/MulhsFs5_ocatCny0FpOWul6OKAzxg
Deka Kenedi @.***) invited you to join her family on
Google.
Here are a few of the services she can set up for you to use together:
YouTube TV family plan
Google Play Family Library
Google Family Calendar
Google One
To see all services available for your family group, visit
families.google.com/families.
ACCEPT INVITATION
https://families.google.com/join/promo/MulhsFs5_ocatCny0FpOWul6OKAzxg
Google LLC
1600 Amphitheatre Parkway,
Mountain View, CA 94043, USA


This repo is missing latest release 0.23.0 and vsix's

Describe the bug
This repo is missing latest release 0.23.0
I was able to download 0.23.0.vsix file from vscode marketplace and https://open-vsx.org/api/mtxr/sqltools/0.23.0/file/mtxr.sqltools-0.23.0.vsix
can this release please be added with links to all the updated vsix's including the drivers

Expected behavior
This repos should include all the release versions and artifacts
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

SQLTools Version [v0.23.0]
VSCode Version: [v1.69.2]
OS: [Linux]
Driver:

[ ] PostgreSQL/Redshift
[ ] MySQL/MariaDB
[ ] MSSQL/Azure
[X] SQLite
[X] HANA

Database version: [e.g. MySQL v5.6, PostgreSQL vX...]

It may be too late to create a release record in GitHub for the exact commit at which @mtxr built and releases 1.23 and the bundled extensions. We plan to record the next release here though.
Please help us understand why you want the VSIX artifacts attached to the release record here in addition to being published on Marketplace.

I have created https://github.com/mtxr/vscode-sqltools/releases/tag/v0.23.0


Ethernet driver for DP83826IRHBR in STM32 nucleo_H743zi in MII mode

We are designing the custom board using stm32 nucleoH743zi, for that we have used DP83826IRHBR PHY chip in MII mode.
But we are not able to up the ethernet. We are using static IP address.
Below are the configuartion i have made,
#Ethernet MAC support
CONFIG_ETH_DRIVER=y
CONFIG_NET_L2_ETHERNET=y
#Mostly, this is ethernet MAC I need use
#But there is no way to plugin phy
#so we may need patch the STM32 driver
CONFIG_ETH_STM32_HAL=y
#Enable MII interface for STM32 PHY. This will automatically enable MII
CONFIG_ETH_STM32_HAL_MII=y
#Conduct auto PHY speed auto negotiation
#Need Alert patch
CONFIG_ETH_STM32_AUTO_NEGOTIATION_ENABLE=y
#100M or 10M, default is 100M
CONFIG_ETH_STM32_SPEED_10M=y
#CONFIG_NET_PROMISCUOUS_MODE=y
CONFIG_ETH_STM32_HAL_PHY_ADDRESS=1
And in dts file we have edit this for MII connection.
&mac {
status = "okay";
pinctrl-0 = <&eth_mdc_pc1
&eth_rxd0_pc4
&eth_rxd1_pc5
&eth_rxd2_pb0
&eth_rxd3_pb1
&eth_ref_clk_pa1
&eth_mdio_pa2
&eth_rx_dv_pa0
&eth_tx_en_pb11
&eth_txd0_pb12
&eth_txd1_pb13
&eth_txd2_pc2
&eth_txd3_pe2>;
pinctrl-names = "default";
};
So zephyr has supporting driver for this particular PHY chip.
If yes, what are the necessary configuration needs to done.

Can you edit this to include the required information from the bug template?

Please use our bug template when reporting bugs. You need to edit this issue to include the information requested in https://github.com/zephyrproject-rtos/zephyr/blob/main/.github/ISSUE_TEMPLATE/001_bug_report.md


Full Document May be incorrect tokenization in document_text

I am inspecting the contents of fulldocuments.json.  I notice that the json content has possible issues with "document_text" field.  In particular, that the text seems to be somewhat incorrect (possibly due to not inserting breaks?)
Examples:
https://answers.yahoo.com/question/index?qid=20071007114826AAwCFvR
example text:
show moreFollow 3 answersAnswersRelevanceRatingNewestOldestBest Answer
http://childparenting.about.com/od/physicalemotionalgrowth/tp/Child-Development-Your-Eight-Year-Old-Child.htm
.4 Cognitive DevelopmentTom Merton/Getty ImagesEight-year-old children are at a stage of intellectual development where they will be able to pay attention for longer periods of time.

Its worth noting that the documents produced are not necisarily perfectly clean documents. The technology used to produce these documents is primarily focused on generating documents that only have the truly relevant content present. In other words the system that produces this tries its best to remove any menus, side bars, and other artifacts that may have term matches but arent relevant. Since its a learned model its behavior is not perfect.

I agree - that make sense.  I get that, but I would expect the model to insert spaces / something between structural parts of the document.  Are these perhaps just getting removed as part of the conversion to json with one per line?  For example, my guess is that these are coming from line breaks being removed and not replaced with a delimiter.


Add a 'Reporting' section

Context
We need a section on reporting in some form or another on the same hierarchy as the other main sections in the docs
Changes proposed in this pull request

Introduction (first draft) of new docs for reporting. I did have a "Cancel payments" section on the same level as this as part of this PR but I'm not sure about that any more.

Makes some changes to 'Making payments' section

Changes directory name for 'Making payments' to 'making_payments' (not 'taking_payments' which was erroneous)

Guidance to review (please read)
I'm going to add some comments myself indicating where I'm unsure of things, so perhaps someone with expert knowledge can kindly help me fill those in.
Please consider this in draft form: as ever, everything goes—and that includes the structure of the docs—so feel free to be as free with your feedback as you please.
I'll also need to have this reviewed by a writer before I publish it.
I've put this up in an app "in situ" for testing/review: https://govukpay-reportingdocs.cloudapps.digital/

@katiebates @tillwirth @heathd @alexbishop1
I've made numerous changes to this after some feedback. Now viewable in situ (in addition to this PR) at https://govukpay-reportingdocs.cloudapps.digital/
Many thanks—any reviews/further feedback welcome :)

Is it worth adding this image to the 'Reporting' section:
https://s3-eu-west-1.amazonaws.com/pay-govuk-documentation/Partner-Architecture-v2.png

Thanks @alexbishop1: I've gone through and implemented much of your feedback. I still have some questions (where relevant I've added them to your comments).
The "Making payments" section is largely a holdover and written by a former writer/software person, and it seems like much of it is out of date.

@alexbishop1 I've added a note attempting to describe pagination and filtering by date. I can't help but wonder if at least some of this information would be best in the API reference section a la https://docs.registers.service.gov.uk/api_reference/ but I'm happy to revisit at a later time: just want to get some valid content about reporting out.
Just want to sanity check the API calls noted in the content are correct, too.

Thanks @alexbishop1, I've added all your suggestions per my comments against each 👍
Let me know what you think of the new version. The only thing I haven't added is something to call out placeholders explicitly: we do need that, but I'd like to make it uniform across the whole docs, so I'd like to do that separately in a different PR ideally.

I'm trying to be a bit creative with the ordering of the search/query parameters: does it look better/worse like this?

Looks good to me. A few comments:

Depending on how 'reporting' is understood, we could expand this section.
A - the dashboard is a form of reporting. service managers tend to use this to look at aggregate figures. however, it's pretty simple/ obvious at the moment so maybe it doesn't need explanation. the only thing which is perhaps not 100% obvious is the date ranges - for example, 'last 30 days' doesn't include today's transactions. (see https://govuk.zendesk.com/agent/tickets/2789063).
B - i wonder if the section makes it sound like you can only download a CSV, and not also see a list of transactions? just having a list of transactions is useful for reporting too. feel like i'm splitting hairs here though

CSV - although the title for the download button is "Download all transaction details as a CSV file." - we might want to spell out that the CSV gives all transaction data (we find that some services then edit it down to remove data they don't need), so they might want to be a bit circumspect about routinely downloading and keeping the files since there's a fair bit of PII in them.

page size - the maximum is 500 - it's not just the default. The API returns an error if a request is made with a display_size parameter > 500.

Is the display page example correct - why would page 1 display transactions 501-1000? Wouldn't it be 1-500?


Modify INSTRUCTOR keys (Old 167)

In gitlab by @A-Lawrence on Aug 31, 2015, 01:09
Broke the standards convention and introduced a new rating structure it seems!
INS1 => I1
INS2 => I2
INS3 => I3

In gitlab by @A-Lawrence on Aug 31, 2015, 01:16
Modified instructor keys to fit the same standard as others.  Resolves issue #488563 (167).
ÔåÆ <<cset 9b31135ab318>>
ALawrence66 - 2014-04-05T13:52:55.490999+00:00


Splitting up article data with firestore and realtime db

We can split up article data from only using firestore to use both firestore and realtime database.
Reasons :

Article's content is gonna be too big, and that's already good in firestore since it doesn't care about size
Realtime databse is better for searchability.

I guess we can clone article title, description and other stuff to RTDB while maintaining the true data in firestore?.

Okay! Seems like a good idea!

Already solved #14


found nil in ServiceResolver extension

Unexpectedly found nil while unwrapping an Optional value in ServiceResolver extension

finished with error - code: -1001
Swinject: Resolution failed. Expected registration:
{ Service: TrainListRouter, Factory: Resolver -> TrainListRouter }

finished with error - code: -1001
Swinject: Resolution failed. Expected registration:
{ Service: TrainListRouter, Factory: Resolver -> TrainListRouter }

Hi @MohammadEhsanMirzaaee
Could you tell me which version of AnnotationInject you're using? There was a known bug in 0.3.0 which was resolved into 0.3.1.
Also, what do you have into Register.generated.swift for TrainListRouter and/or TrainListRouterProtocol?

Hi
version: AnnotationInject (0.3.3)
Register.generated.swift:
`import Swinject
class AnnotationAssembly: Assembly {
func assemble(container: Container) {
container.register(TrainListRouterProtocol.self) { resolver in
return TrainListRouter()
}
.initCompleted { resolver, service in
}
.inObjectScope(.graph)
container.register(TrainSearchViewController.self) { resolver in
return TrainSearchViewController()
}
.initCompleted { resolver, service in
service.trainListRouter = resolver.registeredService()
}
}
}
`
TrainListRouter Class:
`// sourcery:inject
final class TrainListRouter
{
private let storyboard = UIStoryboard(name: "TrainList", bundle: nil)
}
/// sourcery:inject: scope = "graph", type = "TrainListRouterProtocol"
extension TrainListRouter: TrainListRouterProtocol
{
func createModule(userSearchModel: UserTrainSearchModel) -> TrainListViewController
{
...some code
}
}
`
I want use dependency injection in below
`// sourcery: inject
class TrainSearchViewController: BaseController
{
/// sourcery: inject
public var trainListRouter: TrainListRouterProtocol!`

Hi
version: AnnotationInject (0.3.3)
Register.generated.swift:

and my TrainListRouter Class:

I want to use dependecy injection in below controller:

I've just released a 0.4.1 on Cocoapods that should fix your issue.

thanks, can you provide a sample? need to a sample is felt, [https://github.com/SpectralDragon/Viper-LightRoute-Swinject/blob/master/ViperMCFSwift/Modules/FisrtModule/Configurator/FisrtModuleAssemblyContainer.swift](sample like this)

I'm sorry what do you want a sample for? Code from your previous screenshot should work now.
As for multiple injection for one class I think providers would achieve what you're looking for:
/// sourcery: provider
class MyFactory {
 static func instantiate(resolver: ServiceResolver) -> ProtocolA {
     return TrainListRouter()
 }

  static func instantiate(resolver: ServiceResolver) -> ProtocolB {
     return TrainListRouter()
  }
}

I never tested them with attributes injections so you might hit a framework corner.

after release 0.4.1 I get this error in build time:
Error Domain=NSCocoaErrorDomain Code=260 "The file “InjectAnnotation.swift” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/Volumes/Untitled/Projects/TestProjects/AnnotationInjectTest/Pods/AnnotationInject/Scripts/../Templates/../Sources/InjectAnnotation.swift, NSUnderlyingError=0x7fca36ca5710 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
this part is wrong: "../Templates/../Sources"

@MohammadEhsanMirzaaee You can try with 0.4.2

@MohammadEhsanMirzaaee Is it working with latest version?

sorry, I used another library


Store Sales Time Series Forecast

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Store sales time series forecast :
:red_circle: sales forecast time series problem :
:red_circle: https://www.kaggle.com/competitions/store-sales-time-series-forecasting/overview :
:red_circle: sales forecast using arima/RNN model : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

What are the deep learning methods you are going to use here for solving the issue?
@Vansh912

simple RNN model and arima time series model for comparision

You have to implement 2-3 models, are you comfortable with that?

yeah i can search for different models that are suitable for this problem

Cool. Start working on this issue. Assigned to you @Vansh912

ok sir

Full name : Aindree Chatterjee
GitHub Profile Link : aindree-2005
Email ID<EMAIL_ADDRESS>Participant ID (if applicable):
Approach for this Project :Using RNNs
What is your participant role? (Mention the Open Source program) CodePeak 2023

Issue assigned to you @aindree-2005


Performance

I am getting fairly poor performance in release mode (CPU)… 2kB/s.
Is there a guide on using the GPU?

Hi, which bindings to nnsplit are you using? The Rust bindings can be quite slow unfortunately because batching in tract does not work if the length dimension is dynamic too (there can only be one dynamic dim). Python bindings should be very fast though with sufficiently large batch size.

Hello, I am indeed using it from Rust.
What would be needed to get a fixed length dimension in Rust?

Having a fixed length is not possible or at least not feasible. That would mean specifying ahead of time that you are e.g. always using 100 bytes as input. That means that you have to pad input which is shorter than that and have to truncate input which is longer. Padding shorter texts is possible (but will slow things down too) but truncating longer text loses information.
The proper fix is tract being able to optimize models across more than one dimension which is tracked here: https://github.com/sonos/tract/issues/313
The easiest way to make things faster right now is using the Python bindings (the Python bindings are written in Rust too, you might get https://github.com/bminixhofer/nnsplit/tree/master/bindings/python/src usable from your Rust code). Alternatively you can use  the srx crate which will generate lower quality splits but is much, much faster.

Thanks for pointing me at srx. Much, much faster is indeed what I am looking for.
Maybe I can do something about https://github.com/sonos/tract/issues/313 … after reading into it.

That would be great! FYI, https://github.com/languagetool-org/languagetool/blob/master/languagetool-core/src/main/resources/org/languagetool/resource/segment.srx is the most useful SRX file for sentence segmentation that I know of.
I'll leave this open for now, performance of the Rust backend is indeed an issue.

There's been significant progress in tract and batched input is working now: https://github.com/sonos/tract/issues/383
Once it is released, I'll update it in nnsplit. It should lead to a > 20x Speedup of the Rust & Javascript bindings for batched input.

Nice, I need to check it out.

I finally got around to updating this, the Rust bindings should be at least 10x faster as of v0.5.8 for sufficiently large input.


fix broken args from click implementation - partial, multiple fails

The behavior of multiple still varies...it requires an implementation like:
--atm_sigma 1 --atm_sigma 2 --atm_sigma 1

Instead of
--atm_sigma 1 2 1

Hi @pgbrodrick.
This may not be useful, but Click can support the latter syntax if it is a fixed number of arguments:
@click.command()
@click.option('--pos', nargs=2, type=float)
def findme(pos):
    a, b = pos
    click.echo(f"{a} / {b}")

$ findme --pos 2.0 3.0
2.0 / 3.0

I'm not certain if this is the desired behaviour you're seeking or not. If you need flexible argument lengths, then you're correct to use multiple=True and use the first syntax. If you can expect the same number of arguments each time, maybe this would be better.

@jammont - we unfortunately don't know the number of bands in advance...it depends on the number of statevectors, which depends on other flags being set there.

Both checks and individual tests passed. Merging this in!


Reloading of addNew Tab in Toolbar?

Hi Guys,
is it possible to reload somehow the add New Control in the Toolbar? I would like to perform a reload of my form if i make a certain selection in a dropdown of the tab.
At the moment I grab the event of the select2 control and I am able to modify the backend after the ajax call. If I replace the addNew form with a new one the toolbar seems to be broken.
My first approach was something like this:
1.st  get the selected item from a select2 dropdown in the addNew Form.
2.nd perform an ajax request to get / prepare additional data etc.
 $.ajax({
            url: "/profile/UpdateNewForm",
            type: 'get',
            data: { Id: evt.val, name: name },
            dataType: 'json',
            success: function (response) {
                //Do Something
                var r = response;
                $('.js-newForm').replaceWith(r.htmlString);
                this.$subscriberForm = $('.js-newForm');
                this.$subscriberForm.bsInitUI();

                $('#toolbar').bsToolbar({
                    uniqueName: 'profileToolbar',
                    subscribers: [$('#grid')]
                });
                $('.myDropDown').on("change", function (e) { profileIndex.prototype.log("change", e); });
            },
            error: function (xhr) {
                var x = xhr;
                //Do Something to handle error
            }
        });

3rd after the ajax call succeded I replaced the form...
I saw in the documentation that you cann add a control, but i couldn't figure out how to use it for my scenario.
What would be the best way to refresh the tab? Should i remove it and add it again?
Could you provide an example on refreshing a  Tab?
Regards Dumitru

Here's a code snippet that should help you:
var profileIndex = function(options){
	this.options = $.extend(true, {}, options);
    this.init();
};

profileIndex.prototype.init = function(){
	this.$grid = $('#grid');
	this.$toolbar = $('#toolbar');

	this.initGrid();
	this.initToolbar();
	this.events();
};

profileIndex.prototype.events = function(){
	this.$toolbar.on('change', '.myDropdown', $.proxy(this._evChangeDropdown, this));
};

profileIndex.prototype._evChangeDropdown = function(e){
	e.preventDefault();
	var $target = $(e.currentTarget),
		val = $target.val();

	$.ajax({
		url: "/profile/UpdateNewForm",
		type: 'get',
		data: { Id: val },
		dataType: 'json',
		success: $.proxy(this._evChangeDropdownSuccess, this),
		error: $.proxy(this._evChangeDropdownError, this)
	});
};

profileIndex.prototype._evChangeDropdownSuccess = function(response){
	var $form = $(response.htmlString);
	this.$toolbar.find('.js-newForm').replaceWith($form);
	$form.bsInitUI();
};

profileIndex.prototype._evChangeDropdownError = function(){
	console.trace();
};

You are actually replacing only the form (child of toolbar) and you don't need to add any controls or apply the toolbar again.
Let me know if you still have any problems and show me your full code (views, js)


Set GOMAXPROCS automatically

Fix frequently-broken production deploys by forcing GOMAXPROCS to a sensible value. Follows https://github.com/kubernetes/website/pull/41142

OK, so this hasn't helped like I'd like it to. I think nproc is reporting an unhelpfully high value and this is causing Hugo to try to use too much concurrency.
I suspect there is also a concurrency bug of some kind in Hugo, but I'm not sure.
/close

It's a bit annoying that having 1 CPU and believing that there are 32 leads to either:

quick builds
apparent deadlocks

I think there might still be a bug in Go, Hugo, or one of their dependencies, but I haven't the appetite to track it down.

Another related issue is about the section-index partial timeout.
I checked the layouts/docs/list.html where the section-index partial is invoked.
It turned out that we are reusing the themes/docsy/layouts/partials/section-index.html, but we have our own layouts/docs/list.html, which overrides the themes/docsy/layouts/docs/list.html.
In short, we are invoking the upstream version "section-index" from our derived version of "list.html".
Besides this, the Docsy theme we are using is pretty old. We missed 0.6.0, 0.5.0, ... updates from Docsy. These inconsistencies all complicate the issue we have about section-index timeout.
Call for action:

Upgrade Docsy to its latest stable release: 0.6.0 at least;
Check if we really want our own customization of the 'list.html' file and drop the customized version if possible.


Avoid rand() and std::rand() for generating pseudorandom numbers

DESCRIPTION
The C Standard pseudorandom number generator function rand() has limitations. While these generators use mathematical algorithms to produce a sequence of numbers with good statistical properties, they are not genuinely random. Instead, they rely on a seed value to generate a sequence of numbers that appears random, but is actually deterministic.
The problem with using the C Standard function rand() is that it makes no guarantees about the quality of the random sequence produced. The function have a comparatively short cycle, which means that the sequence of numbers generated will eventually repeat.
Moreover, the generated numbers may be predictable, making them unsuitable for applications that require high-quality pseudorandom numbers.
This also applies to the std::rand() from C++ standard library.
It is recommended to choose a generator that is sufficient for the specific needs of the application.
BAD PRACTICE:
#include
#include
std::string getNewIssueId() {
std::string IssueId("ISSUE-");
// Holds the ID, starting with the characters "ISSUE" followed by a random
// integer in the range [0-100000].
IssueId += std::to_string(std::rand() % 100000);
return IssueId;
}
RECOMMENDED:
#include
#include
std::string getNewIssueId() {
std::string IssueId("ISSUE-");
std::uniform_int_distribution Dist(0, 100000);
std::random_device RandDev;
std::mt19937 Engine(RandDev());
id += std::to_string(Dist(Engine));
return IssueId;
}
Found using function rand which has limited randomness here: yara/blob/master/libyara/scanner.c#L224-L224
Reference: https://www.pcg-random.org/

The rand() function is enough for the use-case we have in YARA. Please do not copy and paste the output produced by C code analyzers here. These tools are certainly useful, but not all the suggestions make sense in all situations.


Validate failures after a rebase

After a rebase on 16th of July there are several unexpected validation failures:
   polykinds                 T6068 [bad stderr] (ghci)
   polykinds                 T7128 [exit code non-0] (normal)
   polykinds                 T7230 [stderr mismatch] (normal)
   polykinds                 T7973 [exit code non-0] (normal)
   typecheck/should_fail     tcfail220 [exit code 0] (normal)

The first four are either panics or bogus errors around AnyK. The last one should fail compilation but it succeeds.

The first four tests now pass correctly. The only remaining problem is tcfail220, which should fail but doesn't.

tcfail220 is, if I recall, something to do with .hisg files.   I think we can safely ignore it for now; all of this hsig stuff is being up-heaved by Edward, and no one else uses it.
So we are good!
Simon
From: Jan Stolarek<EMAIL_ADDRESS>Sent: 01 September 2015 01:06
To: jstolarek/ghc
Subject: Re: [ghc] Validate failures after a rebase (#144)
The first four tests now pass correctly. The only remaining problem is tcfail220, which should fail but doesn't.
—
Reply to this email directly or view it on GitHubhttps://github.com/jstolarek/ghc/issues/144#issuecomment-136532268.


[Rubocop] Re-enable Metrics/AbcSize

These we're disabled in 51fe6453e0b15dc38db529bae3ad333140352fa7 to ease upgrading to Rubocop 0.27.0 but we should look into fixing these issues and enabling this rule.
From https://github.com/CocoaPods/Molinillo/commit/87b6784341a98820c628daafa59bc8550d4fbd42#commitcomment-8586155

Closing, I agree with @alloy on this one.


[WIP]  readme updates including roadmap =D

[ ] add roadmap to readme for jest-pact
[ ] move unrelated items to pact out into a separate repo

@TimothyJones - this should be good to go fella, moved everything out into YOU54F/jest-pact-typescript


Logout throws Validation Error when using next branch

Environment

Nautobot version (Docker tag too if applicable): v2.2.0a1
Python version: 3.8
Database platform, version: Postgres
Middleware(s):

This is applicable when using the next branch with version v2.2.0a1.
Steps to Reproduce

Login with a User
Logout

Expected Behavior
Logout successfully

Observed Behavior
A ValidationError is thrown at /logout/ with message ['“4ci8je1rmskkfei3g8avd9mt2da2bft5” is not a valid UUID.'] when I use the next branch.

Thanks for filing the issue! We actually just noticed this bug yesterday on the core team. :-)
The issue is in the _handle_deleted_object signal, which is being triggered when the user logs out and their session DB record gets deleted. This signal is missing logic to handle the case where the deleted object has a PK that isn't of type UUID. A first pass fix is something like:
diff --git a/nautobot/extras/signals.py b/nautobot/extras/signals.py
index 86ad2aca8..17a31217c 100644
--- a/nautobot/extras/signals.py
+++ b/nautobot/extras/signals.py
@@ -20,6 +20,7 @@ from django_prometheus.models import model_deletes, model_inserts, model_updates

 from nautobot.core.celery import app, import_jobs_as_celery_tasks
 from nautobot.core.utils.config import get_settings_or_config
+from nautobot.core.utils.data import is_uuid
 from nautobot.extras.choices import JobResultStatusChoices, ObjectChangeActionChoices
 from nautobot.extras.constants import CHANGELOG_MAX_CHANGE_CONTEXT_DETAIL
 from nautobot.extras.models import (
@@ -165,6 +166,10 @@ def _handle_deleted_object(sender, instance, **kwargs):
     if change_context_state.get() is None:
         return

+    if not is_uuid(instance.pk):
+        # Probably some system object
+        return
+
     associations = ContactAssociation.objects.filter(
         associated_object_type=ContentType.objects.get_for_model(type(instance)), associated_object_id=instance.pk
     )

but we're having some discussions about whether there may be a more elegant way to fix it.

Fixed by #5322.


[6.0] Update lifetime dependence syntax

--- CCC ---
Explanation: Update lifetime dependence syntax
Scope: This changes the syntax  of lifetime dependence specifiers when experimental feature NonEscapableTypes is on.
Original PR: https://github.com/apple/swift-syntax/pull/2564 and https://github.com/apple/swift-syntax/pull/2567
Risk: All changes are under a flag
Testing: Unit tests added.
Reviewer: @ahoppen

Please test with following pull request:
https://github.com/apple/swift/pull/72625
@swift-ci please test

Please test with following pull request:
https://github.com/apple/swift/pull/72625
@swift-ci please test

Please test with following pull request:
https://github.com/apple/swift/pull/72625
@swift-ci please test macOS platform

Please test with following pull request:
https://github.com/apple/swift/pull/72625
@swift-ci please test windows platform


Add the stylish formatter in the Readme

Hey,
Just found that the stylish formatter is missing in the readme and the npm page. I was looking for it, so maybe it will help some other people :)

Thanks 👍


feat(csv): allow use verb in permissions

previously this was only allowed in clusterpermissions

/lgtm

cc @jcantrill

/retest

/retest

/retest


Update redirect URL of attachment assets in Asset Manager

This adds a new service listener which queues jobs to set the redirect URL for attachment assets in Asset Manager when the attachments parent document is unpublished/withdrawn and similarly unset the redirect URL when the parent document is re-published/un-withdrawn.
In combination with these changes to Asset Manager, this will replace the behaviour currently implemented in AttachmentsController#fail when we start serving Whitehall attachment assets from Asset Manager.
I've enhanced AttachmentRedirectDueToUnpublishingIntegrationTest which I added in a previous pull request so that it now also sets expectations for the updates which need to be sent to the Asset Manager API. For the moment, I've left the assertions for the original behaviour, because I think it makes things a bit clearer. We'll need to remove those assertions before we remove the AttachmentsController when we start serving attachment assets from Asset Manager.
Note that I've also had to make a small change to ServiceListeners::AttachmentDraftStatusUpdater so that assets related to an unpublished document are no longer marked as draft in Asset Manager. In Asset Manager the draft status is used to decide whether to redirect requests via the draft-assets host which requires authentication. The fact that AttachmentVisibility#visible? returns false for attachments associated with an unpublished document is a bit of an aberration, because the attachment URL should in some sense be "visible", i.e. it should be accessible without authentication, it's just that requests to it will be redirected to the URL of the parent document which will have a public page explaining why the document has been unpublished.
See individual commit notes for more details.

I'm going to review this now.


Link to missing webpage

A link in src/packages/s/documentation.json links to https://www.emojicode.org/docs/reference/the-s-package.html.
This page does not exist.

I transferred your issue because the link is part of a documentation comment. I think it can be removed altogether.


Cluster is missing permission

I am getting an error about the AWS Token being expired when trying to run the cluster in dev mode.
This is completely stopped me. And Im will be honest Im only guessing that it is related to SST and was hoping to post this to see if anyone else had the same issue.
Sorry if this is not SST issue. I just dont know what happened

I found the issue!! I think. Pr incoming shortly 🚀


[stable/grafana] Update curlimages/curl to 7.70.0

This will allow other architectures besides amd64 to download and install Grafana dashboards.
Signed-off-by: Kristopher Kram<EMAIL_ADDRESS>
Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ x] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ x ] Title of the PR starts with chart name (e.g. [stable/mychartname])

@KristopherKram
Thanks for contribution.
Could you sign DCO and bump the grafana chart to the latest version please? The instruction list on the bottom of this PR. Click Details for instructions.
/assign

Closing. Going to open another pull request.