Query engine binary for current platform "debian-openssl-1.1.x" could not be found.

Bug description
THIS IS A TYPESCRIPT PROJECT
Docker container runs however, when using prisma client to begin querying the server crashes with the error.
app_1              |   Query engine binary for current platform "debian-openssl-1.1.x" could not be found.
app_1              | This probably happens, because you built Prisma Client on a different platform.
app_1              | (Prisma Client looked in<EMAIL_ADDRESS>app_1              |
app_1              | Searched Locations:
app_1              |
app_1              |   /app/node_modules/.prisma/client
app_1              |   /Users/darren/Desktop/pixel-villains-cr/node_modules/@prisma/client
app_1              |   /app/node_modules/@prisma/client
app_1              |   /app/node_modules/.prisma/client
app_1              |   /app/prisma
app_1              |   /tmp/prisma-engines
app_1              |   /app/node_modules/.prisma/client
app_1              |
app_1              |
app_1              | To solve this problem, add the platform "debian-openssl-1.1.x" to the "binaryTargets" attribute in the "generator" block in the "schema.prisma" file:
app_1              | generator client {
app_1              |   provider      = "prisma-client-js"
app_1              |   binaryTargets = ["native"]
app_1              | }
app_1              |
app_1              | Then run "prisma generate" for your changes to take effect.
app_1              | Read more about deploying Prisma Client: https://pris.ly/d/client-generator
app_1              |     at cb (/app/node_modules/@prisma/client/runtime/index.js:35107:17)
app_1              | (Use `node --trace-warnings ...` to show where the warning was created)
app_1              | (node:33) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

How to reproduce
PRISMA SECHMA:
generator client {
  provider = "prisma-client-js"
  binaryTargets = ["native","debian-openssl-1.1.x"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model company {
  id      Int     @id
  name    String
  age     Int
  address String? @db.VarChar(50)
  salary  Float?  @db.Real
}

DOCKER dev file:
In my prisma/client file within node modules I have "query-engine-darwin" binary.
FROM node:14-slim
RUN apt-get update && apt-get install --no-install-recommends --yes openssl

WORKDIR /app/src

COPY package*.json /app

RUN npm install

COPY . /app
COPY prisma ./prisma

RUN npx prisma generate
RUN npm run build

DOCKER-COMPOSE
version: '3.8'

services:
    app:
        build:
            context: .
            dockerfile: DockerFile.dev
        env_file:
            - ./.env
        volumes:

             - "./src:/app/src"
             - "./nodemon.json:/app/nodemon.json"
             - "./node_modules:/app/node_modules"
        ports:
            - 5000:3000
        depends_on:
            - "cloud-sql-proxy"
        command: sh -c "npm run dev"
    cloud-sql-proxy:
         image: gcr.io/cloudsql-docker/gce-proxy:1.21.0
         volumes:
             - ./cloudsql_service_acct.json:/tmp/keys/keyfile.json

         command: /cloud_sql_proxy -instances=INSTANCE=tcp:<IP_ADDRESS>:5432 -credential_file=/tmp/keys/keyfile.json
         expose:
           - 5432

ERROR:
app_1              |   Query engine binary for current platform "debian-openssl-1.1.x" could not be found.
app_1              | This probably happens, because you built Prisma Client on a different platform.
app_1              | (Prisma Client looked in<EMAIL_ADDRESS>app_1              |
app_1              | Searched Locations:
app_1              |
app_1              |   /app/node_modules/.prisma/client
app_1              |   /Users/darren/Desktop/pixel-villains-cr/node_modules/@prisma/client
app_1              |   /app/node_modules/@prisma/client
app_1              |   /app/node_modules/.prisma/client
app_1              |   /app/prisma
app_1              |   /tmp/prisma-engines
app_1              |   /app/node_modules/.prisma/client
app_1              |
app_1              |
app_1              | To solve this problem, add the platform "debian-openssl-1.1.x" to the "binaryTargets" attribute in the "generator" block in the "schema.prisma" file:
app_1              | generator client {
app_1              |   provider      = "prisma-client-js"
app_1              |   binaryTargets = ["native"]
app_1              | }
app_1              |
app_1              | Then run "prisma generate" for your changes to take effect.
app_1              | Read more about deploying Prisma Client: https://pris.ly/d/client-generator
app_1              |     at cb (/app/node_modules/@prisma/client/runtime/index.js:35107:17)
app_1              | (Use `node --trace-warnings ...` to show where the warning was created)
app_1              | (node:33) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
app_1              | (node:33) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Expected behavior
No response
Prisma information
generator client {
  provider = "prisma-client-js"
  binaryTargets = ["native","debian-openssl-1.1.x"]
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model company {
  id      Int     @id
  name    String
  age     Int
  address String? @db.VarChar(50)
  salary  Float?  @db.Real
}

Environment & setup
MAC CATLINA 10.15.7
Works in local, can read and introspect. But when testing on docker, i get the error.
I am trying to host this on cloud run.
Prisma Version
prisma               : 2.23.0
@prisma/client       : 2.23.0
Current platform     : darwin
Query Engine         : query-engine adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules/@prisma/engines/query-engine-darwin)
Migration Engine     : migration-engine-cli adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine : introspection-core adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary        : prisma-fmt adf5e8cba3daf12d456d911d72b6e9418681b28b (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash : adf5e8cba3daf12d456d911d72b6e9418681b28b
Studio               : 0.393.0

lmfao fixed. add this to your sechma.prisma
generator client {
  provider = "prisma-client-js"
  binaryTargets = ["native", "darwin", "debian-openssl-1.1.x"]
}

idk if this is "proper" but it seems to get it to work. will test it on production tomorrow by hosting it on cloud run. for now i am going to study for finals.

I would like to add to be able to NOT have to install the entire prisma package and just install prisma client when using docker.

Prisma uses a Rust binary under the hood which is platform specific. You need to ensure that engines for platform you are using are there. If you sharing a volume between windows <-> docker linux, you need that binaryTargets block so that you have engine builds for both platforms downloaded. The npx prisma generate command will do that.


[Story] Review a validation report of Errors in my submitted file

Epic
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
Add link to the parent epic
User story
As a filer, I want to review a validation report of Errors in my submitted file, so that I can review the necessary changes I need to make to my submission.
Acceptance criteria
Given a user has submitted a file when they receive confirmation of a successful upload then the system should provide an Error Validation Report highlighting the necessary changes that need to be made in their file.
Technical tasks
Developers should create technical tasks and add links (below) prior to sprint planning.
Front end

[ ] Task (link)
[ ] Task (link)

Back end

[ ] Task (link)
[ ] Task (link)

@sthomas93, I changed the acceptance criteria from "Given a user has submitted a file when they receive confirmation of a successful upload then the system should provide an Error Validation Report highlighting the necessary changes that need to be made in their file." to "Given a user has uploaded a file and triggered Error Validations, when they visit the resolve errors page the system should display an Error Validation Report highlighting the necessary changes that need to be made in their file as well as an option to download a copy of the report, then they will know what the errors are, where the errors are, and what they need to do about the errors."
I did this to make sure we capture the downloading report option and to avoid another story.


Update confluent_connector.md

as per docs: https://docs.confluent.io/cloud/current/connectors/cc-kinesis-source.html#aws-credentials

Thanks for creating a PR! I agree there's this difference with Kinesis source connector but our example seems to represent Amazon S3 Sink connector.

Yes, but I have just run your example and it did not work.
Error: error creating Connector "*****": error validating config: 1. "aws.secret.key.id" : ["\"aws.secret.key.id\" is required"]

Wait, it didn't work for S3 Sink Connector? 😮

oh sorry. No, just for kinesis. You can close the PR again 😅

Thanks! By the way, will it be helpful if we add examples for more connectors and not just S3 Sink one?


Use fused types in DQM cython methods

E.g. https://github.com/dwavesystems/dimod/blob/3402a03a337b64f4618fc2fbc44a3c5e58f60e5d/dimod/discrete/cydiscrete_quadratic_model.pyx#L418 since right now there will be a buffer mismatch

Closed by #716


Render embedded code preview by permlink in markdown (#30234)

Backport #30234 by @wxiaoguang
Ready for review

Try to backport it: https://github.com/go-gitea/gitea/pull/30234#issuecomment-2032634745
And I suggest to backport it to 1.22, because:

1.22-rc0 is far from stable, it still contains a lot of refactorings, and this PR is quite clear/independent and is covered by tests, it shouldn't cause problems.
Some related testing code changes are important for further backporting works.


Fix: Minor fixes

Thank you very much for this contribution! :)
Seems like typos are very common for me 😅


Change some line endings from CRLF to LF

The only remaining files that still use CRLF should be:

bin/crystal.bat
bin/crystal.ps1
etc/msvc/crystal.natvis
etc/win-ci/*.ps1
etc/win-ci/crystal.iss
Makefile.win
samples/Makefile.win

I'm wondering if we should put those paths into .gitattributes with eol=crlf and a default entry with eol=lf? 🤔


Add a conclusion to the tour

This PR adds a conclusion to the tour directing the reader to resources for further study.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.758%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
822

Relevant Lines:
1331

💛  - Coveralls


Add Symfony 3.4 compatibility, without deprecation notices

Added reset function that caused deprecation notices in Symfony 3.4+ upgrades.

@ChristianRiesen could you please also do what has been done in https://github.com/M6Web/AmqpBundle/pull/46/files please? 🙏
If this bundle could be compatible with SF4 too, that would be nice :)

@Oliboy50 There is a problem with Symfony 4, that's why I backed it down to 3.4 to be compatible, so that can be used without having tons of deprecation notices. For 4.0 you need a bit more work. I had it in originally, but that went bad. See here: https://travis-ci.org/M6Web/AmqpBundle/builds/312455080
I'd be very happy to have this merged as is and tagged.
My suspicion is that there is something going wrong with the tests because of how PHP 7.1 handles the error triggering now, but that's just a hunch, and I think it would be best to address that in another PR.

@ChristianRiesen thanks for your feedback about  SF4 👍

No problem. It gave me some headaches today, but thankfully I don't need SF4, yet :)

@Oliboy50 I went over it again and made sure there will be no states that could cause an error. I cleaned up some small things (also in regard to PHP7) in this PR as well since probably nobody will touch the datacollector in a long time anyways :)
If this works for you, please merge and tag. Thank you!


Connection manager bug

Hi im currently using .net framework for my bots and im getting a really weird bug with the connection manager i have spent the past hour trying to debug it with no luck and the only error im getting is https://i.imgur.com/8EeuCkr.png
Up untill now my bot has been working perfectly but it seems like Discord has changed something with the shard system causing these issues because i have been testing it with multiple versions including the latest and 0091 which is old.

I don't think Discord wouldn't change things like sharding without warning us. What I think is happening is that your websocket is timing out in the connect phase.

The ConnectionManagar hasn't been touched in over a year. Try targetting .net core instead since that's where Microsoft have focussed their websocket improvements.

I just changed the ConnectionTimeout config to 50000 and all my shards are connecting properly


Compute and store execution metrics after each execution

Description
This pull request changes the way we store and use execution metrics. Previously read from influxdb when using them in the web server, they are now read from a SQL database; this will increase the website performance. To be read from a SQL database, they are first written there at the end of each macrobench run call. The macrobenchmark toolset handles storing metrics to SQL.
A new table metrics has been added. It represents a key/value table with the name of the metric and its value (a float). Each metric is linked to an execution ID and has a unique primary key.
Related issues
Resolves #248.

The new SQL schema is merged. Merging this pull request now.


Applying for GitHub publisher verification for Liquibase GitHub Action

I’m writing regarding the GH Action Liquibase Github Action
Our project is starting to migrate the CI/CD to GH Actions and we are interested to use your Actions.
Providing some context, our Security team requires the "Creator Verified by GitHub" badge to start the internal GHA verification process, due to this we are blocked to use unverified Actions.
We would be grateful if you could start the GH Action verification process, as it would help us greatly.
I believe it must improve your impact in the whole GitHub community as a partner organization and also, you are letting us use your actions.
You can find more helpful information in the following articles from GitHub Docs as a good starting point on the process.
Applying for publisher verification for your organization
About marketplace badges

Alberto - the team was able to look at this quickly and just submitted our organization for verification. I'll keep this ticket open until we hear back. Thanks again for pointing this out.
-Kevin

We got our organization verified, and we ended up needing to join the ISV program to get our GitHub action listed as verified. We applied two days ago and are awaiting the response. Once that is complete, the GitHub Action should show as verified as well.
-Kevin

Hi Kevin,
There's any update about the process?
Regards,
Alberto M.

@kevin-atx @kenta2097, thanks for using Liquibase!  We're about to publicly announce our brand new github actions that support all Liquibase commands, command parameters, and global parameters.  These are also Verified by GitHub! Take a look!
https://github.com/liquibase-github-actions

@jnewton03
The plan is to deprecate Liquibase Github Action on behalf on all these new Actions?

hi @kenta2097 Sorry for the delay.  Yes, we will eventually deprecate the old action.


Problems with WFS and projections

Describe the bug
This is two bugs (or possibly mistakes by me) that I believe have to be closely related but I cannot see how.
I have a working map with working WFS layers in EPSG:27700 crs. See https://swbayproject.com.
I wanted to add a layer in EPSG:4326 and then use WFS-T to add locations from the phone.
When I added a working WFS 1.1.0 layer in EPSG:4326 - it draws the points in the wrong place - i.e. it uses the coords as if they were supplied in 27700 and this puts the points close to the Scilly Isles. I have looked at the packets coming from the server (which is QGIS Server) and they are correct and use the correct SRS name.
When I create the WFS-T request using WFS.writeTransaction() with srsName= 'EPSG:4326' - the node provided has the coords in lon/lat order rather than lat/lon order which is confusing the server.
Fo both of them, I tried different versions of GML and setting the srsName in GML format but nothing seemed to work.
In the end - I just converted the server to EPSG:27700 and converted the data points in script. But this should not be the way that it works.
To Reproduce
You cannot directly reproduce since I had to changed the crs ofthe backend layer
Expected behavior
That Ol should convert correctly between the projections.

ol/format/WFS doesn't automatically transform features into view projection, you need to do it in the loader.  Here's some example code from a StackExchange question (it won't run in codesandbox as the source isn't https)
import 'ol/ol.css';
import Map from 'ol/Map';
import View from 'ol/View';
import WFS from 'ol/format/WFS';
import {Tile as TileLayer, Vector as VectorLayer} from 'ol/layer';
import {bbox as bboxStrategy} from 'ol/loadingstrategy';
import OSM from 'ol/source/OSM';
import VectorSource from 'ol/source/Vector';
import {Stroke, Style} from 'ol/style';
import {fromLonLat, transformExtent} from 'ol/proj'

var vectorSource = new VectorSource({
  loader: function(extent, resolution, projection) {
      var extent4326 = transformExtent(extent, projection, 'EPSG:4326');
      var extent4326yx = [extent4326[1], extent4326[0], extent4326[3], extent4326[2]];
      fetch('http://wms.pcn.minambiente.it/ogc?map=/ms_ogc/wfs/Bacini_idrografici.map' +
          '&service=WFS' +
          '&version=1.1.0' +
          '&request=GetFeature' +
          '&typename=ID.ACQUEFISICHE.BACINIIDROGRAFICI.PRINCIPALI' +
          '&srsname=' + 'EPSG:4326' +
          '&bbox=' + extent4326yx.join(',') + ',EPSG:4326'
      ).then(function(response) { return response.text(); }
      ).then(loadFeatures);
      function loadFeatures(response) {
          var formatWFS = new WFS();
          vectorSource.addFeatures(formatWFS.readFeatures(response, {
              dataProjection: 'EPSG:4326',
              featureProjection: projection
          }));
      }
  },
  strategy: bboxStrategy
});

var vector = new VectorLayer({
  source: vectorSource,
  style: new Style({
    stroke: new Stroke({
      color: 'rgba(0, 0, 255, 1.0)',
      width: 2
    })
  })
});

var raster = new TileLayer({
  source: new OSM()
});

var map = new Map({
  layers: [raster, vector],
  target: document.getElementById('map'),
  view: new View({
    center: fromLonLat([15, 41]),
    maxZoom: 19,
    zoom: 8
  })
});

Thank you for the prompt, detailed and disappointing answer. I find it very strange that this is not part of the core functionality.
I have to say that the documentation could be much clearer about this. I also have to say that there are a number of community answers in e.g. StackOverflow that explicitly state that it does. So there is considerable confusion here.


Vertical bar appearing on all images.

New Issue Checklist

[ ] I have read and understood the CONTRIBUTING guide
[ ] I have read the Documentation
[ ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
ios

Platform Version
8.0

SDWebImage Version
e.g. 4.0.0

Integration Method
e.g. cocoapods

Xcode Version
e.g. Xcode 9.0

Repro rate
e.g.  sometimes 5%

Repro with our demo prj
does it happen with our demo project?

Issue Description and Steps
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.
I have start using SDWebImage cache. But we are facing an issue for some users. The vertical bar are appearing on every image loaded by library. The issue I very hard to reproduce
and we are unable to find out the root cause. Please find attached screenshot.

Any update on this issue?


[FE / Javascript] love namings for boolean starts from is...

https://github.com/YoungLeeHan/YoungleehanKorean/blob/a45be186a1c9aa8ebc7252bde0b215c31f6db9b5/client/src/pages/Cart.js#L20
I love the way of naming booleans like above! That's great.
It may be described on airbnb style guide too.
Everyone! please put name on boolean start with is has or something

Nice to hear this!! We will keep it up!  :)


Recommend Node v8

no issue

update travis.yml

Coverage remained the same at 71.895% when pulling a084334c4c6a2912e3844aa3cba6e1d1c56e1473 on kirrg001:travis-8 into 04b8dbb8550ebef2f739e28ae7cc5df830ea2950 on TryGhost:master.

@kirrg001 should travis be updated to run on v8 too?

@kevinansfield I don't understand the question 🙈travis.yml was updated to run on Node v8 for admin builds.


docstrings for vae_fish.py

We're missing docstrings current for the methods in vae_fish.py.

[ ] get_latents
[ ] sample_from_posterior_z
[ ] sample_from_posterior_l
[ ] get_sample_scale
[ ] get_sample_rate
[ ] get_sample_rate_fish
[ ] classify
[ ] forward

We'd like to have docstrings that look more like this one:
https://github.com/YosefLab/scVI/blob/8147cb6b11717adb7578cf95c97c8ef5ae3c3386/scvi/models/modules.py#L42-L50

commit 18a3c7ec2e318ffb284f5641cf4c3218cbc3b05e


delegate reload to common code

@ryanjbaxter  whenever you have a chance... this came up as I am trying to work on an existing issue (will comment there soon too)

@ryanjbaxter whenever you have a chance... thank you


support multiple image carousel when zoomed in

When there's a grouping of images that you want to be able to individually zoom or traverse through a series without zooming out/in again.
Should also have keyboard support when implementing this.

:+1:
And also swipe right/left support on touch screens. (will have to deal with the close on scroll feature)


Pico

This pull request adds the support for the Raspberry Pi Pico.
The supported board is the original board from the Raspberry Pi Foundation.

A environment is added to the platformio.ini file
A MFBoards.h file is added for the board specific definitions
After writing to the eeprom these changes have to be commited, accordingly MFEEPROM.cpp/h is modified
Pico requires it's own servo lib. Therefore the servo lib for Atmels is moved from the standard environment to the boards environment from the Atmel boards
The Pico servo lib gets initialized with the same range as for the Atmels
The unique ID from the NOR flash gets used instead of a random serial number
The device buffer gets initialized with the correct size for this (and other) architectures.

Fixes #225

YES!!!!!!!!!!!!!!!!!!!!!!!!!!!!


Flux will not update environment when a new image is pushed

Describe the bug
I am deploying Flux through Helm on to a Kubernetes cluster and Flux is not updating and re-deploying new images properly. When a new image is pushed onto the docker registry (Nexus Repository Manager), Flux sees this new image but does not update the existing container. I am also using semantic versioning to check the image tags (e.g imageExample:1, imageExample:2, etc)
Previously, this was working a few days ago and there was no problem at all. I wonder if it is the new patch causing this bug.
Expected behavior
I expect Flux to be able to update my existing container with the new image and since I am using semantic versioning, it should not check the timestamp at all.
Logs
ts=2019-06-19T17:15:25.807882143Z caller=images.go:107 component=sync-loop workload=dev:helmrelease/********** container=container repo=********** pattern=semver:* current=********** warning="image with zero created timestamp" current="********** (0001-01-01 00:00:00 +0000 UTC)" latest="********** (0001-01-01 00:00:00 +0000 UTC)" action="skip container"
Additional context
Add any other context about the problem here, e.g

Flux version: 1.13.0
Helm Operator version: 0.92

I agree that if you're using semantic versioning, the timestamp shouldn't matter for deciding which image is more recent.
The reason for the check is slightly broader than that: a missing timestamp can indicate that the image tag in question doesn't have a (valid) manifest. That ought to be a distinct and detectable case, but -- I forget exactly why -- it's not.
 Or is a secondary problem that fluxd isn't picking up their timestamps correctly?

The docker image has the Created field which has a valid timestamp, however the LastTagTime in the Metadata object is set to 0 (as shown below).
"Metadata": {
"LastTagTime": "0001-01-01T00:00:00Z"
}
I am wondering if this is the cause of the problem? Was Fluxd looking at the Created field in the manifest before and after the patch it is looking at this instead?

fluxd doesn't look at the LastTagTime, no; just at the Created timestamp and the labels.
#2175 implements the expected behaviour; closing on that basis.


gems: bundle update

Went through and pinned a few versions

rubocop - to avoid deciding on new rules
govuk_frontend_toolkit - no idea what 8.x changes
site_prism - because it doesn't like the most recent capybara

then just did an all round bundle update

if we're happy with this, should probably turn on dependabot
and just do daily dependency updates that way.

At the moment me and Clive are working to get rid of the deprecated front-end gems:
https://github.com/ministryofjustice/moving-people-safely/pull/543

@cesidio that's fine,
just pinned it to avoid it doing an update to 8.x

@cesidio would be good to take another look

closing in favour of #572


Management command help text is inconsistent/not useful

The help text for the management commands could be a lot more helpful.
   MANAGEMENT COMMANDS:
     config, cf  set configuration for an object
     create, c   create
     delete, d   delete command
     get, g      get command
     inspect, i  inspect command
     list, ls    list command
     unset, un   unset command
     update, up  update command
     use, u      use command

config and create are inconsistent with the others, and the others don't give any suggestion as to how/why you would use them.

Yeah, aware of this but didn't want it to block the overall command delivery. I've also been talking to @michael-w-williams about getting him involved in helping with our text, also about externalising the help text to potentially enable generation of online CLI reference docs.


Context Manager to modify config.

Test will fail as _validate_config, actually pop values from config.

What's the use case you want this for?
If we're doing programmatic modification of config files, I'd like to look into round-tripping parsers (e.g. the iniparse module, but preferably something that's still active). With the standard library configparser module, any formatting or comments you have in the config file is lost when you overwrite it. And comments are one of the main reasons to use ini instead of JSON.

If we're doing programmatic modification of config files,

Yes, programatic modification.
Would you be ok in just splitting the validate logic out, so that I can use a rough programatic way to modify ?
We can also have that in flit (private) and have round-tripping as a later feature.

You mean splitting validate into a separate function from reading
configuration? Sure, I don't see a problem with that.

You mean splitting validate into a separate function from reading
configuration? Sure, I don't see a problem with that.

Done, removed the context manager and change the validate method not to modify the config object it got as parameter.

Thanks. At the airport now, but I'll try to have a look this evening from
the hotel.

Ping BTW.

Thanks


Worker tolerances, possible --dry-run for create-pipeline?

From a user:

Hi all,  does anyone know of a way to set tolerances for pipeline workers?  Our situation is that we have an instance group composed of high performance (read expensive!) nodes that scales down to 0 when there is no k8s pod pressure.   We only want pipeline workers to run on this instance group and not any of the other services in the cluster. This is usually the case and there aren't any problems, but occasionally a service will be evicted and end up re-deploying on this worker instance group when a job is running.  This prevents the instance group from scaling down to 0 and costs :moneybag: over the longer term. We would be like any taints that we have set on nodes in the IG to be tolerated by Pachyderm workers but can't figure out how to set these tolerances.  Should this be in the pipeline spec, is there another way to set tolerances, or is there a completely different approach that gets us to where we want to be? Thanks :slightly_smiling_face:

A possible solution that was suggested here was adding a --dry-run option for create-pipeline and possibly update-pipeline that would allow users to modify certain k8s primitives before deploying pipelines. However, I could definitely see some scenarios where this would be an "unsafe" route to deploying a pipelines. That is, Pachyderm could no longer make certain guarantees about how pipelines were deployed, but maybe that is a trade off some users would like to make.

@dwhitena Thanks for following this up.  Yes, I agree it would be unsafe and would possibly forfeit any Pachyderm guarantees, but taking this into account it would be a useful 'power user' feature that would increase the flexibility of Pachyderm.
The workaround I'm going to look at goes something along these lines: kubectl get -o yaml rc/pipeline-my-pipeline-v1 | my-update-script | kubectl apply -f -.
I would also add run-pipeline to the commands that could benefit from a --dry-run option.

Getting --dry-run to work for pipelines would require a decent sized architectural shift. Not impossible but kind of difficult and it doesn't seem like that's the easiest way to solve this. Much easier would be to just added a section for tolerances like we've done for other k8s fields in the past.

@jdoliner Adding a tolerances section would solve the issue in this case, although the --dry-run option would be nice to have in the future.

Another user reports a similar use case (tolerances + affinity)
Right, I did that to the resources that `pachctl deploy --dry-run` generates and you can see in the `kubectl get pods` output that all pods but one are on the right node. The misbehaving pod was created with the command `pachctl create-pipeline -f edges.json` that doesn’t have a `--dry-run` option to spit out the resources it would create and allow me to set `affinity` and `tolerations` to achieve what you are suggesting.
The default node scope for a google backed k8s cluster is `storage-ro` so I believe this would impact anyone trying to install  Pachyderm on an existing google cluster.

Tolerances are now possible in addition to other scheduling fields on pipelines. We've also got a stop gap solution for arbitrary modifications to the pipeline in the pod_patch field. The path to a --dry-run flag for pipelines is most likely going to be CRDs, that work is being tracked in #3345, so I'm going to close this in favor of that.


Fix and update the calendar app

Fix the calendar app so it shows data from local db

[x] Data in the local db
[x] The documentation adjusted to the new local database, meaning no hdi container

Send approved appointments to the S4HANA mock server

[x] Added transaction to join already existing read request

Change the vacations (SFSF) from 2019 to current year
This is now done in the mock server
Changed the requests (both S4HANAand SFSF) to include the fixed year timesheet entries
Changed the date parsing function from the transform appointments function to change the fixed year into current year
Change the appointments from 2020 to current year

[ ] Make the year variable in the local db

Additional documentation

[x] Documentation mentions the setup of the mock servers SEE PULL REQUEST

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: marikaner:x: jjtang1985:x: CharlesDuboisSAPYou have signed the CLA already but the status is still pending? Let us recheck it.


3D point placement bug

To replicate,
Enable 3D rendering for MRHead.nrrd, adjust volume property.
Mouse mouse to 3D rendering window, hit p, see that you cannot create a point without moving the mouse around.
Replicates all the time on latest windows stable.
While this is not a terrible bug, I think we should change the behavior of P keystroke, not to go into Place mode, but actually place the point where the cursor is. It is more convenient (and intuitive) to adjust your rendering first, position your cursor, and create the point at that location.

closed via #133


Containers should get deployed to the right zone when creating service with volume using KmsKeyId and VolumeID

Rancher Versions:
Server: 1.6.0-rc5
**Docker Version:**1.12.6
**OS and where are the hosts located? (cloud, bare metal, etc):**Cloud
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB): Single node
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) Cattle
Steps to Reproduce:

Deploy rancher-ebs catalog on a setup with AWS-hosts
Create an encrypted key in east zone. Create a service with volume using this key in a setup with hosts in west zone and east zone. Service creation fails as the keys are from east zone.

version: '2'
services:
  foo:
    image: ubuntu
    stdin_open: true
    volumes:
    - bartestabc:/mydata
volumes:
  bartestabc:
    driver: rancher-ebs
    driver_opts:
      size: '10' # specify the size for EBS volume. This is required.
      volumeType: 'gp2' # specify the volume type
      iops: '1000' # specify the iops
      encrypted: true
      kmsKeyId: 'arn:aws:kms:us-east-1:605812595337:key/654f82eb-5ba7-4f40-92ba-81b8639e0f2f'

A volume ID from east zone cannot be used with hosts in west zone

version: '2'
services:
  coo:
    image: ubuntu
    stdin_open: true
    scale: 2
    volumes:
    - soumyanewawsvolume:/mydata
volumes:
  soumyanewawsvolume:
    driver: rancher-ebs
    driver_opts:
      volumeID: 'vol-0e9f109d2dc24ca29'

Note:
Using ec2_az: zone in driver options will schedule the containers to the appropriate zone currently

This is as expected and by design. The instructions document the requirement of using ec2_az when using these options.


Change the docker config to optimize for development on Mac machines.

Add xdebug configs.
Add gd lib use to testing upload image(UploadedFile::fake() func need it)
Change file sync mode to :delegated Refer
You yarn watch directly inside blog-server container to remove syncing bundled js/css bundle file from node server in to blog-server

Thanks for the PR!
But I don't want xdebug by default in this project. Lots of people don't use it myself included.
Why do you think delegated is better ? The performance are pretty much the same but with less guarantee right ?
Imo a container should be responsible for only one thing. PHP and node should be splitted.

I know it. So I created a new file and named it * .dev.
On my computer and testing a month ago, I got speed up 3x times when use delegated
When use delegated that less guarantee, so me and my colleague got the bundled js files isn't applied when he and I change the js files in sometimes.
Remember it is used only for developer purposes.

I saw yep.
I will check for the delegated option. Last time I tried it was not significant : https://guillaumebriday.fr/docker-ameliorer-les-performances-avec-le-cache
Thanks !


Upgrade to lxc 3.2.1 fails

I was using Ubuntu 18.04 with stock lxc, not lxd. Now I need ipvlan support so I erased all packages with the word "lxc" in the name. Then I downloaded https://linuxcontainers.org/downloads/lxc/lxc-3.2.1.tar.gz. I did the usual make,install, etc. lxc-start --version shows the correct version. But lxc-ls shows no containers exist, when in fact I do have 20 containers in the box. The tar ball does not really install LXC. Can somebody fix the tar ball so it does what it needs to do? I also did a lxc-update-config on one of my containers, and it worked, but still lxc-ls shows nothing.

Filled against the wrong project. What you're describing would be consistent with a manually built LXC without the appropriate paths being passed to configure.
In that case it would likely look for containers in /usr/local/var/lib/lxc or something.

is there any documentation on how to pass the right parameters to the ./configure ?

parse.c: lxc_file_for_each_line_mmap: 142 Failed to parse config file "/usr/local/var/lib/lxc/xxx-20/config" at line "lxc.net.1.ipvlan.flags=bridge"

lxc.net.1.type=ipvlan
lxc.net.1.ipvlan.mode=l3
#lxc.net.1.ipvlan.flags=bridge
lxc.net.1.link=eth0
lxc.net.1.name = eth1
lxc.net.1.flags=up
lxc.net.1.ipv4.address = <IP_ADDRESS>/24
The network type ipvlan does no work. It creates an interface with the same mac address as the linked interface from the host, and that is what I need, but there is no communication through.
if I try this:
arping -I eth1 xx.x.x.1
ARPING xx.x.x.1
arping: libnet_write(): libnet_write_link(): only -1 bytes written (No buffer space available)


#12527: refactor slice

-use exclusive ends and move all the list splicing features to ttnn.slice
-add support for negative starts
-add negative starts and ends support to ttnn.slice
-move most pre-processing to C++
-refactor C++ code
-remove skip on bert ttnn.slice unit tests
Ticket
Link to Github Issue
Problem description
ttnn.slice and the tensor[..start:end:step] format had differences in feature support. Refactor slice to improve coverage.
What's changed
Describe the approach used to solve the problem.
Summarize the changes made and its impact.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

The description says to use inclusive ends but the diffs show slice now uses exclusive ends?

The description says to use inclusive ends but the diffs show slice now uses exclusive ends?

The description says to use inclusive ends but the diffs show slice now uses exclusive ends?

Yeah it's exclusive, made a mistake in the description

LFG, very involved change good job @sjameelTT


Pt 156600645 resolve name at current height

Resolves names for SpendTx at current height while mining and validating.

account_pubkey pointer from naming system is used
if name is found but no account_pubkey, the transaction is rejected
if name is not valid, the transaction is rejected

https://www.pivotaltracker.com/story/show/156600645

as discussed with @velzevur, maybe we should specify explicitly if we want to send a spend_tx (or others using name resolvement) to a pubkey or name, as the binary handling could lead to conflicts.

@thepiwo ...that would be huge change. We are just after adding payload to spend. Maybe we can do short call about it? I might be to fast with that feature.

@thepiwo contracts have more logic and that would be another mechanism to drive it. For regular transaction I don't see the point.

@sennui @happi ok, I'd propose to squash and keep this to the scope it is. And then have various other resolvements as follow up task for me, so could you review?

I understand not suitable to merge yet, and that @thepiwo may address comment. I take the liberty of labeling as WIP for easing filtering.

Yes, thank you @lucafavatella I will clarify my state tomorrow in the call.

so, I will close this for now and include all possible name resolvements and change requests in a future PR


Added on awesome-rollup

Added on awesome-rollup: https://github.com/rollup/awesome/pull/27

Maybe we should add it in Readme when merged.


New version using cbapi-python bindings!

looks good, merging in - will prepare a new release of cbapi with you today


separator

need natvie way for add separator title
	addSeparator( f: GUI, title?: string ) {
		const separator = f.add( { l:100 }, 'l' );
		const el = separator.domElement;
		const style: Partial<CSSStyleDeclaration> = {
			borderTop:`1px solid #aaaaaa50`,
			margin: '6px 10%',
			justifyContent: 'center',
			fontSize: 'x-small',
			paddingBottom: '6px',
			opacity: '0.7',
		};
		Object.assign( el.style, style );
		while( el.firstChild ) el.removeChild( el.firstChild ); // remove all childs
		// add title in middle
		if( title ) {
			const titleDiv = document.createElement( 'div' );
			titleDiv.style.position = 'sticky';
			titleDiv.style.backgroundColor = 'inherit';
			titleDiv.innerText = title;
			separator.domElement.appendChild( titleDiv );
		}
	}

ex:
		const f0 = gui.addFolder( 'camera' );
		( this.addSeparator( f0, 'BASE' ) );
		f0.add( obj, 'sceneW' ).listen().disable();
		f0.add( obj, 'sceneH' ).listen().disable();

I had a feature like this in mind at one point, but I felt like you could accomplish the same things with a folder. I'm curious—why don't you want to use folders for "BASE" and "FOV" in your screenshot? Is it because they're already in a folder? Ultimately I left "separators" out to keep the library small, but I'd consider adding them if there were enough requests.

these purely aesthetic :)
for me, folder represente a coupling property instance inside a class. (example new component tranform, position,euler....)
and title separator is to represent field props groups,categories...
Some library have a design pattern type GodClass, and i feel like i need to sort some props.


fix: various multifile editor bugs

The issue was caused by the shift to functional components, since the Editor relied a lot on internal state (not React state) that needed to be present when the monaco editor mounted.  Using React state meant those values existed, but before editorWillMount and editorDidMount were called.
This PR handles everything with useRef instead, since that can be updated on the fly without triggering a new render.
Should fix #42806

Small bug, I stumbled on in: /learn/responsive-web-design/basic-html-cat-photo-app/part-66
Uncaught Error: Illegal value for lineNumber
    at TextModel.getLineContent (textModel.js:521)
    at positionsToRange (editor.tsx:1021)
    at eval (editor.tsx:796)
    at Array.map (<anonymous>)
    at decorateForbiddenRanges (editor.tsx:795)
    at editorWillMount (editor.tsx:275)
    at MonacoEditor.editorWillMount (editor.js:118)
    at MonacoEditor.initMonaco (editor.js:109)
    at MonacoEditor.componentDidMount (editor.js:53)

No worries. Thanks for all you've done to improve the editor. We're gradually getting it into shape.

@Sembauke yeah, it's definitely hard to understand.
There's not really that much about this which has to do with the multiple files - it's just the useRefs that hold various parts of the editor's state.  We could lift that up into the multifile editor and pass it in as props, though.
We could also pull the config out to separate .json files.


GC-109/add-pending-state-to-dropzone

JIRA
GC-109
Description
In order to be able to work on GC-109 in dashboard-vue, I first needed to be able to set uploading or pending as a status for the dropzone. This way, we can show the creative that was uploaded is still validating.
Screenshots
You can test this by setting the status prop in the Dropzone story:

I don't see a change in the package lock - but now that i think about it i guess it's not necessary as the github runners will update it?


New Casks: beaTunes and Xpra

beaTunes is an advanced music application for Windows and OS X that lets you analyze, inspect, and play songs—and create compelling playlists.
Xpra is 'screen for X', and more: it allows you to run X programs, usually on a remote host and direct their display to your local machine. It also allows you to display existing desktop sessions remotely.

In the future, please submit separate pull requests for each cask, as more often than not this type of pull request brings problems with one or more of them, and it halts the inclusion of the other ones.
In this case, for xpra, seeing as url doesn’t point to a specific version, this cask should use version :latest and sha256 :no_check. See an example.

Thank you for the contribution. It needed some fixes, so they were made in c82b1a90a0d4e726131a7a5cf2d43a5f16287c35. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

Thanks for the info! :) I actually intended to do a separate pull request, but when I clicked on pull request github brought this one automatically and added the latest commit to it. Is it normal behavior when a pull request is open perhaps?


Made spin gate names consistent

The naming between the spin gates, the decorated circuit, and the spin gate display name has been made consistent. This fixes #21

Sorry, I tried to remove my above approval because I spotted some points after the initial review...

Regarding the discussion in #21, a point that Fred made is that the gate names (which eventually end up in the JSON via circuit_to_cold_atom) should be all lowercase like the circuit instructions, so rlx instead of rLx. I would agree with this.

Fred also suggested to remove the r from all two-spin gates, in order not to clutter the notation too much. I'd also agree with this.

Once we agree and this is implement we can merge this and close #21.

I found one more place where the names should be changed which is the configuration of the collective_spin_simulator backend. I updated that in the previous commit.

LGTM.


Keep app name consistent

Initially i added this like a meta tag, but now i think it is able to change completely :)


fix: CSSBuilder removes valid CSS class names provided by external CSS frameworks

🐛 Bug Report
The CSSBuilder will remove valid CSS classes from the class list of components. For instance, the following are all valid class names provided by TailwindCSS:

min-h-[16px]
p-[2rem]
bg-[#ff0000]
bg-red-500/50
w-11/12
bg-[#ff0000]/50
my-abitrary-value-[#ff0000]/100

💻 Repro or Code Sample
    [Fact]
    public void CssBuilder_AddValidUserClass()
    {
        // Arrange
        var expected = "ml-2 inline-block min-w-[16px]";
        var cssBuilder = new CssBuilder(expected);

        // Act
        var actual = cssBuilder.Build();

        // Assert
        Assert.Equal(expected, actual);
    }

i.e.
<FluentIcon Value="new Icons.Regular.Size16.Settings()" OnClick="Edit" Class="ml-2 inline-block min-w-[16px]" />

🤔 Expected Behaviour
The class list should read class="ml-2 inline-block min-w-[16px]", with all valid CSS classes intact.
😯 Current Behaviour
The class list reads class="ml-2 inline-block", with min-w-[16px] removed, even though it is valid.
💁 Possible Solution
The regex used here should read:
^[a-zA-Z_][a-zA-Z0-9_-]*(\[[^\]]+\])?(\/\d{1,3})?$

Explanation

^: Asserts the start of the string.
[a-zA-Z_]: Ensures the first character is a letter (a-z, A-Z) or an underscore (_).
[a-zA-Z0-9_-]*: Ensures subsequent characters are letters, digits, hyphens (-), or underscores (_).
([[^]]+])?: Optionally matches a part that starts with [, followed by one or more characters that are not ], and ends with ].
(/\d{1,3})?: Optionally matches a / followed by one to three digits, representing the opacity value (to cover 100 as well).
$: Asserts the end of the string.

Example Matches

min-h-[16px]
p-[2rem]
bg-[#ff0000]
bg-red-500/50
w-11/12
bg-[#ff0000]/50
my-abitrary-value-[#ff0000]/100

I have prepared a PR with this fix for approval.
🔦 Context
We use FluentUI heavily within many of our projects, and there is a large overlap with FluentUI, and Tailwind. The Regex at current will disallow the use of a large amount of classes that Tailwind offers, including making any class "important", using any negative values for margins, padding, etc., using any opacity modifiers, and using any arbitrary values. The changes made to this regex addresses all of these issues, and more. While it is not an exhaustive fix for everything that any CSS framework will offer, it will fix that vast majority of use-cases.
Currently, FluentUI actively fights against frameworks such as Tailwind, when it should not need to, or want to. While I have focussed on Tailwind here within our use-case, other similar frameworks for CSS utility classes will suffer the same.
🌍 Your Environment

OS & Device: Windows 11
Browser: Firefox, Chrome, Opera, and Edge.
.NET and Fluent UI Blazor library Version [e.g. 8.0.3 and 4.8.0]

This issue has just been discussed here: #2251

I'm going to close this one and keep only one (the first).


Support a machines/default directory, for first time boot of new server

The API server returns the Spec for machine "default" if it can't find a specific Spec for that machine.
data/
  machines/
    52:54:00:20:17:f9/
      machine.json
    default/
      machine.json

This allows me to boot new servers for the first time using a default configuration, and discover their MAC address so I can create a specific configuration.

Booting new machines with a default definition to discover their attributes feels a bit dirty, but I was using that approach too (or just running bootcfg with -log-level-=debug). I agree this is of practical convenience for small clusters or random spare hardware whose spec sheets aren't readily available.

Feature added as #16


thread 'tokio-runtime-worker' panicked at /cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwest-0.11.18/src/into_url.rs:80:14: a parsed Url should always be a valid Uri: InvalidUri(TooLong)

This error is facing me after i have provided the url and word list it finds for me some hidden pages and then it throws me this error, I don't know if the websites made this url to prevent from finding thier hidden files or it is just from Feroxbuster tool.
Here is a screenshot of the error:

Is there is any solution?


Bind system probe and security agent configs to env

What does this PR do?
Binds internal profiling configs to environment variables.
Motivation
This enables profiling in the SMP environment.
Ref: https://github.com/DataDog/datadog-agent/pull/19453

@paulcacheux You're totally right. Thanks for the review, I'll close this.


fix: struct field don't push down to TableScan

Which issue does this PR close?

Closes #8735
Rationale for this change
when debug #8735, I find not only the case in #8735 don't push down, we have other case don't push down
for example
DataFusion CLI v34.0.0
❯ create table t(a int, b int, c int);
0 rows in set. Query took 0.014 seconds.

❯ explain select -a from t;
+---------------+-------------------------------------------------+
| plan_type     | plan                                            |
+---------------+-------------------------------------------------+
| logical_plan  | Projection: (- t.a)                             |
|               |   TableScan: t projection=[a, b, c]             |
| physical_plan | ProjectionExec: expr=[(- a@0) as (- t.a)]       |
|               |   MemoryExec: partitions=1, partition_sizes=[0] |
|               |                                                 |
+---------------+-------------------------------------------------+
2 rows in set. Query took 0.016 seconds.

What changes are included in this PR?
add more case to outer_columns_helper.
Are these changes tested?
yes, add more tests
Are there any user-facing changes?

the root reason maybe in below code
https://github.com/apache/arrow-datafusion/blob/4e4059a68455fbc14f04902c76acbcd258b7f2ef/datafusion/optimizer/src/optimize_projections.rs#L771-L775
I'm not sure why we handle it this way. I tried commenting out this line, and all the tests still passed.


Get back in touch with resident from Capitola

Schedule day to do water quality testing

closing this! spoke to the homeowner on 3/1. going to send her an email to schedule best day/time in March to do water quality testing


support additional header name~value pairs

Currently in the go/storage/needle.go file, NewNeedle() do not handle additional name~value pairs in headers.
We can have one additional bit in Needle.Flags byte, to mark that we have a string storing additional name~value paris.

I think I can help. Which request will the additional pairs be returned for, a GET or HEAD request for the file, or a special URL request? More details can be helpful. Thanks.

Just GET and HEAD requests.

Is this done? @sparklxb


execSelectionInTerminal to run in now active terminal

I would like that the comman "python.execSelectionInTerminal" to run in the terminal that is open.
Now the default behavior is to track the terminal opened by the extension and always run in this one.
But the change would let me open many Python Terminals and run in the open one with my key bindings.

Is this already possible to set ? if so, how ?
Thanks for the help

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

Thanks,
The idea of using multiples Python Iterative Terminals is already in use in Python Development in the  PyCharm  and RStudio of my colleagues. And its very useful. But would like to keep using VSCode.
Can use the "runSelectedInTerminal" from vscode multiple languages but this command from python extension works better with the indentation. But just works with the one terminal he created itself.
Lets See if someone thinks the same.

Thank you to everyone who upvoted this issue! Since the community showed interest in this feature request we will leave this issue open as something to consider implementing at some point in the future.
We do encourage people to continue 👍 the first/opening comment as it helps us prioritize our work based on what the community seems to want the most.

This is difficult to implement ?
Would change my life in debugging my code.


feat: Support different merge conditions in athena.to_iceberg function

Feature or Bugfix

Feature

Detail
Sometimes, when inserting new data into an iceberg table it may be necessary to ignore existing data on some fields and load only the new ones, to avoid having unwanted overwrites on all columns of the dataset.
In this case a check has been added on the type of merge you want to do, by default an update is done, or you can choose to ignore duplicate entries and go into insert with only the new ones.
Use case:
df1:
| title   |   year |    gross |
|:--------|-------:|---------:|
| Dune    |   1984 | 35000000 |
| Fargo   |   1996 | 60000000 |

df2:
| title   |   year |     gross |
|:--------|-------:|----------:|
| Dune    |   2021 | 400000000 |
| Fargo   |   1996 |  60000001 |

case 1: UPDATE (default)
wr.athena.to_iceberg(..., merge_cols=["title", "year"])

out:
| title   |   year |     gross |
|:--------|-------:|----------:|
| Dune    |   1984 |  35000000 |
| Fargo   |   1996 |  60000001 |
| Dune    |   2021 | 400000000 |

case 2: IGNORE
wr.athena.to_iceberg(..., merge_cols=["title", "year"], merge_condition="ignore")

out:
| title   |   year |     gross |
|:--------|-------:|----------:|
| Dune    |   1984 |  35000000 |
| Fargo   |   1996 |  60000000 |
| Dune    |   2021 | 400000000 |

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

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 83621d9b729d037d185fe34be2f2caebc5828f33
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 83621d9b729d037d185fe34be2f2caebc5828f33
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: cafd0d972c71d992ab4cf3992d81e180702b487b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


fix: restore /api/v0/add in WebUI in Brave

This PR:

switches to async iterator version of ipfs.cat introduced to js-ipfs in https://github.com/ipfs/js-ipfs/pull/2517 and ensures Node streams are replaced by deterministic version of readable-stream

this restores upload functionality via /api/v0/add and closes #757

as a side effect:

we remove override and switch to async iterator versions of delegated routing modules
switch override to latest hapijs release with support for Chrome Apps / WebExtension (introduced in https://github.com/hapijs/hapi/pull/3946)

unblocks other PRs related to Brave and js-ipfs :tada:

Tests pass, merging this fix to unblock other PRs


Python Error

Hi,
It seems like I have a two Python version installed, and I wonder if below error might be what cause it. Would you be able to help?
ubuntu$ python --version
Python 2.7.15+

ubuntu$ python3.5 --version
Python 3.5.6

With Sudo
ubuntu$ sudo trello-full-backup -B -L -C -m -o
==== Backup initiated
Backing up to: 2019-08-06_10-49-20_backup
Incremental: False
Tokenize: False
Backup my boards: True
Backup organization boards: True
Backup closed board: True
Backup archived lists: True
Backup archived cards: True
Attachment size limit (bytes): 100000000
====

Traceback (most recent call last):
  File "/usr/local/bin/trello-full-backup", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.5/site-packages/trello_full_backup/__init__.py", line 5, in main
    cli()
  File "/usr/local/lib/python3.5/site-packages/trello_full_backup/backup.py", line 302, in cli
    org_boards_data['me'] = requests.get(my_boards_url).json()
  File "/usr/local/lib/python3.5/site-packages/requests/models.py", line 897, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/local/lib/python3.5/json/__init__.py", line 319, in loads
    return _default_decoder.decode(s)
  File "/usr/local/lib/python3.5/json/decoder.py", line 339, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/local/lib/python3.5/json/decoder.py", line 357, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Without Sudo
ubuntu$  trello-full-backup -B -L -C -m -o
Traceback (most recent call last):
  File "/usr/local/bin/trello-full-backup", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.5/site-packages/trello_full_backup/__init__.py", line 5, in main
    cli()
  File "/usr/local/lib/python3.5/site-packages/trello_full_backup/backup.py", line 276, in cli
    mkdir(dest_dir)
  File "/usr/local/lib/python3.5/site-packages/trello_full_backup/backup.py", line 28, in mkdir
    os.mkdir(name)
PermissionError: [Errno 13] Permission denied: '2019-08-06_10-49-35_backup'

For me this error was showing up as well, so I opened backup.py and printed out API_KEY and API_TOKEN values, and turns out it was not getting them from environment variables for some reason. So I just edited the file in place, and it worked. I also had to fix the "sanitize_file_name" and made it use production proven werkzeug.utils.secure_filename instead, because otherwise it was producing bad filenames.
You can also find backup.py file inside your python folder and replace it with this. You will also need to pip install werkzeug and write your api and token into the code.
I'm not yet familiar with how to contribute to github project, but author or anyone else can implement these changes. I would also suggest just using two more arguments for token and api key instead of environment variables. Or at least allowing it as an option.
Permission denied error is because you're not specifying the output path, and it writes to the directory you're in by  default (I think) and most likely your user does not have access to that dir, that's why it  fails without sudo.
import sys
import itertools
import os
import argparse
import re
import datetime
import requests
import json
from werkzeug.utils import secure_filename

# Do not download files over 100 MB by default
ATTACHMENT_BYTE_LIMIT = 100000000
ATTACHMENT_REQUEST_TIMEOUT = 30  # 30 seconds
FILE_NAME_MAX_LENGTH = 100
FILTERS = ['open', 'all']

API = 'https://api.trello.com/1/'

# Read the API keys from the environment variables
API_KEY = 'YOUR API KEY' #os.getenv('TRELLO_API_KEY', '')
API_TOKEN = 'YOUR TOKEN' # os.getenv('TRELLO_TOKEN', '')

print ('API_KEY', API_KEY)
print ('API_KEY', API_TOKEN)

auth = '?key={}&token={}'.format(API_KEY, API_TOKEN)

def mkdir(name):
    ''' Make a folder if it does not exist already '''
    if not os.access(name, os.R_OK):
        os.mkdir(name)

def get_extension(filename):
    ''' Get the extension of a file '''
    return os.path.splitext(filename)[1]

def get_name(tokenize, real_name, backup_name, element_id):
    ''' Get back the name for the tokenize mode or the real name in the card.
        If there is an ID, keep it
    '''
    name = backup_name if tokenize else sanitize_file_name(real_name)
    return '{}_{}'.format(element_id, name)

def sanitize_file_name(name):
    """
    Normalizes string, converts to lowercase, removes non-alpha characters,
    and converts spaces to hyphens.
    """
    return secure_filename(name)
    #return re.sub(r'[<>:\/\|\?\*\'\"]', '_', name)[:FILE_NAME_MAX_LENGTH]

def write_file(file_name, obj, dumps=True):
    ''' Write <obj> to the file <file_name> '''
    with open(file_name, 'w', encoding='utf-8') as f:
        to_write = json.dumps(obj, indent=4, sort_keys=True) if dumps else obj
        f.write(to_write)

def filter_boards(boards, closed):
    ''' Return a list of the boards to retrieve (closed or not) '''
    return [b for b in boards if not b['closed'] or closed]

def download_attachments(c, max_size, tokenize=False):
    ''' Download the attachments for the card <c> '''
    # Only download attachments below the size limit
    attachments = [a for a in c['attachments']
                   if a['bytes'] is not None and
                   (a['bytes'] < max_size or max_size == -1)]

    if len(attachments) > 0:
        # Enter attachments directory
        mkdir('attachments')
        os.chdir('attachments')

        # Download attachments
        for id_attachment, attachment in enumerate(attachments):
            extension = get_extension(attachment["name"])
            # Keep the size in bytes to backup modifications in the file
            backup_name = '{}_{}{}'.format(attachment['id'],
                                           attachment['bytes'],
                                           extension)
            attachment_name = get_name(tokenize, attachment["name"],
                                       backup_name,
                                       id_attachment)

            # We check if the file already exists, if it is the case we skip it
            if os.path.isfile(attachment_name):
                print('Attachment', attachment_name, 'exists already.')
                continue

            print('Saving attachment', attachment_name)
            try:
                content = requests.get(attachment['url'],
                                       stream=True,
                                       timeout=ATTACHMENT_REQUEST_TIMEOUT)
            except Exception:
                sys.stderr.write('Failed download: {}'.format(attachment_name))
                continue

            with open(attachment_name, 'wb') as f:
                for chunk in content.iter_content(chunk_size=1024):
                    if chunk:
                        f.write(chunk)

        # Exit attachments directory
        os.chdir('..')

def backup_card(id_card, c, attachment_size, tokenize=False):
    ''' Backup the card <c> with id <id_card> '''
    card_name = get_name(tokenize, c["name"], c['shortLink'], id_card)

    mkdir(card_name)

    # Enter card directory
    os.chdir(card_name)

    meta_file_name = 'card.json'
    description_file_name = 'description.md'

    print('Saving', card_name)
    print('Saving', meta_file_name, 'and', description_file_name)
    write_file(meta_file_name, c)
    write_file(description_file_name, c['desc'], dumps=False)

    download_attachments(c, attachment_size, tokenize)

    # Exit card directory
    os.chdir('..')

def backup_board(board, args):
    ''' Backup the board '''

    tokenize = bool(args.tokenize)

    board_details = requests.get(''.join((
        '{}boards/{}{}&'.format(API, board["id"], auth),
        'actions=all&actions_limit=1000&',
        'cards={}&'.format(FILTERS[args.archived_cards]),
        'card_attachments=true&',
        'labels=all&',
        'lists={}&'.format(FILTERS[args.archived_lists]),
        'members=all&',
        'member_fields=all&',
        'checklists=all&',
        'fields=all'
    ))).json()

    board_dir = sanitize_file_name(board_details['name'])

    mkdir(board_dir)

    # Enter board directory
    os.chdir(board_dir)

    file_name = '{}_full.json'.format(board_dir)
    print('Saving full json for board',
          board_details['name'], 'with id', board['id'], 'to', file_name)
    write_file(file_name, board_details)

    lists = {}
    cs = itertools.groupby(board_details['cards'], key=lambda x: x['idList'])
    for list_id, cards in cs:
        lists[list_id] = sorted(list(cards), key=lambda card: card['pos'])

    for id_list, ls in enumerate(board_details['lists']):
        list_name = get_name(tokenize, ls['name'], ls["id"], id_list)

        mkdir(list_name)

        # Enter list directory
        os.chdir(list_name)
        cards = lists[ls['id']] if ls['id'] in lists else []

        for id_card, c in enumerate(cards):
            backup_card(id_card, c, args.attachment_size, tokenize)

        # Exit list directory
        os.chdir('..')

    # Exit sub directory
    os.chdir('..')

def cli():

    # Parse arguments
    parser = argparse.ArgumentParser(
        description='Trello Full Backup'
    )

    # The destination folder to save the backup to
    parser.add_argument('-d',
                        metavar='DEST',
                        nargs='?',
                        help='Destination folder')

    # incremental mode don't download the
    # already existing attachments
    parser.add_argument('-i', '--incremental',
                        dest='incremental',
                        action='store_const',
                        default=False,
                        const=True,
                        help='Backup incrementally (existing folder)')

    # Tokenize the names for folders and files
    parser.add_argument('-t', '--tokenize',
                        dest='tokenize',
                        action='store_const',
                        default=False,
                        const=True,
                        help='Name folders and files using the shortlink')

    # Backup the boards that are closed
    parser.add_argument('-B', '--closed-boards',
                        dest='closed_boards',
                        action='store_const',
                        default=0,
                        const=1,
                        help='Backup closed board')

    # Backup the lists that are archived
    parser.add_argument('-L', '--archived-lists',
                        dest='archived_lists',
                        action='store_const',
                        default=0,
                        const=1,
                        help='Backup archived lists')

    # Backup the cards that are archived
    parser.add_argument('-C', '--archived-cards',
                        dest='archived_cards',
                        action='store_const',
                        default=0,
                        const=1,
                        help='Backup archived cards')

    # Backup my boards
    parser.add_argument('-m', '--my-boards',
                        dest='my_boards',
                        action='store_const',
                        default=False,
                        const=True,
                        help='Backup my personal boards')

    # Backup organizations
    parser.add_argument('-o', '--organizations',
                        dest='orgs',
                        action='store_const',
                        default=False,
                        const=True,
                        help='Backup organizations')

    # Set the size limit for the attachments
    parser.add_argument('-a', '--attachment-size',
                        dest='attachment_size',
                        nargs='?',
                        default=ATTACHMENT_BYTE_LIMIT,
                        type=int,
                        help='Attachment size limit in bytes. ' +
                        'Set to -1 to disable the limit')

    args = parser.parse_args()

    dest_dir = datetime.datetime.now().isoformat('_')
    dest_dir = '{}_backup'.format(dest_dir.replace(':', '-').split('.')[0])

    if args.d:
        dest_dir = args.d

    if os.access(dest_dir, os.R_OK):
        if not bool(args.incremental):
            print('Folder', dest_dir, 'already exists')
            sys.exit(1)

    mkdir(dest_dir)

    os.chdir(dest_dir)

    # If neither -m or -o args specified, default to my boards only
    if not (args.my_boards or args.orgs):
        args.my_boards = True
        print('No backup specified (-m and -o switches omitted). Backing up personal boards.')

    print('==== Backup initiated')
    print('Backing up to:', dest_dir)
    print('Incremental:', bool(args.incremental))
    print('Tokenize:', bool(args.tokenize))
    print('Backup my boards:', bool(args.my_boards))
    print('Backup organization boards:', bool(args.orgs))
    print('Backup closed board:', bool(args.closed_boards))
    print('Backup archived lists:', bool(args.archived_lists))
    print('Backup archived cards:', bool(args.archived_cards))
    print('Attachment size limit (bytes):', args.attachment_size)
    print('==== ')
    print()

    org_boards_data = {}

    if args.my_boards:
        my_boards_url = '{}members/me/boards{}'.format(API, auth)
        org_boards_data['me'] = requests.get(my_boards_url).json()

    orgs = []
    if args.orgs:
        org_url = '{}members/me/organizations{}'.format(API, auth)
        orgs = requests.get(org_url).json()

    for org in orgs:
        boards_url = '{}organizations/{}/boards{}'.format(API, org['id'], auth)
        org_boards_data[org['name']] = requests.get(boards_url).json()

    for org, boards in org_boards_data.items():
        mkdir(org)
        os.chdir(org)
        boards = filter_boards(boards, args.closed_boards)
        for board in boards:
            backup_board(board, args)
        os.chdir('..')

    print('Trello Full Backup Completed!')

if __name__ == '__main__':
    cli()


Backport: HBASE-24161 [flakey test] locking.TestEntityLocks.testEntityLockTimeo…

…ut (#1477)
Signed-off-by: stack<EMAIL_ADDRESS>

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2.3 Compile Tests _

+1 :green_heart:
mvninstall
5m 37s
branch-2.3 passed

+1 :green_heart:
checkstyle
1m 10s
branch-2.3 passed

+1 :green_heart:
spotbugs
1m 57s
branch-2.3 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m  4s
the patch passed

+1 :green_heart:
checkstyle
1m  6s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
10m 42s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2.

+1 :green_heart:
spotbugs
2m  5s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 16s
The patch does not generate ASF License warnings.

35m 28s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1481

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 0dbdca1e51cc 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / eae7523cef

Max. process+thread count
93 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 44s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.3 Compile Tests _

+1 :green_heart:
mvninstall
5m 38s
branch-2.3 passed

+1 :green_heart:
compile
0m 54s
branch-2.3 passed

+1 :green_heart:
shadedjars
4m 17s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 37s
branch-2.3 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 57s
the patch passed

+1 :green_heart:
compile
1m 10s
the patch passed

+1 :green_heart:
javac
1m 10s
the patch passed

+1 :green_heart:
shadedjars
5m 45s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 40s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
132m 43s
hbase-server in the patch passed.

160m 41s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1481

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux be02886ea223 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / eae7523cef

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/testReport/

Max. process+thread count
3277 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  7s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2.3 Compile Tests _

+1 :green_heart:
mvninstall
8m 56s
branch-2.3 passed

+1 :green_heart:
compile
1m 22s
branch-2.3 passed

+1 :green_heart:
shadedjars
6m 32s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 55s
hbase-server in branch-2.3 failed.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m  5s
the patch passed

+1 :green_heart:
compile
1m 28s
the patch passed

+1 :green_heart:
javac
1m 28s
the patch passed

+1 :green_heart:
shadedjars
6m 11s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 48s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
209m 56s
hbase-server in the patch passed.

248m 23s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1481

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 0db5337de25d 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.3 / eae7523cef

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/testReport/

Max. process+thread count
2603 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1481/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Timeout of issues-vs-101485.md test

See 7aa9352031c7325c9447fb9f3df42c15c547328e where the CI fails on windows

Fixed by bf8fe87ba200976339e55263b3be0be6d4d2e51f


Unsuccessful every time I try to jailbreak.

I've never had any issues with the prior versions but this one hasn't work not even once :( don't know if this could help ios 15.3 iPhone 11
[] Launching kexploitd
[] Hello from kernel exploit server!
[] My UID is 0
[] My GID is 0
[] Launching oobPCI
[] CP: 0x1b564
[] GE: 0x15344
[] SpawnDriver failed: failedToGetThreadState
E: The operation couldn’t be completed. (Fugu15KernelExploit.Fugu15LaunchError error 4.)

Yes, many people have reported this issue after upgrading to version 1.1. However, after examining the code, I couldn't identify why this problem would occur. Essentially, it calls the thread_get_state function in Obj-C, but the call is not successful (the return value is not KERN_SUCCESS). I have looked into several possibilities, but I couldn't find any potential causes in Dopamine for these issues:

Invalid thread identifier: If the thread identifier tp passed to the function is invalid or not a valid thread port, the function will return an error code instead of a successful return value.
Invalid state type: If the state type type passed to the function is invalid or unsupported, the function may return an error code.
Invalid state buffer: If the thread_state_t type state buffer passed to the function is invalid or insufficient to hold the thread state information, the function may return an error code.
Permission restrictions: If the calling thread does not have sufficient permissions to retrieve the specified thread's state information, the function may return an error code.

Perhaps there are other reasons that I'm not aware of that could be causing this problem?

Nothing has changed in the code related to this ever.


Width and Height not always honored

Environment
React Native Environment Info:
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
Memory: 20.55 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.3 - /usr/local/bin/node
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 25.0.2, 26.0.3, 27.0.3, 28.0.1, 28.0.3
System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64
IDEs:
Android Studio: 3.1 AI-173.4819257
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: ^0.59.8 => 0.59.8
npmGlobalPackages:
create-react-native-app: 2.0.2
react-native-cli: 2.0.1
On IOS, trying to render a canvas with a given width and height (less than screen size). I can't still figure out why sometimes it would render outside of the bounds I have given.
Good render:

Bad render, nothing changed, just reopened the modal that renders the canvas:

Happens totally randomly.

Hello! I really sorry for that, but this package is deprecated for the RN Version you are using. I don't have enough time to update, but up to you if you want to be a collaborator. Sorry!

Sorry to hear that! Such a good and simple library, couldn't find better alternatives. I will take a look, but if this is related to Objective-C, there's not much I can do.

I've gone through the native code and can't really find a reason for this to happen so randomly. Any thoughts?

The XIB file auto sizing seems to be the culprit. If it is set to not auto expand, it will render just fine, but it will obviously not take the size required from its parent view, so that wouldn't work.
Any specific reason to use that XIB file instead of a regular view like https://github.com/RepairShopr/react-native-signature-capture does?

After hours of testing, couldn't really find out why the XIB file view would expand beyond its parent component (and the whole screen). However, from the JavaScript side the issue was having the sketch component inside 2 View components (to achieve some styling). In order for the issue to not happen, I had to ensure that the sketch view component only has 1 parent View, and also had to render the sketch component with a delay if I'm using it within a modal component.


Fix poly1d

Do not "maintain" poly1d
The semantics of NumPy's poly1d (legacy polynomial class) is not maintained.
Therefore __array_priority__ should be removed.

note: https://numpy.org/doc/stable/reference/routines.polynomials.html

LGTM.

Jenkins, test this please.

Jenkins CI test (for commit 92e956a1228996a0e28156568e8521094bbb86a4, target branch master) succeeded!

LGTM.


API rendering is very slow

Describe the bug
Once we publish our APIs on our Nutanix.dev platform, the rendering is very slow. Can you please have a look?
To Reproduce
https://www.nutanix.dev/api_references/foundation-central/#/b3A6MjIyMjI3Mjg-update-the-details-of-a-cluster
Expected behavior
API rendering should be quick for our customers.
Additional context
Add any other context about the problem here.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (remove any that are not applicable):
Chrome on windows and mac

➕ We're migrating from next -> platform now and also experiencing this. It's unacceptably slow performance even with trivial payloads.

Sometimes the API responds in a few seconds, other times it's 350ms or similar. It's not a consistent user experience and quite frustrating to wait 5-10 seconds sometimes for an API to load the data for a page.


Create LSIF dumps by querying arbitrary language servers

All the LSIF implementations I came across are tightly coupled to a specific underlying tool. I was wondering if it would be possible to create LSIF dumps by going through the language server protocol. The idea is that the you would be able to plug any existing language server and the LSIF utility would act as a client and progressively crawl the entire codebase. I understand it would probably be a lot less efficient than current implementations like lsif-tsc but it would open up LSIF to a lot of languages for free. I think a language agnostic LSIF utility would be very useful. I want to know if it's something that has already been considered, or if it already exists and I just missed it somehow.

We tried this and it is extremally slow for find all references.

I see. My motivation for this would be using LSIF as a source of truth for a generic utility that can display hover information on code examples, similar to what twoslash currently does for typescript. I started investigating how I could do this for Python in a discussion on the Pyright repo, and it looks like the sourcegraph team will revisit https://github.com/sourcegraph/lsif-py at some point and make it work with Pyright (it only works with Jedi currently). This should cover my most immediate use-case but I'd still be interested in a generic language server crawler/scrapper. Even if it's slow it would make LSIF instantly available to dozens of languages, and depending on the use-case (e.g.: running it once when building docs) it would probably be fine for a lot of projects. If something like lsif crawl --stdout pyright-langserver -- --stdio isn't completely off the table I could look into it next week.

The feature has not gain any traction in the community. I therefore close the issue. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add client functionality to server library

I wanted to be able to register clients through our backend. This functionality was not available in the current pusher library, so I decided to add it here rather than build something custom.

Thanks for your contribution; we really appreciate it. However Pusher is currently deprecating their existing notifications system in favour of their new one: https://pusher.com/push-notifications. This comes with its own set of separate libraries, e.g. https://github.com/pusher/push-notifications-python. I think new work should be moved there rather than adding more push notification functionality to this library.


whitelist cdn.jsdelivr.net

This site is used to serve LESS via<EMAIL_ADDRESS>

Hi Christopher @blizzardengle thank you for this.  The cdn.jsdelivr.net domain comes to us from two sources.
@brijrajparmar2 why is this in your list?
The other source is mvps.org, one of our oldest and most respected curators.  Christopher @blizzardengle please submit this to<EMAIL_ADDRESS>and see what they say.

hello Steven @StevenBlack,
thankyou for informing me, i have removed cdn.jsdelivr.net from my list.
it looks like my script mistakenly flagged the given cdn as one for the targeted porn site ones, this is unusual, i'll look into it.
thanks again.     :)

Sorry if this is not directly related to this issue, but it's related to JSDELIVR and my cli tool for the HOSTS files here so I don't know where to ask/comment.
My cli tool uses cdn.jsdelivr.net to download the files at this repo and so I was slightly concerned when I seen this issue, but am I correct in assuming (from what I'm reading here) that this service (cdn.jsdelivr.net) is safe to keep using? I'll be rewriting this tool sometime soon anyway with a different method, but I want to make sure my tool is safe in the meantime and I've not read or heard anything bad about this service before.

hello @Lateralus138
JSDelivr is a free public CDN for open-source projects, it's addition to my hosts list was a pure mistake from my end and as far as mvps.org host goes, as dnmTX pointed out The domain is commented therefore harmless.
we have no reason to believe cdn.jsdelivr.net is not safe to keep using.
thanks for reaching out.

Hi @brijrajparmar27
Thanks for the prompt reply and I figured as much. Like I said, I'm just making sure.
Again. much appreciated!

Thanks @blizzardengle and everyone for the assist.
Closing.


Saving Tags, Yet Metadata Still Disappears?

From<EMAIL_ADDRESS>on January 25, 2015 06:38:07
What version of ComicTagger are you using? 1.1.15-beta On what operating system (Mac, Linux, Windows)? What version? Windows What steps will reproduce the problem? 1. Apparently, using Nightwing (New 52) issue#1 -5 and auto-tagging/identifying it, or even just adding a random metadata (changing name, etc.)
2. Save the tags.
3. Tags mysteriously disappear. What is the expected output? What do you see instead? After saving a certain (not sure if specififc) comic's tag, the metadata suddenly disappears, instead of remaining there. Please provide any additional information below. Just trying to fix my Nightwing's issues...
Original issue: http://code.google.com/p/comictagger/issues/detail?id=69

From<EMAIL_ADDRESS>on January 24, 2015 21:41:15
Eyyy, would you look at that; I'm issue number 69 :S

From<EMAIL_ADDRESS>on January 24, 2015 21:45:25
BTW, additional info: the CR (at the left side of GUI) un-checks itself, too, when I save that certain comic.


Cannot Install confu

Hi,
when installing confu, I got the following error:

CRITICAL:root:failed to detect the host platform: sys.platform = linux2, platform.machine = i686

Actually, platform.machine() gets me 'i686'; in your platform.py script, this possibility is not taken into account.
I tried to modify the following line in platform.py:
x86_64_machines = ["x86_64", "amd64"]
by adding
x86_64_machines = ["i686", "x86_64", "amd64"]
but then NNPACK build fails anyway: the error I get (after the trick above in platform.py) is the following:

IOError: [Errno 2] No such file or directory: /home/administrator/NNPACK/deps/pthreadpool/configure.py

The reason is that no deps are downloaded when cloning git.
Any suggestion about?
Thank you.
Emanuele

Do you have a 64-bit CPU/OS?

Hi @Maratyszcza , thank for your great job.
I have met the same problem when I try to build nnpack in  ARM Cortex-A57, which platform is outputed as 'aarch64'. Collecting git+https://github.com/Maratyszcza/confu
Cloning https://github.com/Maratyszcza/confu to /tmp/pip-kzRWXJ-build
Complete output from command python setup.py egg_info:
CRITICAL:root:failed to detect the host platform: sys.platform = linux2, platform.machine = aarch64
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-kzRWXJ-build/setup.py", line 3, in
from confu import version, maintainer, email
File "confu/init.py", line 35, in
from confu.platform import Platform
File "confu/platform.py", line 217, in
host = Platform(detect_host())
File "confu/platform.py", line 213, in detect_host
.format(sys=sys, machine=machine))
ValueError: Unexpected sys.platform, platform.machine combination (linux2, aarch64)
`

@nopattern I suppose your problem is fixed in #71


Error using basic rax.py

Seems to work with
RAX_REGION=DFW ./rax.py --list
{}
but trying a different region fails.
RAX_REGION=IAD ./rax.py --list
Traceback (most recent call last):
File "./rax.py", line 282, in
main()
File "./rax.py", line 275, in main
_list(regions)
File "./rax.py", line 185, in _list
imagegroup = 'image-%s' % images[server.image['id']]
TypeError: string indices must be integers
Any help would be great...thanks

I have noticed the same:
with ~/.raxpub containing region = ORD

main()

File "/usr/bin/rax.py", line 461, in main
_list(regions, refresh_cache=args.refresh_cache)
File "/usr/bin/rax.py", line 374, in _list
_list_into_cache(regions)
File "/usr/bin/rax.py", line 310, in _list_into_cache
imagegroup = 'image-%s' % images[server.image['id']]
TypeError: string indices must be integers


ouroboros-network update (big ledger peers)

Description
Changes due to introduction of big ledger peers in ouroboros-network (eclipse evasion).
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated.  These may include:

golden tests
property tests
roundtrip tests
integration tests
See Runnings tests for more details

[ ] Any changes are noted in the CHANGELOG.md for affected package
[ ] The version bounds in .cabal files are updated
[ ] CI passes. See note on CI.  The following CI checks are required:

[ ] Code is linted with hlint.  See .github/workflows/check-hlint.yml to get the hlint version
[ ] Code is formatted with stylish-haskell.  See .github/workflows/stylish-haskell.yml to get the stylish-haskell version
[ ] Code builds on Linux, MacOS and Windows for ghc-8.10.7 and ghc-9.2.7

[ ] Self-reviewed the diff

Note on CI
If your PR is from a fork, the necessary CI jobs won't trigger automatically for security reasons.
You will need to get someone with write privileges.  Please contact IOG node developers to do this
for you.

The network changes were merged in #5243 and #5467.


Feat: Improving the registry and dependency injection for hierarchical instantiation

While integrating Huggingface transformers into modalities, I figured that we need to improve the hierarchical instantiation from the config substantially and rather sooner than later, otherwise extensibility is limited.
Right now, the instantiation via the registry is flat and we have helper functions in main which reflect the hierarchy. For instance, when we instantiate the optimizer, we instantiate the model first via
        model: torch.nn.Module = self.resolvers.build_component_by_config(config=config.model)

and then subsequently we feed in the moder parameters into the optimizer via
optimizer: torch.optim.Optimizer = self.resolvers.build_component_by_config(
        config=config.optimizer, extra_kwargs=dict(params=wrapped_model.parameters())
)

This approach is only feasible for small hierarchies and as long as the components are generic, e.g., if the optimizer always needs an nn.Module object passed.
The moment when concrete implementations have different dependencies this breaks. For instance, if one special optimizer not only depends on a model but also on another component, then this would be a special case that we would have to reflect/hardcode in our code.
Given these issues, I would suggest we implement hierarchical instantiation within the registry already.
We would call registry.build(config: AppConfig, component_names: List[str]) -> Dict[str, Any] to instantiate the components given by component_names. Since these components will depend on other components up in the hierarchy, the registry will start instantiating the components without any dependencies. Then we continue the instantiation by injecting the already instantiated components until all components in component_names are instantiated.
Given this setup, we can build arbitrary configs and dependencies, as the registry is capable of the whole instantiation process.

@lllAlexanderlll is your solution from this weeks hackathon solving this? If I got it right, by explicitly specifying type hints, pydantic could not get confused about turning a Config into a different type, than the respective type_hint would expect. Therefore, when having nested configs, a miss configuration is not possible anymore, isn't it?

In my tests with a flat config specification it worked to instantiate the correct config and select the config class specified by the type_hint. Also, validation errors were thrown for incorrect configs.

only that I get this right - with "copy_by_value" and "copy_by_reference" you refer to having two components, which require an object of the same type for their initialization and then either requiring a copy of that or a reference (e.g. using the same dataset instance for two situations, while using two different dataloaders, so their iteration is not affected by concurrency issues?)


[nit] enhance testing

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 59.434%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
567

Relevant Lines:
954

💛  - Coveralls


max_rows not respected with reorder

When reordering with a max_rows widgets still get added to the bottom, instead of being moved in between.

if you have a fix I'd gladly accept a PR


Release cobigen-eclipse-v5.1.0

This issue has been automatically created. It serves as a container for all release related commits

Automatically processed.
The decisions taken by the developer and the context of the decisions throughout the script:

User confirmed that tests are running on CI and the build is not failing.
User confirmed that tests are running on CI and the build is not failing after pushing release changes to development branch.


Correct bracket type used around nvarchar/varchar when formatting the command

The current formatting code puts brackets around varchar/nvarchar size instead of parenthesis

@schotime - I didn't realize this was here so long!! Any chance of getting this in? Getting tired of replacing [] with () :)

You think maybe we can get this in for v6? Replacing [ ] with ( ) is annoying :)


Deny-Subnet-Without-Nsg policy blocks the deployment of Subnet using Terraform

Describe the bug
Once the policy to block subnets without NSG is enforced via deny mode. We are unable to deploy a subnet using the terraform. The terraform resource provider doesn't have an option to pass the NSG while creating the subnet. Only way is to do the association after the subnet is created. However once the said policy is enforced, we wont be able to create the subnet.
We are aware of the other ways to do the association, however while creating a new subnet on an existing virtual network and terraform template, we are unable to find a way forward.

Hey @dpb519,
This is a known behaviour I'm afraid for terraform, and we document it here https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/wiki/[User-Guide]-Getting-Started#additional-considerations-when-deploying-landing-zone-resources-with-terraform
You could look at using the AzApi provider to achieve this though  https://learn.microsoft.com/en-us/azure/templates/microsoft.network/virtualnetworks/subnets?pivots=deployment-language-terraform or https://learn.microsoft.com/en-us/azure/templates/microsoft.network/virtualnetworks?pivots=deployment-language-terraform


RFC7807Error not used

as title
https://github.com/yahoojapan/authorization-proxy/blob/6c6a4ee54da058a1efc5d135cdba28462642267b/handler/error.go#L19-L28

continue in: https://github.com/AthenZ/authorization-proxy/issues/10