GKE workload identity pod with PGAdapter as sidecar can't create a table with UNIQUE,serial,timestamp

I created the following deployment in GKE autopilot with GKE workload identity configured properly. I'm able to use psql -h localhost command to connect to the Spanner database of PosgreSQL interface, psql-test under instance hil-test. Here's the deployment file:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: gcloud-psql
  labels:
    app: pgadapter
spec:
  replicas: 1
  selector:
    matchLabels:
      app: pgadapter
  template:
    metadata:
      labels:
        app: pgadapter
    spec:
      serviceAccountName: spanner
      containers:
      - name: gcloud
        image: gcr.io/google.com/cloudsdktool/cloud-sdk:latest
        command: [ "/bin/bash", "-c", "--" ]
        args: [ "while true; do sleep 30; done;" ]
      - name: spanner-pgadapter
        image: gcr.io/cloud-spanner-pg-adapter/pgadapter:latest
        args: [ "-p PROJECT_ID -i hil-test -d psql-test -x" ]

However, I found the PostgreSQL create table syntax compatibility is quite limited. I want to confirm that's indeed the case. I tried an example from the Internet to create a table with the following DDL:
psql-test=> CREATE TABLE accounts (
 user_id serial PRIMARY KEY,
 username VARCHAR ( 50 ) UNIQUE NOT NULL,
 password VARCHAR ( 50 ) NOT NULL,
 email VARCHAR ( 255 ) UNIQUE NOT NULL,
 created_on TIMESTAMP NOT NULL,
        last_login TIMESTAMP
);
ERROR:  INVALID_ARGUMENT: io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Type <serial> is not supported.
psql-test=> CREATE TABLE accounts (
 user_id bigint PRIMARY KEY,
 username VARCHAR ( 50 ) UNIQUE NOT NULL,
 password VARCHAR ( 50 ) NOT NULL,
 email VARCHAR ( 255 ) UNIQUE NOT NULL,
 created_on TIMESTAMP NOT NULL,
        last_login TIMESTAMP
);
ERROR:  INVALID_ARGUMENT: io.grpc.StatusRuntimeException: INVALID_ARGUMENT: <UNIQUE> constraint is not supported, create a unique index instead.
psql-test=> CREATE TABLE accounts (
 user_id bigint PRIMARY KEY,
 username VARCHAR ( 50 ) NOT NULL,
 password VARCHAR ( 50 ) NOT NULL,
 email VARCHAR ( 255 )  NOT NULL,
 created_on TIMESTAMP NOT NULL,
        last_login TIMESTAMP
);
ERROR:  INVALID_ARGUMENT: io.grpc.StatusRuntimeException: INVALID_ARGUMENT: Type <timestamp> is not supported.
psql-test=> CREATE TABLE accounts (
 user_id bigint PRIMARY KEY,
 username VARCHAR ( 50 ) NOT NULL,
 password VARCHAR ( 50 ) NOT NULL,
 email VARCHAR ( 255 )  NOT NULL);
CREATE

It appears I had to delete UNIQUE,serial,timestamp to create a table in a database of PostgreSQL interface. Is this normal?

Yes, this is normal. PGAdapter only supports the data types and DDL features that are also supported by Cloud Spanner PostgreSQL dialect databases: https://cloud.google.com/spanner/docs/reference/postgresql/data-definition-language
So any DDL or other SQL statement that is not supported by Cloud Spanner will also not be supported in PGAdapter. The only exception to this is a fixed set of SQL statements that are known to be executed by some drivers, like for example JDBC. These statements will be converted internally in PGAdapter to a statement that is supported by Cloud Spanner.
In addition, the create table|index if not exists... and drop table|index if exists are supported by PGAdapter.


[ENH] Template-based masking of EPI boldrefs

Changes proposed in this pull request
This PR explores template-based masking of boldrefs to initialize the skull-stripping workflow (see issues related on #1000).
This PR is also highly related to #1050.

Documentation that should be reviewed

This is WIP, will update documentation when it is proven to work out.

So this are the results:

https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000116/sub-12_task-visualoddballwithbuttonresponsetotargetstimuli_run-02_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000133/sub-06_ses-post_task-rest_run-01_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000140/sub-32_task-heatpainwithregulationandratings_run-02_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000157/sub-23_task-passiveimageviewing_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000210/sub-06_task-rest_run-01_echo-1_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000210/sub-06_task-rest_run-01_echo-2_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000210/sub-06_task-rest_run-01_echo-3_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000216/sub-03_task-rest_echo-2_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000216/sub-03_task-rest_echo-3_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000216/sub-03_task-rest_echo-4_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000237/sub-03_task-MemorySpan_acq-multiband_run-01_bold_masks.svg
https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000237/sub-06_task-MemorySpan_acq-multiband_run-01_bold_masks.svg

I still need to investigate what happened here: https://2488-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds000216/sub-03_task-rest_echo-1_bold_masks.svg

The problem with echo 1 of ds216 seems to have been introduced here https://5172-53175327-gh.circle-artifacts.com/0/tmp/data/reports/ds000216/sub-03_task-rest_echo-1_bold_masks.svg

Seems like the weird problem on ds216 is now fixed. At this point I would ask: do you think it is maybe worth changing the whole algorithm to the following?:

Initialization: ANTs' AI, using the template as target and the boldref as moving
Gross mask, applyTransform on the inverted transform of 1)
N4 on the boldref with the gross mask
First registration: very fast refinement (Rigid) of the gross mask using the template as target and the boldref as moving and initialized with 1)
N4 on the boldref with the less-gross mask
Second registration (Affine) initialized with 4)
Remaining boldref refinement with the final mask

Let's test on the subject from #1181, as well.

Artifacts in the latest commit without [skip ci] -> https://circleci.com/gh/oesteban/fmriprep/2525#artifacts/containers/0

Thanks a lot for your precious feedback! @ZhifangYe

The pre_mask's header should be fixed before N4 correction. I encountered Inputs do not occupy the same physical space! error on one of my test image.

Could you provide more information about the error (full trace) or even the dataset (privately is fine) where this is happening? This is a new caching procedure we are testing and it does not surprise me you got this kind of problem.

The N4 correction has no effect on some of the unwrapped images (eg. sub-26 rest) in bold_bold_trans_wf. I tried to run N4 correction manually on the ref_image_valid.nii.gz and it yielded the same incorrect result.

Cool, sub-26_task-rest is now within the regression tests, so I'll work on this one particularly.

What if the BOLD image only covers part of brain volume? I think the initial affine transformation would generate a quite large mask for N4 correction. I think we should include some partial volume scan (especially for scans only covers 30-40 slices parallels to the long axis of hippocampus) in the test battery to see how well the method works.

This question is also very pertinent. I'll dig up some partial FoV datasets from OpenNeuro and add them to the test battery.
Thanks a lot for your input, very much appreciated!

Fixes #1000
Fixes #1181

Ref #900

Here's the fMRIprep error log and the verbose log of N4 correction command.

I think it's due to the very small discrepancy between the qform matrix of pre_mask and ref_image.
The following link is the raw data to replicate this error. https://www.dropbox.com/s/akfyadrih5lgcbd/sub-30.zip?dl=0

I think it's due to the very small discrepancy between the qform matrix of pre_mask and ref_image

Correct, there is a minimal difference in the qform.

Alright, this ready for review (@ZhifangYe, @effigies). I've just fixed the issue of mismatched headers before N4.
Since we don't make any promises about very limited FoV (https://github.com/poldracklab/fmriprep/labels/partial FOV), I propose to merge this in and come back later to the FoV issue.
Regarding sub-26_task-rest, please check out the regression tests under the test_pytest build of Circle.

This is sub-26_task-rest: https://2591-53608443-gh.circle-artifacts.com/0/tmp/data/reports/ds001240/sub-26_task-rest_bold_masks.svg which looks okay.
We are seeing ds005 fail due to a problem checking filenames that is also happening in master. I'm guessing that would be a trivial change to do in master.
Thumbs up?

ds005 problems addressed here - #1344
If there are no further comments or voices against, I'll be merging later today and close #1050 as this PR supersedes that one.
Thanks to @ZhifangYe, this PR has been only possible with all the new data we have now for regression tests.


Regular links don't work as expected

Look at the advanced example's email column for instance
https://vue3-datatable-document.vercel.app/advanced
When you click on it it would normally open up the default mail application.
I think the bug is caused by using prevent modifier.

Hi,
You can use @click.stop to prevent the parent click event, which will work. I will also update it in all our demos.
<template #email="data">                 <a :href="mailto:${data.value.email}" class="text-primary hover:underline" @click.stop>{{ data.value.email }}</a>             </template>


[SONARMSBRU-177] Fix capability for invalid SARIF from RTM Roslyn.

SonarQube analysis reported 4 issues:

 4 major

Watch the comments in this conversation to review them.

SonarQube analysis reported 4 issues:

 4 major

Watch the comments in this conversation to review them.

FYI @HSAR @duncanpMS , I've managed to get the following JSON produced by VS2015 RTM by adding double-quotes, backslashes and newlines in a SonarLint rule id, title & message:
    {
      "ruleId": ">"
\<S2228",
      "locations": [
        {
          "analysisTarget": [
            {
              "uri": "C:\Users\dinesh\Desktop\tmp\ConsoleApplication1\ConsoleApplication1\Program.cs",
              "region": {
                "startLine": 23,
                "startColumn": 16,
                "endLine": 23,
                "endColumn": 33
              }
            }
          ]
        }
      ],
      "shortMessage": ">"
\<Remove this logging statement.",
      "fullMessage": "Debug statements are always useful during development. But include them in production code - particularly in code that runs client-side - and you run the risk of inadvertently exposing sensitive information.",
      "properties": {
        "severity": "Warning",
        "warningLevel": "1",
        "defaultSeverity": "Warning",
        "title": ">"
<Console logging should not be used",
        "category": "SonarLint",
        "helpLink": "http://vs.sonarlint.org/rules/index.html#version=1.3.0&ruleId=>"
\<S2228",
        "isEnabledByDefault": "True"
      }
    },

The good news is that there shouldn't be any special character in SonarLint's rule IDs, and there should be no new line in neither the title nor the short/full message in the real world.

FYI, VS2015 Update 1 doesn't support special characters in rule IDs:
"shortMessage": "Analyzer 'SonarLint.Rules.ConsoleLogging' threw an exception of type 'System.ArgumentException' with message 'Reported diagnostic has an ID '>\"\u000d\u000a\\<S2228', which is not a valid identifier.\u000d\u000aParameter name: diagnostic'.",

@dbolkensteyn Unfortunately, RTM does. I'm investigating to see whether SonarLint generates fullMessages with multiple lines at this time.

It doesn't AFAIK @HSAR

SonarQube analysis reported 4 issues:

 4 major

Watch the comments in this conversation to review them.

LGTM


Support Node native TypeScript (--experimental-strip-types and --experimental-transform-types)

Feature Request
I want to use these new flags to get rid of configs, nodemon, ts-node etc. but can't because typia. I really like typia and don't want to lose it. Is there any plans for Node native TS?
Cheers.

because typia using tsc to extract type information, you need to run scripts by running tsc + typia

because typia using tsc to extract type information, you need to run scripts by running tsc + typia

So we need tsc no matter what. I guess I should wait generation to suffixed files feature, at least.
Or generate mode with proper caching.

@ryoppippi I just checked unplugin-typia and saw it can work with Bun. It looks like it injects with a preload script and it reminded me how ts-node can run with Node —require parameter: https://www.npmjs.com/package/ts-node#node-flags-and-other-tools
I’m wondering, can unplugin-typia work same way and use —require/—import flags to extract types in Node?

@ismailkarsli unplugin-typia uses tsc inside

@ryoppippi Since ts-node can transform TS files to JS files with node -r ts-node/register, I thought that typia can extract TS types with tsc and then let other compilers do their jobs.
I don’t know how tsc, typia or unplugin-typia works so please excuse me if I ask meaningless questions.


Enabling changelog for custom fields

Fixes: #1234

This PR enables changelogs for custom fields.  It migrates any existing history from the Django LogEntry objects to the ObjectChange objects.  As these are not identical objects some modifications were necessary during the migration.

After more testing I believe Glenn was right (of course Glenn was right) and we need to add changelog for CustomFieldChoice objects as well...


Use bbox intersection logic for rectangles

If a polygon describes a rectangle, we don't need to load the way geometry to check for an intersection.
This should be especially beneficial for large areas, for which we previously had to load all intersecting edge geometries.

@karussell any objections?

Looks good!
(There could be rare problems with this approach in general, when the bbox of the tower nodes is smaller than the bbox of the entire geometry, but this is not a new problem.)


builder: support variables in stage names

Sometimes it can be useful to have dynamic stage names.
I'm not sure if my change to dispatchers.go is correct. Previously, the flagArgs got processed without HeadingArgs and I wasn't sure if this omission was on purpose or a bug. Please let me know if you want me to undo this change.
Closes https://github.com/containers/buildah/issues/4948

Discussing here: https://github.com/containers/buildah/issues/4948#issuecomment-1670952849 since this is not in parity with docker/buildkit so this feature will be applicable only for Containerfile and not Dockerfiles

@nalind PTAL

Since we have had no activity on this for many months closing.


Document #[graphql(flatten)] in the english version of the book

Description of the feature
As per #1004 , async graphql supports the flatten attribute on Simple-/InputObject's, but this is not yet documented in the english version of the async-graphql book. I'd add it myself there, but I'm not sure which page to put it into, if someone tells me where to put it I'd be happy to add it myself.
Code example (if possible)

add to these pages 🙂
https://github.com/async-graphql/async-graphql/blob/master/docs/en/src/define_input_object.md
https://github.com/async-graphql/async-graphql/blob/master/docs/en/src/define_simple_object.md


RFC: Re-execute notebooks on CI when building Sphinx docs

Currently, we have set nbsphinx_execute = "auto" in the Sphinx configuration so that notebooks are not re-executed anytime someone runs tox -e docs, in large part to speed up the build cycle for quick development.
However, even without changing this for local builds, we have the option of changing this on CI, which is where our deployed documentation is built.
Here's what would be different:

The notebooks in the docs will always be the result of a fresh run, so we will no longer to be forced to manually re-execute notebooks e.g., anytime the Qiskit default visualizaions change (#524) or  when deprecation warnings are added to our own codebase (possible part of #533), etc.
We will have less control about what output is appearing in the hosted notebooks.  Maybe something weird will happen because of a weird random seed.  (For the docs to build and deploy successfully, the code must execute without errors, but there could still be something weird in the notebook short of an actual failure.)  Conversely, if running a notebook does result in something weird, I'd almost prefer that that is visible to at least us as we glance through the documentation, rather than be something that is not discovered until a user actually tries to use the notebook.

I'm not really sure which I'd prefer, but think it is worth considering merging this.  Open to discussion.

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 95.433%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3448

Relevant Lines:
3613

💛  - Coveralls

I am highly in favor of adding this. Didn't realize this was straightforward


How and why the warping works?

Hey! Great work!
I have a question about the details of warping.
In the equation (2), you use predicted depth map $D_s$ to warp input sketch $S$ at the newest viewpoint $c_1$. But, am I misunderstanding that $c_1$  corresponds to not the input sketch $S$ but a novel view's sketch?
How could such warping be accurate? Alternatively, $S_1$ acts as a rough, intermediate result that helps MVDream to generate the final images, so the precision of warping is not that that significant.

Yes, $c_1$ corresponds to a sketch from a novel view rather than the input sketch $S$.
It is true that when the novel view sketch has a rotation angle too large relative to the input sketch, the quality or precision of the sketches degrades. Therefore, we only warp the sketches within a ±45 degree range.


Beam routing framework integration

Change list:

Added way id attribute to the graph
Added writing travel_time, way_id and result of BPR function on travel_time for each edge of the graph in traffic assignment.

I am sorry i mixed the repo.


5654 measurescorer bug for denominator exception- master

closes #5654

replaced by https://github.com/hapifhir/hapi-fhir/pull/5677


[WIP] Backport 10244

Cherry-picking

[X]     ea73b84d2d Add src/interface/README.md
[X]     71e0d90876 Remove direct bitcoin calls from qt/bitcoin.cpp
[X]     c0f2756be5 Remove direct bitcoin calls from qt/optionsmodel.cpp
[X]     3d619e9d36 Remove direct bitcoin calls from qt/bitcoingui.cpp
[X]     c2f672fb19 Remove direct bitcoin calls from qt/utilitydialog.cpp
[X]     5fba3af21e Remove direct bitcoin calls from qt/splashscreen.cpp
[X]     fe6f27e6ea Remove direct bitcoin calls from qt/clientmodel.cpp
[X]     d7c2c95948 Remove direct bitcoin calls from qt/intro.cpp
[X]     e0b66a3b7c Remove direct bitcoin calls from qt/peertablemodel.cpp
[X]     3034a462a5 Remove direct bitcoin calls from qt/bantablemodel.cpp
[X]     582daf6d22 Remove direct bitcoin calls from qt/rpcconsole.cpp
[X]     90d4640b7e Remove direct bitcoin calls from qt/optionsdialog.cpp
[ ]     a0704a8996 Remove most direct bitcoin calls from qt/walletmodel.cpp
[ ]     827de038ab Remove direct bitcoin calls from qt/coincontroldialog.cpp
[ ]     3ec2ebcd9b Remove direct bitcoin calls from qt/addresstablemodel.cpp
[ ]     3cab2ce5f9 Remove direct bitcoin calls from qt/paymentserver.cpp
[ ]     58845587e1 Remove direct bitcoin calls from qt transaction table files
[ ]     e872c93ee8 Remove direct bitcoin access from qt/guiutil.cpp
[ ]     56f33ca349 Remove direct bitcoin calls from qt/sendcoinsdialog.cpp
[ ]     9a61eed1fc Use WalletBalances struct in Qt
[ ]<PHONE_NUMBER> Add developer notes about blocking GUI code

Additional Stuff:

[ ] Privatesend stuff everywhere
[ ] InstantSend stuff at least in clientmodel
[ ] Masternode list stuff in clientmodel

Superseeded by https://github.com/dashpay/dash/pull/3682


1 K Bots ? : ) !! UPDATED !!

https://www.youtube.com/watch?v=-gbPzJPymCc
Blah...Blah... meehh...soo? Update this weekend?  xD

cool cant wait

Thanks : ) Only 2 days. Just make better gui

Awesome bro!!!! Where are you running bots

still getting "Waiting for client!"
have installed the userscript and it pops up on the game but nothing else happens

@Salvationdk @l3mpik me too "waiting for client!"

I have same problem btw "Waiting for client!"  when hosting on my vps

@l3mpik where you got ur proxies from please say

Maybe they us some edited files. 2. Look for feeder.js at line 13:
ex. var socket = require('socket.io-client')('ws://<IP_ADDRESS>:4000'); <--- Maybe is the problem with port : )

Enyoj !

@l3mpik in c9.io i am getting 400-500 bots

Nice : )

@l3mpik where you got your proxies from please? i want like your bots

@mayed505  give me sec : )

@mayed505  can u tell me what is this ? http://imgur.com/oLApoHh ? Hmm..

@l3mpik yea about that..... i created a project like yours and took it down since youtuber skids stole my gui and all files and sold me them YES THEY SOLD IT....

@l3mpik btw can you send me the link where u get your proxies from?

http://www.vipsocks24.net/
http://www.live-socks.net/
Here is script for tempermonkey :
Proxy saver: http://pastebin.com/8VPGtgE2
Proxy saver server: http://pastebin.com/ygZ3fHtk
:))

thx @l3mpik  i used procees.env.ip and worked btw I hacked c9 never get banned & get with 2.5GB ram ONLY SUPPORT for DEV no PUBLIC my skype: david ali -09

what

@David1ali12 @Salvationdk @Lok0n @mayed505
#45


Seek IITB training requests stats

Following discussion with IITB Learning Team,  they mentioned IITB employees make financial requests for training. They will touch base with finance to see what type of training are frequently requested.

IITB Learning informed me the information that the finance team take care of all training requests of all the employees. However, they don't think it would be valuable for us to get general information because there are different ones. Furthermore, rep is not sure if they are set up to report of all of the data quite yet


Wrong formatting of Inline JavaScript within blade directives => intentions will be lost

Template
<script>
    function test() {
        @if (Auth::check())
            if (window.test) {
            return;
            }
        @endif
    }
</script>

Context (Environment)

macOS 12.3.1 (21E258)

Description
Formatting this template should cause the inline JS to format with proper intentions as well. return; should have a couple more spaces in front, so it's more to the right. So, the above should format to look like this:
<script>
    function test() {
        @if (Auth::check())
            if (window.test) {
               return;
            }
        @endif
    }
</script>

But this won't happen. Here is a richer presentation of the problem:

See how all JS lines are on the same vertical plane level?
This happens when JS is inside of blade directives, in this case between @if (Auth::check()) and @endif. As soon as I remove those lines, JS will be formatted correctly.
My current work-around is to put {{-- blade-formatter-disable-next-line --}} ahead of each directive in JS. Ugly, but better than keeping it this way. I hope this can be fixed, because this extension is the best choice for blade formatting so far.

Thanks @martin-braun for creating the issue.
I'll look into it.

Fixed at https://github.com/shufo/vscode-blade-formatter/releases/tag/v0.13.24

@shufo Thank you. I just updated, it works flawlessly, good work! Really appreciate it. :)


Fix docs build v2

Description of the problem
The docs CI is failing as we import kivymd in docs generation.
Describe the algorithm of actions that leads to the problem
This happens because the version of the package is defined in the init.py of kivymd.
When importing that it also runs this line, which then imports kivy, this issue should be fixed in the latest kivy, but its best to have version info in a separate file

Is this PR ready to merge?

yes, all build system should work the same, but if anything breaks please feel free to ping me

Okay, thanks

Hello everyone, the large Materialyoucolor library does not want to work on a 32-bit system

ImportError: dlopen failed: "/data/data/com.autograd.ag_emp/files/app/_python_bundle/site-packages/materialyoucolor/quantize/celebi.so" is 64-bit instead of 32-bit

Are 32-bit systems still supported?

Did you user recipe for building?

ImportError: dlopen failed: "/data/data/com.autograd.ag_emp/files/app/_python_bundle/site-packages/materialyoucolor/quantize/celebi.so" is 64-bit instead of 32-bit

why is this discussion taking place in the PR ?


feat: go-da and modularization of API building

This PR does the following:

Introduce the go-da interface
Separate the API structs to their own modules for dependency reduction
Introduced clientbuilder package, letting users build a client using only the modules they require

Turning to draft until node PR is merged and released


feat: add new api playground to the documentation

Hello @Wauplin
I should probably upload the image to the hugging face datasets, as the others images, right ?
Wanted to wait your confirmation first
thx

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

I should probably upload the image to the hugging face datasets, as the others images, right ?

Yes exactly! Thanks for taking care of it :)

(related a bit to #1075)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Add threshold when updating user.last_login field

I want to merge this change because it adds 5 seconds of threshold (settings variable) when calling tokenCreate/tokenRefresh mutation. In case of calling multiple times this mutation for the same user, this will not make an additional updates on DB side.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations

Docs

[ ] Link to documentation:

Pull Request Checklist

[ ] Privileged queries and mutations are either absent or guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migrations are either absent or optimized for zero downtime
[ ] The changes are covered by test cases
[ ] All new fields/inputs/mutations have proper labels added (ADDED_IN_X, PREVIEW_FEATURE, etc.)
[ ] All migrations have proper dependencies
[ ] All indexes are added concurrently in migrations
[ ] All RunSql and RunPython migrations have revert option defined

Should we implement the same logic in ExternalObtainAccessTokens and ExternalRefresh?

@fowczarek I was thinking about this. In the beginning decided not to add it as this flow uses external providers for authenticating, so there are some limits there. Also additionally you need to authenticate first on their side.
So the whole external flow will take longer than our default one. But if you see any risks here, we can also add this to external mutations :) But I will do that in a separate PR


Obsidian & drawio Update

Thanks a lot for this plugin! Being so used to drawio, I've been rather missing it whenever I used Obsidian. 😄
I noticed that the drawio version was a bit older and had some odd behavior where the editor would open in the navigation pane, effectively breaking it and requiring a restart of Obsidian. With the Obsidian update, some functions were deprecated or removed, so I updated those.
I'm not very familiar with Obsidian plugin development and my front-end skills aren't the best, so forgive my ignorance if I missed something obvious.
I tried to run the automation part, but that was broken to begin with and I couldn't figure out what needs to be changed exactly.
Additionally, I added some instructions to the README, as it seems not as intuitive (see #60 / #54 / #45).
Let me know if there's anything that I should adjust 🙂

DrawIO just updated to v20.3.6 what looks to be a few hours after your commit. Would it be worth reflecting this update in a new commit? 🤔

Thanks for letting me know! I just rewrote the commit.
The funny part is, that I did actually already have the reference locally, but they must have tagged it between me checking the available tags on GitHub and me fetching the remote. 😄

Thanks for merging this! 😄
Anything I can help with to create a new release?

请问可以发布一个新的release吗？
Can you release a new release?

请问可以发布一个新的release吗？
Can you release a new release?


"--limit" behaving oddly?

I seem to be getting non deterministic returns from my queries,
malwarebazzar % bazaar query --limit 900 -s tag ransomware  | wc -l
1170
malwarebazzar % bazaar query --limit 900 -s tag ransomware  | wc -l
1317
Another example:
malwarebazzar % bazaar query --limit 300 -c -s tag ransomware  | wc -l
301
malwarebazzar % bazaar query --limit 900 -c -s tag ransomware  | wc -l
901
malwarebazzar % bazaar query --limit 1000 -c -s tag ransomware  | wc -l
1001
malwarebazzar % bazaar query --limit 2000 -c -s tag ransomware  | wc -l
101
There doesn't seem to be a lot going on in the code that could cause this so I think it is on the server side, but has anyone observed this behavior? I am just trying to get all the ransomware binaries on malware bazaar...

This is probably because the CSV output somehow a) breaks because of your terminal width or b) has linebreaks in it. If you just query via the --simple switch, the amount of results is as expected:
❯ bazaar query tag ransomware --limit 10 -s | wc -l
10
❯ bazaar query tag ransomware --limit 100 -s | wc -l
100
❯ bazaar query tag ransomware --limit 150 -s | wc -l
150
❯ bazaar query tag ransomware --limit 250 -s | wc -l
250
❯ bazaar query tag ransomware --limit 500 -s | wc -l
500
❯ bazaar query tag ransomware --limit 1000 -s | wc -l
1000

The latter example is correct, as the CSV output also contains headers for the columns.

Also, 1000 seems to be the API limit and therefore only 100 results are returned if you try to query more than 1000 Samples.


Need help: Can we create a subpage for a few repos?

https://github.com/TheAlgorithms/C-Plus-Plus/pull/730#issuecomment-619399245 is has a GitHub Action that generates html.  It would be cool if we could have that appear at https://thealgorithms.github.io or https://thealgorithms.github.io/C-Plus-Plus

Hi @cclauss really happy to talk to you after a long time
would you please explain this more like you need a separate page for each algorithm to navigate
And also I want  to share that this is a nice idea for the repo. we can create it for large amount of algorithms and for different methodologies.
What do you say???

VerbalExpressions has VerbalExpressions/verbalExpressions.github.io and we have a docs folder on master in VerbalExpressions/JSVerbalExpressions. GH Pages definitely has support for this sort of thing, because we have a page at https://verbalexpressions.github.io/JSVerbalExpressions.
I don't have access to the repo's settings, but I assume you just have to configure Settings, Options, GitHub Pages, Source. It doesn't give very many options afaik—it's got to be either master, docs/ on master, or the gh-pages branch (no subfolder).

@viragumathe5 We already have autogenerated markdown directories for all the algorithms in Python, C++ so we do not need to replicate that level of functionality.  However, @Albirair did a really cool thing in TheAlgorithms/C-Plus-Plus#730 by autogenerating HTML docs with Doxygen for that algorithm.  I was just interested to (experimentally) see if we could use GitHub Pages to display such HTML content.  Doxygen, pydoc, sphinx, javadoc, etc. an autogenerate HTML, markdown, etc.
@shreyasminocha https://thealgorithms.github.io shows that I did configure things enough to display the most basic hello world.  It would be great if you could submit some PRs that would help us to get closer to the level that you have on VerbalExpressions.

https://github.com/TheAlgorithms/C-Plus-Plus/commit/57ea7b1f9d6f440aef0cdb6b8ccd111ba3f5c50e looks like it should do the right thing—bring all website files to the top level of gh-pages, but it doesn't seem to…

We now have an index.html but that is not what the wiki tab displays.

Pages in the wiki must be added manually edited with markdown as far as I know, but I will make sure to check.

Pages in the wiki must be added manually edited with markdown as far as I know, but I will make sure to check.

Yeah, the best you can do is:

Add a link to the website in the wiki
Disable the wiki altogether

Can you autoforward?  If not then a manual link will be the compromise position.


feat: add whitelistPackages configuration option

Description
This PR adds a whitelistPackages configuration option to the FilteredStacktraceExceptionResolver. Given this configuration, the mentioned packages will always be shown in the stacktrace, while all others won't. additionalPackagesToIgnore are ignored as well as the built-in package list.
Checklist

[x] My code follows the style guidelines of the project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation

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

1.3.0
GitHub release

Your semantic-release bot :package::rocket:


python312Packages.{docling-core,docling-ibm-models}: fix build

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 356561

x86_64-linux

:white_check_mark: 12 packages built:

python311Packages.deepsearch-toolkit
python311Packages.deepsearch-toolkit.dist
python311Packages.docling-core
python311Packages.docling-core.dist
python311Packages.docling-ibm-models
python311Packages.docling-ibm-models.dist
python312Packages.deepsearch-toolkit
python312Packages.deepsearch-toolkit.dist
python312Packages.docling-core
python312Packages.docling-core.dist
python312Packages.docling-ibm-models
python312Packages.docling-ibm-models.dist

aarch64-linux

:white_check_mark: 12 packages built:

python311Packages.deepsearch-toolkit
python311Packages.deepsearch-toolkit.dist
python311Packages.docling-core
python311Packages.docling-core.dist
python311Packages.docling-ibm-models
python311Packages.docling-ibm-models.dist
python312Packages.deepsearch-toolkit
python312Packages.deepsearch-toolkit.dist
python312Packages.docling-core
python312Packages.docling-core.dist
python312Packages.docling-ibm-models
python312Packages.docling-ibm-models.dist

x86_64-darwin

:white_check_mark: 12 packages built:

python311Packages.deepsearch-toolkit
python311Packages.deepsearch-toolkit.dist
python311Packages.docling-core
python311Packages.docling-core.dist
python311Packages.docling-ibm-models
python311Packages.docling-ibm-models.dist
python312Packages.deepsearch-toolkit
python312Packages.deepsearch-toolkit.dist
python312Packages.docling-core
python312Packages.docling-core.dist
python312Packages.docling-ibm-models
python312Packages.docling-ibm-models.dist

aarch64-darwin

:white_check_mark: 12 packages built:

python311Packages.deepsearch-toolkit
python311Packages.deepsearch-toolkit.dist
python311Packages.docling-core
python311Packages.docling-core.dist
python311Packages.docling-ibm-models
python311Packages.docling-ibm-models.dist
python312Packages.deepsearch-toolkit
python312Packages.deepsearch-toolkit.dist
python312Packages.docling-core
python312Packages.docling-core.dist
python312Packages.docling-ibm-models
python312Packages.docling-ibm-models.dist


Updated copyright to 2015

Should still be 2014. It needs to be the earliest year.

Alternatively 2014-2015 could be used.

indeed, thank you for correcting me :)


Create Components package

The TopicApiClient implementation is currently only available in bindings_ffi however is useful in native rust Clients (Specifically in Cli-Client).
This PR creates a package called xmtp_components which makes useful implementations available in other packages.

@richardhuaaa  left some notes on #140 and pre-emptively gave it a 👍 to unblock you.
I'm not opposed to this plan; main driver is to be able to access a network implementation in as many places as possible so the solution you describe fits the bill perfectly.
I think there is an open question around if there should be 1 Package, where each domain is a module (e.g. Components/networking) or if each domain ought to get there own package (e.g. xmtp_networking, xmtp_storage, xmtp_wallet). Though I'm not picky here -- I agree with @neekolas's comments above, this is very changeable in the future.


remove new dictionaryexpression and keep as snippet only

Fixes https://github.com/microsoft/typespec/issues/3471

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.Generator.CSharp


Add extra tests to increase coverage

Coverage was inflated still because the files in tests were included. These files do not matter for coverage. Coverage is now run with --source=xopen so only the actual package is tested.
I added a html report to the coverage reporting. It makes it easy to check coverage. I added some tests for uncovered lines.
Consequently I found a bug in the peek method, which can only read binary files. I also removed some legacy code to increase the coverage (fspath workaround).

Coverage was inflated still because the files in tests were included.

Test files absolutely need to be included! Tests are code as well and the same mistakes can happen as in "normal" code. For example, I have written tests that were never executed because I accidentally had two functions with the same name.

For example, I have written tests that were never executed because I accidentally had two functions with the same name.

Wouldn't that show up as a reduced line coverage in the actual code?
Anyway, I enabled the tests code for coverage again.

Wouldn't that show up as a reduced line coverage in the actual code?

Perhaps, but line coverage isn’t foolproof, so it could just reduce branch coverage, or not even that.

Perhaps you could enable branch coverage while you’re at it? Should be as simple as adding branch = True under the [coverage:run] section in tox.ini.

@marcelm, oooh those graphs look nice. Strange that this is not enabled by default.

Totally agree!

And thanks for cleaning up the coverage configuration. I don’t remember why it ended up looking the way it did, but it’s much simpler now.

Merge ahead when you’re done, I don’t want to do it now in case you’re still changing something, but I need to work on something else.

No problem. These things just happen on old projects. Sometimes some good old refactoring is necessary. And I enjoy removing lines from a project. The less code the better, less maintenance! :wink:


default Bucket::request_timeout too low, or shouldn't be based on full transfer time

Describe the bug
When doing a Bucket::get_object_stream, if the file is very large, it will exceed the request_timeout and the download will fail.
I think this behavior violates the principle of least surprise; right now rust-s3 simply cannot be used by default on large files or slow or high-latency connections.
To Reproduce
let b = s3::bucket::Bucket::new(...).unwrap();
b.get_object_stream("path to a file larger than about 1GB on a reasonably fast connection", &mut writer);

This command will fail with TimedOut.
Expected behavior
By default, rust-s3 should allow one to download any sized file with the default settings.
Environment

Rust version: 1.59
lib version 0.30
"sync" feature enabled

Additional context
I think there should be no default timeout of the "entire request" kind, i don't think the class of error it can prevent is worse than the problem I experienced.
A more useful timeout that could be enabled by default would be "time to first byte".
Furthermore, documentation says the default timeout is 30 seconds, but the actual default timeout is 60 seconds according to the code. This tells me you found 30 seconds was too low at some point :)
Finally, thank you for the work you've put into this crate, it's very useful and you've done a great job!

@njaard I'm not sure how to address the issue, other then with a timeout, and since timeouts must exist there has to be a default. Since the timeout is in the underlaying implementation of HTTP clients used. Timeout for a bucket can be changed with a method, or at creation (since 0.31). I think I remember that in the days of yore the default timeout was None, which could cause the request to just hang forever, so a sensible timeout was chosen instead.
The 95% use case seems to be some sort of a timeout, and if you have a suggestion for a more ergonomic default or a mroe graceful handling of these issues I'd be happy to oblige :)

I think a more ergonomic default is "30 second connection timeout and unbound download timeout".
I think it's unfortunate that hyper has a timeout, and it appears that you're just following its lead, so I conducted a survey of other http libraries:
Has no default timeout on total transmission

curl
python's urllib
Go's http client
Java, 5 minute connection or inter-packet timeout, but not transfer time
firefox, 90 second connection timeout

Has a default timeout

rust's reqwest
C# (but there's the chance it's just time to connection or inter-packet time, I can't tell from documentation)

I think a more ergonomic default is: 60 second connection timeout and no transfer timeout, and then as a secondary feature, a 60 second time-to-next-packet timeout. Right now, an 8 GB file simply cannot be downloaded over a typical 1GBit connection by default, which I would call "pathological"; you could keep on increasing the timeout until you realize that the measure itself has no value.

Well, obviously this is a problem for upstream, for example: https://github.com/seanmonstar/reqwest/issues/870 so I'll close this ticket with my thanks!

Thank you, I love a good discussion :)

I’ve been actually thinking about moving away for reqwest, if there are other tokio compatible libs out there I’d be happy to give them a whirl


Support for devices using https over port 4443

Some devices (recent Audio Pro units like the "A10 MkII") expose the linkplay http api over HTTPS on port 4443. As far as I can tell python-linkplay only ever tries to connect on the standard port 443, which fails for these devices.
Would it be possible to implement support for trying multiple https ports?
Linkplay CLI seems to rely on iterating over a list of potential http ports, defaulting to only 4443.
Proof of potential communication
Using client-cert.pem extracted from consts.py I can run getStatusEx on my speakers, even though python-linkplay fails to connect to them:
$ curl -k -E client-cert.pem 'https://<IP_ADDRESS>:4443/httpapi.asp?command=getStatusEx'
{ "language": "en_us", "firmware": "audiopro_a10-user 1.56 1.56 1.56.503670 test-keys", "cast_ver": "1.56. 310669\n", "build": "user", "project": "A10MkII Speaker", "priv_prj": "A10MkII Speaker", .... }

No luck finding a way to auto-discover the port..
I tried to do research a way to resolve what port is being used through the mDNS announcements but is seems to only announce the UPNP port (59512):

The metadata exposed through the UPNP description (in my case http://<IP_ADDRESS>:59152/description.xml) doesn't seem to include a reference to the linkplay http/https port.
The GetControlDeviceInfoResponse soap response (from soap request to http://<IP_ADDRESS>:59152/upnp/control/rendercontrol1) gives a Status-field with lots of information about the device - including port used for tcp-uart communications, but no reference to port 4443.

It's also what the WiiM Home App does, I decompiled it for your other issue.


Refactored configuration file field names

Closes: #2242
Description
This PR refactored the TOML configuration file used by the ibc-relayer in order to have - (dash) instead of _ (underscore) for the field names.

PR author checklist:

[x] Added changelog entry, using unclog.
[ ] ~Added tests: integration (for Hermes) or unit/mock tests (for modules).~
[x] Linked to GitHub issue.
[x] Updated code comments and documentation (e.g., docs/).

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

imho there is no need for a changelog entry here since this is a fully cosmetic change. On the other hand the guide needs to be updated as well.

imho there is no need for a changelog entry here since this is a fully cosmetic change. On the other hand the guide needs to be updated as well.

Regarding the changelog, since this PR will break any relayer using a custom config file which has the old format, is it not better to log it in breaking-changes ? The old field names will cause an unknown field name error.
As for the guide, I updated the Hermes guide, but there is one link, section 3.3 Configuration, which redirects to https://github.com/informalsystems/ibc-rs/blob/v0.15.0/config.toml. As long as there isn't a new version with the updated config file format, I am not sure which link should be used.

Ah my bad, I thought the toml crate automatically mapped kebab-case fields to lower_dashes. Since this change is therefore not backward compatible, let's perhaps put it aside for now or figure out a way to make it work with both types of names.


[SMALLFIX] Randomly pick a worker correctly

Since LocalFirstPolicy is the default policy, the current implementation will always pick the same worker for multiple threads, i.e. Performance.java

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15622/
Test PASSed.

@danielfree Thanks for the fix. Could you add a unit test to validate the behavior? Also could you target this to branch-1.5 instead of master?


cpplint: Harmonize with stan-dev/math

Submission Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary
Updates cpplint so python 2 is no longer required.
This change ONLY makes sense when https://github.com/stan-dev/math/pull/1871 has been merged.
Intended Effect
No more warnings about python 2 while running cpplint
How to Verify
make cpplint
Side Effects
VERY dependent on this:
https://github.com/stan-dev/math/pull/1871
Documentation
N/A
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Rohit Goswami <rg0swami[at]yahoo.com>
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Will approve once Math change propagates. Thanks!


Eliah Kagan: Watch cracksystem.com

Eliah Kagan requests the watch of the watch_keyword cracksystem\.com. See the MS search here and the Stack Exchange search here.

cracksystem\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


[Bug] Overlapping Console Output

Bug Report 🐛

Version of Majestic: 1.2.20
Version of Jest: 20.0.3
Version of Node: v8.15.1
Operating System: macOS Mojave

Cannot Reproduce (Large, Enterprise Source Code)
When posting multiple console.log()s and getting warnings the text in the console output view overlaps to the point it's unreadable. You cannot see the dropdowns from objects printed in the console.
Example:

Another example

Upgraded to<EMAIL_ADDRESS>(1.2.24) and the problem persists.

Update:
After some testing this only occurs when using Safari to view Majestic. Chrome works fine with the text output.

I recommend adding a section in the bug reports for browser type.


App in Foreground Receives Push Notification Prompt

ITS-Pro time category: https://its-pro.ucsd.edu/browse/MA-60
This is complete when:

[ ] Push notifications are received when the app is in the foreground on iOS
[ ] Push notifications are received when the app is in the foreground on Android

References:

iOS: https://pub.dev/packages/flutter_local_notifications#-ios-setup
Android: https://pub.dev/packages/flutter_local_notifications#-android-setup

https://firebase.google.com/docs/cloud-messaging/concept-options

Note: When foreground push notification comes in, the app automatically reroutes to the notifications tab no matter what screen it's on. There is logic to route to the maps tab on the background & app closed push notifications on-click, but foreground doesn't have that, so my thought is that it has to be something else.

The automatic rerouting has been disabled, now working on making the route to the notifications tab on click of the push notification.

Android testing all PASS


Please help

Sent Btc to address and only received of portion on receiving end.

Sent $1500.00 ended up with $14.00

did you add a change output?
What is your transaction ID? Which address did you send to?

How is your balancing looking now?


[SP-5826] Add a kettle property to control the size of the

ArrayBlockingQueue used to signal when steps are finished.  Set new
default high enough to avoid it filling up in the future.
This commit is a cherry-pick from master 3b9592ef0d

:white_check_mark: Build finished in 30m 8s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core,engine

:ok_hand: All tests passed!
Tests run: 4795, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 30m 8s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core,engine

:ok_hand: All tests passed!
Tests run: 4795, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


Cursor pointer on folder row

https://keybase.atlassian.net/browse/DESKTOP-944

@keybase/react-hackers

:shipit:


Run Biff without RocksDB?

One of my systems is a very old Mac and RocksDB won't run on it:
Execution error (UnsatisfiedLinkError) at jdk.internal.loader.NativeLibraries/load (NativeLibraries.java:-2).
/private/var/folders/p1/30gnjddx6p193frh670pl8nh0000gn/T/xtdb_rocksdb-6.12.7/librocksdbjni-osx-x86_64.jnilib: dlopen(/private/var/folders/p1/30gnjddx6p193frh670pl8nh0000gn/T/xtdb_rocksdb-6.12.7/librocksdbjni-osx-x86_64.jnilib, 1): Symbol not found: __ZdlPvSt11align_val_t
  Referenced from: /private/var/folders/p1/30gnjddx6p193frh670pl8nh0000gn/T/xtdb_rocksdb-6.12.7/librocksdbjni-osx-x86_64.jnilib
  Expected in: /usr/lib/libc++.1.dylib
 in /private/var/folders/p1/30gnjddx6p193frh670pl8nh0000gn/T/xtdb_rocksdb-6.12.7/librocksdbjni-osx-x86_64.jnilib

Is there a way to run Biff locally for development without using RocksDB?

Yes, you can override the default XT config by setting :biff.xtdb/opts in config.edn and have it use LMDB instead:
{...
 :dev {...
       :biff.xtdb/opts {:xtdb/index-store {:kv-store {:xtdb/module xtdb.lmdb/->kv-store
                                                      :db-dir "storage/xtdb/index-lmdb"}}
                        :xtdb/document-store {:kv-store {:xtdb/module xtdb.lmdb/->kv-store
                                                         :db-dir "storage/xtdb/docs-lmdb"}}
                        :xtdb/tx-log {:kv-store {:xtdb/module xtdb.lmdb/->kv-store
                                                 :db-dir "storage/xtdb/tx-log-lmdb"}}}}}

And update deps.edn:
{...
 :deps {com.biffweb/biff {...
                          :exclusions [com.xtdb/xtdb-rocksdb]}
        com.xtdb/xtdb-lmdb {:mvn/version "1.21.0-beta2"}}}

Works perfectly! Thank you. Yes, setting up deps.edn so it works differently for dev/prod via aliases would be the next step but this at least lets me play with the framework.
Is LMDB not recommended for production then?

Great!

Is LMDB not recommended for production then?

In general I don't have any opinion on it beyond what the XT docs say about rocksdb vs lmdb. But now that you mention it, if you're using lmdb in dev, I probably would recommend also using it in prod to keep things the same.

Perhaps you could add a note to the Biff docs showing how to use lmdb instead of rocksdb?

Just made a release which adds a :biff.xtdb/kv-store config option which can be set to :lmdb, to make this a bit easier. That also avoids a problem that I missed earlier: if you use the value of :biff.xtdb/opts I gave above in the :prod section and you set :biff.xtdb/topology :jdbc, the jdbc options will get clobbered. I added a Troubleshooting section to the docs with instructions for LMDB using the new option: https://biffweb.com/docs/#unsatisfiedlinkerror. And there's a new release here with upgrade instructions: https://github.com/jacobobryant/biff/releases/tag/v0.4.2-beta

Cool. Thanks. Will take another look at Biff in a week or two when I get another block of spare time.


improve test structure for collection__element_by_condition__lazy_search_test.py

child of #313

will do

Hi, Is this issue still open to fix or someone has already fixed it?

It's in progress)


Make sure all background tasks are killed when expired

If the app is background/foregrounded very quickly, we can't guarantee that we end all the tasks after they expire since self.taskId keeps a reference to the last executed task on the background.

:+1:


feat: add details modal

This PR adds the Portfolio Project Details Modal following the design and layout in the Assignment Link
This milestone is used to implement a popup window that includes the project details in both desktop and mobile, In order for that to be possible, I store the information about your projects in a JavaScript object.

also update your PR description to have the link to the figma design

you're definitely getting closer ,do you notice the overflow below plz lets fix that


fix: Recipies broken link in README.md

Noticed that the Recipes bullet did not have a link associated with it. Hence, have added the link of the first web-hook under the Recipies section from the Configu docs in README.md

Hi @IAmRiteshKoushik , check out the https://github.com/configu/configu/issues/266#issuecomment-1826770636 for details regarding the Hacktoberfest rewards


Full Validation Error Object passed to client promise

Steps to reproduce
I have the problem that a validation error in feathers-sequelize is not completely(not the whole object) passed to the catch block of my client's service promise. More precisely, after looking into it, either the problem is that the error is "converted" here(https://github.com/feathersjs/feathers-rest/blob/master/src/client/base.js#L60) or the actual error lib is doing something wrong here(https://github.com/feathersjs/feathers-errors/blob/master/src/index.js#L216);
In the latter case i fixed it by forcing it to extend to an object. So the Code in Line 216 in the error lib(2nd link) is now actually:
  if ((typeof error === 'undefined' ? 'undefined' : _typeof(error)) === 'object') {
    return _extends({}, result, error);
  }

Expected behavior
Seeing the full error object, with the error array, statusCode etc.

Actual behavior
I'm only getting the concatinated error message:

System configuration
Module versions:
"feathers-rest": "^1.6.0",
"feathers-errors": "^2.5.0",
NodeJS version:
7.5.0
Operating System:
Windows 10 64
Browser Version:
FF 51.0.1

Here is my sequelize model:
  const user = sequelize.define('users', {
    email: {
      type: Sequelize.STRING,
      allowNull: false,
      unique: {
        args: true,
        fields: [sequelize.fn('lower', sequelize.col('email'))]
      },
      validate: {
        isUnique: function (value, next) {
          var self = this;
          user.find({where: {email: value}, attributes: ['id']})
            .then(function (user) {
              // reject if a different user wants to use the same email
              if (user && selef.id !== user.id) {
                return next('Email already taken.');
              }
              return next();
            })
            .catch(function (err) {
              return next(err);
            });
        }
      }
    },
  });

When using the Feathers client, errors get converted back into a feathers-error. Error objects are not easily console.log-able (but should have all the properties).. Try calling error.toJSON() to get it as an object.

you are right! Oh man, although i was sooo sure that i was actually not able to get the object attributes.

It's a little weird, which is why we had to do the https://github.com/feathersjs/feathers-errors/blob/master/src/index.js#L60 hack but we figured they should be normal JavaScript errors on the client as well which is why they are converted back.


[BUG] - PowerBI Visual not loading Custom Map style

My Mapbox Style is published and public as well as the tilesets but it is not loading into my powerbi visual. I tried title sets that were SHP, GeoJson and same results with both.
Tried redoing the styles, making sure they were public, and double checking for any errors
The only conclusion I can come to is that there is a bug. Please advise

Same problem

I too have this. If I create a new map it wont load the custom style and playing about results in an error about hills.
I have got around it by copying an older map and using that as a starting point. Those load fine. But... it has a box come up when editing the map saying it can be updated. If you say yes to this then the map breaks again so dont do that.

Update: Just seen there is an updated version here on Github that solves the problem. mapbox://styles/dannyoneill/clsotavfh02c301qy6ffr07f2 You need to upload manually and change all your maps to the new visual as it doesnt update the existing store install.

It's working for me !

I have the same issue, my tile sets load fine but I´m trying to add a custom Map Style and it doesn´t load it, it shows a blank background instead


Added a notebook for testing the accuracy of get_panel()

This notebook is used to show the efficacy of finding panel members in case documents. It compares different lists of judges, as search patterns for panel members, using the code that is currently implemented. It then uses a hard-coded list of judges, alongside SpaCy's Pattern Matcher, to achieve results that correctly identify panel members approximately 97% of the time. This shows that the Phrase Matcher should be used instead of the current method.
To view the actual notebook, click on Files changed, find the ... under Review changes, and click View file from the submenu.

Thank you for this tool!


Choose the metatags.twig template location

It would be nice if I could select where to the save metatags template, instead of the theme's default root. Generally I save it into a /partials sub-folder.
Thanks for this extension it's super useful.

Since I'm using the extension with Bolt 3.* the _metatags.twig is no longer being picked up from the theme folder. Should it be inside a specific folder structure in the theme folder?

I've just noticed this also.

This is due to the template being loaded in the Twig namespace of @bolt, which the theme path is very deliberately not included in.
I am presuming this is to prevent them being overridden.

@bobdenotter can you clear up what the intention is? The instructions in the README don't seem to apply anymore: https://github.com/bobdenotter/seo#configure-the-meta-tags-output

@bobdenotter Hi, the same for me.. Overwriting _metatags.twig still possible ?

I'm seeing the same behaviour on Bolt 3.0.7 with the dev-master of this extension.
I am pretty sure this is not intentional. @GawainLynch could you elaborate more about the Twig namespace? How can this be fixed? Perhaps I can work on a PR.

The behaviour isn't Bolt itself so much as the configurable options.
Basically here you could add:
# templates:
#     meta: @bolt/_metatags.twig

Note that they are probably best left commented out by default, but the example keeping the system default so that if accidentally uncommented it won't break things.
Then here:
protected function getDefaultConfig()
{
    return [
        'templates' => [
            'meta' =><EMAIL_ADDRESS>        ]
    ];
}

Then here
        $html = $this->app['render']->render($this->config['templates'['meta'], $vars);


Unable to login in Hub : The POST method is not supported for route hub/login.

I have installed in my local Ubuntu 22.04 Laptop but i am unable to login in hub. Please help me to solve
https://flareapp.io/share/yPa2REY7#top

Lunar version: 0.3.1
Laravel Version: 8.1.17
PHP Version: #.#.#
Database Driver & Version:

Sounds like the Livewire assets are not loading. Please check the browser console. This is a common Livewire issue.

Please help me to fix

Community support is available in Discord or you could Google it, plenty of results.

Not sure what is happening, but I had the same problem and when I went to refresh my admin login page and re-login... I was successful. If it happens again I will try to capture the logs and determine if there is a fix / work-around.


New boot config and EEPROM firmware version

Hmm... Maybe having POWER_OFF_ON_HALT=0 and WAKE_ON_GPIO=1 or so on CM4 is actually good, since at least with POWER_OFF_ON_HALT=1 WAKE_ON_GPIO+0 the CM4 reset button (connected to RUN_PG) won't work after you have run poweroff (the watchdog still works though, since it's connected to GLOBAL_EN)

We need to consider that with ENABLE_SELF_UPDATE there is a small chance that on first boot we might flash what we put on the factory image currently, which is an older EEPROM with a slightly different config. It seems however that currently, something about the format of the pieeprom.sig file or otherwise is preventing SELF-UPDATE from happening.
SIG pieeprom.sig b1c0fd22ae38c7ce62f5cbc88d56c90f13679281d1aefe183e14864cbe6dcec1 0
SELF-UPDATE timestamp current<PHONE_NUMBER> new 0 skip

regular recovery.bin-based update, as we do on RPi4, does not care about this detail.

I found out that for the SELF-UPDATE mode of reflashing to function, it requires:

ENABLE_SELF_UPDATE=1 in the EEPROM config
pieeprom.sig must contain a second line with a timestamp that is newer than when the firmware was last flashed, like this:

b1c0fd22ae38c7ce62f5cbc88d56c90f13679281d1aefe183e14864cbe6dcec1
ts:<PHONE_NUMBER>

We do not put this timestamp in the pieeprom.sig in the factory image, so we do not need to worry about the EEPROM contained in the factory image reflashing EEPROM on first boot (unless of course, we would like for it to function in that manner).

Since we are looking at using booting from a USB stick, and then flashing from within a Linux environment in production, perhaps this repo won't be neccessary.


pull request for e2e test at 11/18/2016 05:26:06

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[CT-1712] [Bug] information schema columns not included in dbt docs for non-default database

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
With a default database profiles.yml of e.g. ods:
my_project:
  target: local
  outputs:
    local:
      database: 'ods'

and over-ridden database of e.g. dwh for some model paths in dbt_project,yml:
models:
  my_project:
    marts:
       +database: `dwh`

Dbt docs generate only includes information schema information (columns not in models, data types for all columns) for models in the default database of ods and not the over-ride of dwh.
Expected Behavior
dbt docs should include information schema information for models in databases other than the default.
Steps To Reproduce
Override the database in config as above, then:
dbt compile [other args]
dbt docs generate --no-compile
Note that catalog.json only includes tables in the default database.
Note that columns do not contain full information in the documentation for non-default databases.
Relevant log output
No response
Environment
- OS: Windows 10
- Python: 3.10.1
- dbt: 1.3.0

Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
sqlserver

Thanks for reaching out @rtooker !
Using dbt-snowflake, I created a dbt_project.yml like you described:
models:
  my_dbt_project:
    +materialized: table
    marts:
       +database: analytics
       +schema: DBT_DBEATTY_DBT_UTILS

My profiles.yml has the following default database:
      database: JAFFLE_SHOP

Then created a (very simple) model in the marts folder:
models/marts/my_little_table.sql
select 1 as my_number

After running dbt docs generate, I could see this model in my target/catalog.json:
jq . target/catalog.json > target/catalog.pp.json
    "model.my_dbt_project.my_little_table": {
      "metadata": {
        "type": "BASE TABLE",
        "schema": "DBT_DBEATTY_DBT_DBEATTY_DBT_UTILS",
        "name": "MY_LITTLE_TABLE",
        "database": "ANALYTICS",
        "comment": null,
        "owner": "TRANSFORMER"
      },
    ...

And running dbt docs serve gave me this:

It sounds like you might be using the dbt-sqlserver adapter?
Based on the above, this doesn't look like a bug in dbt-core to me, and I suspect that it is an edge case not covered within the dbt-sqlserver adapter. Could you try opening an issue there instead?
I'm going to close this in the meantime, but we can open it back up again if it doesn't indeed turn out to be a bug in dbt-core.


[SYSTEMML-857][SYSTEMML-858] Release process for docs and version

Describe release process for documentation.
Update documentation version in _config.yml.
Add version number to global documentation header.

Preview here: http://deroneriksson.github.io/incubator-systemml/release-process.html

Renders correctly on OS X with Firefox, Chrome, and Safari. Will try out Windows browsers tonight.

Added white-space nowrap to projecttitle class to prevent title from wrapping with IE10 on Windows.

Verified version number shown on Windows with IE11.  Thanks for doing this Deron!
LGTM

Thank you for reviewing @gweidner! I will merge.


Rename OpenedContract to SandboxContract

Lgtm

Merged here https://github.com/ton-community/sandbox/commit/b54dae2db99ebf4f71375bad3babf6ae89b0e360


Streamlined logic

removed string -> int -> string conversion

renamed column property to col for inline usage

Thanks @fearphage! 🙂


Validate Composer config in CI

PHP Extension and Composer packages installation goes into "install"

Rebased on latest master in #533.


[M1] Notifications: "Couldn't start client Razor Language Server" pop up when open razor project.

Steps to reproduce

Create a razor project via CLI.
Open it in VScode.

Expected  behavior
Open razor project without any notifications.
Actual behavior
Notifications: "Couldn't start client Razor Language Server" pop up when open razor project.

Environment data
dotnet --info output:
.NET SDK:
Version:   7.0.100-rc.1.22401.1
Commit:    bceb18f027
Runtime Environment:
OS Name:     Mac OS X
OS Version:  12.5
OS Platform: Darwin
RID:         osx.12-arm64
Base Path:   /usr/local/share/dotnet/sdk/7.0.100-rc.1.22401.1/
Host:
Version:      7.0.0-rc.1.22381.5
Architecture: arm64
Commit:       508fef51e8
.NET SDKs installed:
7.0.100-rc.1.22401.1 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 7.0.0-rc.1.22380.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 7.0.0-rc.1.22381.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Other architectures found:
None
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download
VS Code version:1.69.2
C# Extension version:1.25.1

Not repro on Mac Intel chip and windows arm64.

With SDK:8.0.100-alpha.1.23062.10 from https://github.com/dotnet/installer and latest C# extension 1.25.3 v1.25.3 installed, this issue doesn't repro on VSCode(1.74.3) now.


Add Danish translation

Hey do you want a Danish translation for the basic strings as well @tonybaloney ? :)

Sure!


Tensorflow unsupported within MSYS2?

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
TensorFlow installed from (source or binary): wanted binary .whl via python3 -m pip install tensorflow
TensorFlow version: any would be fine, was trying for 2.6.3
Python version: 3.9
Installed using virtualenv? pip? conda?: pip
CUDA/cuDNN version: no GPU

Describe the problem
On MSYS2, using pip via the mingw64-compiled Python, the message is
# python3 -m pip install --upgrade https://files.pythonhosted.org/packages/f2/ff/32e0f1e039fb6cabc88a5e03a0a2b2f01cd50b69cc1b915daf80ca0345c5/tensorflow-2.6.3-cp39-cp39-win_amd64.whl
ERROR: tensorflow-2.6.3-cp39-cp39-win_amd64.whl is not a supported wheel on this platform.

It's the same if I just use the name eg python3 -m pip install tensorflow.
I have an extensive codebase that currently depends on MSYS2 and gcc in the Windows context, and we have a module that successfully uses Tensorflow on our Linux version of the code. As above, however, I can't use Tensorflow via Python under MSYS2 using the version Python that MSYS2 provides.
I wonder if I could get some clarity on what the options are for Windows/MSYS2 therefore:

can tensorflow be built on Windows using gcc in MSYS2? The instructions, even if they use MSYS2, seem to be referring to MSVC as the compilier. What are the reasons why 'full' MSYS2 support is not possible? *
should I instead switch, if possible, to building my software to link against Windows Python instead of MSYS2 Python. This would be less convenient for users, but might work.
would it be possible for the situation regarding MSYS2 support to be clarified in the MSYS2 documentation somehow?

[*] I note that https://www.tensorflow.org/install/source_windows says that there is some issue with path support in Windows by Bazel, but obviously Tensorflow builds find on Linux, where such paths exist. Is this a Bazel configuration issue?

@jdpipe ,
Can you please confirm is there any specific reason to use tf v2.6.3, please try with stable v2.7 and let us know if you are facing same issue.Thanks!

Hi @tilakrayal,
I tried the following instead:
pye@DESKTOP-6ADQVP0 MINGW64 ~/solartherm
# python3 -m pip install --upgrade "https://files.pythonhosted.org/packages/dd/0b/6fd33732d436a6735094b6e44359e13c10901e71aeaf348ff7c9e4ee08c9/tensorflow-2.8.0-cp39-cp39-win_amd64.whl"
ERROR: tensorflow-2.8.0-cp39-cp39-win_amd64.whl is not a supported wheel on this platform.

and also
pye@DESKTOP-6ADQVP0 MINGW64 ~/solartherm
# python3 -m pip install --upgrade "https://files.pythonhosted.org/packages/af/e0/d1e53ca7411b0dbe8d82afafd39aab5aafaa02fa5d22c3c226a61f349f19/tensorflow-2.7.1-cp39-cp39-win_amd64.whl"
ERROR: tensorflow-2.7.1-cp39-cp39-win_amd64.whl is not a supported wheel on this platform.

and also
pye@DESKTOP-6ADQVP0 MINGW64 ~/solartherm
# python3 -m pip install tensorflow
ERROR: Could not find a version that satisfies the requirement tensorflow (from versions: none)
ERROR: No matching distribution found for tensorflow

pye@DESKTOP-6ADQVP0 MINGW64 ~/solartherm
# which python3
/mingw64/bin/python3

Note here that I am using the Python that is provided by MSYS2 (MinGW64), which is not the same as 'regular' CPython for Windows. It seems that the PyPI packages for Tensorflow are being deliberately blocked for use on MSYS2 somehow, and I'm not sure if that's deliberate (nothing in the documentation that I could see) or on purpose (would be nice to know the reason).

Further to the above, I note that I typed python3 -m pip debug --verbose and got the following output:
Compatible tags: 33
  cp39-cp39-mingw_x86_64
  cp39-abi3-mingw_x86_64
  cp39-none-mingw_x86_64
  cp38-abi3-mingw_x86_64
  cp37-abi3-mingw_x86_64
  cp36-abi3-mingw_x86_64
  cp35-abi3-mingw_x86_64
  cp34-abi3-mingw_x86_64
  cp33-abi3-mingw_x86_64
  cp32-abi3-mingw_x86_64
  py39-none-mingw_x86_64
  py3-none-mingw_x86_64
  py38-none-mingw_x86_64
  py37-none-mingw_x86_64
  py36-none-mingw_x86_64
  py35-none-mingw_x86_64
  py34-none-mingw_x86_64
  py33-none-mingw_x86_64
  py32-none-mingw_x86_64
  py31-none-mingw_x86_64
  py30-none-mingw_x86_64
  cp39-none-any
  py39-none-any
  py3-none-any
  py38-none-any
  py37-none-any
  py36-none-any
  py35-none-any
  py34-none-any
  py33-none-any
  py32-none-any
  py31-none-any
  py30-none-any

Meanwhile, if I type  python3 -m pip download tensorflow --platform win32 --python-version 3.9 -vv --no-deps then I get this output:
[...]
d72c28c6c6fdda814fd68b957a3d206f4df5/tensorflow-2.8.0-cp37-cp37m-macosx_10_14_x86_64.whl#sha256=fa4a723368d5f748b6f4ec305cf7c26b98e4a6a8c2ce1425f8ae10383a37bcfc (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp37-cp37m-manylinux2010_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/31/66/d9cd0b850397dbd33f070cc371a183b4903120b1c103419e9bf20568456e/tensorflow-2.8.0-cp37-cp37m-manylinux2010_x86_64.whl#sha256=05fb161c6b2a6c4b8317a703a0a6d7f7aa6b5e3c6ea31bbc4f44ef96b89c3344 (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp37-cp37m-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/fe/36/7c7c9f106e3026646aa17d599b817525b139e2870f75b532318573cbabd4/tensorflow-2.8.0-cp37-cp37m-win_amd64.whl#sha256=291fa84f1022914580810ad76732fb254e44a8a609128e1c58873a12b2f81559 (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp38-cp38-macosx_10_14_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/e9/6b/a4b872afe267184051a716aae58f1f9d8ebb456ecce7edece70a07c15f56/tensorflow-2.8.0-cp38-cp38-macosx_10_14_x86_64.whl#sha256=dd0f9f113ebc21b73fcd349db1629e187b8686395b8146d100eb1706a943bbc0 (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp38-cp38-manylinux2010_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/2f/45/f5c91d69c2121e8e60673164bdcd2c6cda7b89e37decbc3c01b0466ca990/tensorflow-2.8.0-cp38-cp38-manylinux2010_x86_64.whl#sha256=8489b4f1771e146f752b0eaeb57acf183bd07357e4550464e7dff18b3b656b5d (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp38-cp38-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/17/5b/dac6e0607e4186b9e157597cd96d945aa769c60ef9f9f1b7ddc174f39332/tensorflow-2.8.0-cp38-cp38-win_amd64.whl#sha256=da38d4043185267e7316ae5dc98d18e89c8af4170859f64798e7a3607fd606e3 (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp39-cp39-macosx_10_14_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/80/26/2990ee24ea5ef5ece557828ce295abc75e5b6c0c8ebf571a842f6e1125db/tensorflow-2.8.0-cp39-cp39-macosx_10_14_x86_64.whl#sha256=52f225fecc688281b3ae2cba2b52d3ed6215ed4a3ffb686b9cfd09885ca65563 (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp39-cp39-manylinux2010_x86_64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/b9/39/88799b7257f73482d4c77bc18c068902a91629c6d380db88cc28ede44fd5/tensorflow-2.8.0-cp39-cp39-manylinux2010_x86_64.whl#sha256=9d91a989e5455ae713c03fd7236071ab3f232ad8ff2831f2658072933546091f (from https://pypi.org/simple/tensorflow/)
  Skipping link: none of the wheel's tags (cp39-cp39-win_amd64) are compatible (run pip debug --verbose to show compatible tags): https://files.pythonhosted.org/packages/dd/0b/6fd33732d436a6735094b6e44359e13c10901e71aeaf348ff7c9e4ee08c9/tensorflow-2.8.0-cp39-cp39-win_amd64.whl#sha256=b360c13b3e58b9a5c0780cbdb6b549eea73f620275fa203f8508fe418ae02735 (from https://pypi.org/simple/tensorflow/)
[...]

Which clearly indicates that it is the 'platform tag' that is causing the problem here. In short, cp39-cp39-win_amd64 doesn't match with cp39-cp39-mingw_x86_64.
The question is, does the platform need to be so restrictive here? If Python/Wheel wasn't blocking me, would this module actually work, or not? Is this a MSYS2 issue or a TensorFlow issue, I wonder?
https://www.python.org/dev/peps/pep-0425/#platform-tag

One more thing. If I manually unzip the .whl file
wget "https://files.pythonhosted.org/packages/dd/0b/6fd33732d436a6735094b6e44359e13c10901e71aeaf348ff7c9e4ee08c9/tensorflow-2.8.0-cp39-cp39-win_amd64.whl"
mkdir ~/tmpwhl
cd ~/tmpwhl
bsdtar xvf ../tensorflow-2.8.0-cp39-cp39-win_amd64.whl

and then 'trick' Python into importing that package:
pye@DESKTOP-6ADQVP0 MINGW64 ~/tmpwhl
# PYTHONPATH=. ipython3
Python 3.9.7 (default, Nov 21 2021, 22:02:56)  [GCC 11.2.0 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 7.30.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import tensorflow
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
C:/msys64/home/pye/tmpwhl/tensorflow/python/pywrap_tensorflow.py in <module>
     63   try:
---> 64     from tensorflow.python._pywrap_tensorflow_internal import *
     65   # This try catch logic is because there is no bazel equivalent for py_extension.

ImportError: DLL load failed while importing _pywrap_tensorflow_internal: The specified module could not be found.

During handling of the above exception, another exception occurred:

ImportError                               Traceback (most recent call last)
<ipython-input-1-d6579f534729> in <module>
----> 1 import tensorflow

C:/msys64/home/pye/tmpwhl/tensorflow/__init__.py in <module>
     39 import sys as _sys
     40
---> 41 from tensorflow.python.tools import module_util as _module_util
     42 from tensorflow.python.util.lazy_loader import LazyLoader as _LazyLoader
     43

C:/msys64/home/pye/tmpwhl/tensorflow/python/__init__.py in <module>
     38 # pylint: disable=wildcard-import,g-bad-import-order,g-import-not-at-top
     39
---> 40 from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow
     41 from tensorflow.python.eager import context
     42

C:/msys64/home/pye/tmpwhl/tensorflow/python/pywrap_tensorflow.py in <module>
     77     sys.setdlopenflags(_default_dlopen_flags)
     78 except ImportError:
---> 79   raise ImportError(
     80       f'{traceback.format_exc()}'
     81       f'\n\nFailed to load the native TensorFlow runtime.\n'

ImportError: Traceback (most recent call last):
  File "C:/msys64/home/pye/tmpwhl/tensorflow/python/pywrap_tensorflow.py", line 64, in <module>
    from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: The specified module could not be found.

Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors for some common causes and solutions.
If you need help, create an issue at https://github.com/tensorflow/tensorflow/issues and include the entire stack trace above this error message.

In [2]:

I opened _pywrap_tensorflow_internal.pyd using Dependency Walker, and found that the file that was missing was PYTHON39.DLL. On MinGW64, this file is called libpython3.9.dll, so I made a copy of the MinGW64 file, and renamed it to the expected name python39.dll.
I then made a tiny bit more progress, namely:
pye@DESKTOP-6ADQVP0 MINGW64 ~/tmpwhl
# ipython3
Python 3.9.7 (default, Nov 21 2021, 22:02:56)  [GCC 11.2.0 64 bit (AMD64)]
Type 'copyright', 'credits' or 'license' for more information
IPython 7.30.1 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import tensorflow
2022-02-13 07:08:14.285665: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'cudart64_110.dll'; dlerror: cudart64_110.dll not found
2022-02-13 07:08:14.400592: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.

This looks like it's getting a little bit further, and attempting to dlopen some CUDA-related stuff, and my system doesn't have CUDA, so I guess it fails. But presumably, it should not be crashing out of Python in this case.
All in all, it looks like the mingw_x86_64 'platform tag' makes sense, because the DLL for Python has a different name on this platform compared to win_amd64, and that means that platform-sensitive Python modules need to be compiled differently on this platform.
Having established that, are there any suggestions for how to compile Tensorflow such that it works with the MSYS2-MinGW64 version of Python?

@jdpipe ,
Can you please take a look at this link for the issue with the similar DLL error.It helps.Thanks!

Hi @jdpipe ,
The prebuilt binaries for windows are of win_amd64.whl type and seems not supporting for mingw_x86_64 architecture.
You have option for Build from source using MSYS shell. Please refer to the documentation here for same. May be this can be helpful for your case.
Please check and confirm if this solves your purpose. Thank you!

Hi @SuryanarayanaY,
Thanks for the documentation link. It says that one can build using the MSYS2 bash shell.
But would this produce a version of Tensorflow that is built using MINGW's GCC and links to the MINGW version of Python?
The instructions say to use the MSYS2 shell, but then all of the instructions for installing dependencies, specifically MS Visual C++ Build Tools, etc. (ie "then follow the previous instructions for the Windows native command line").
I feel that the instructions are not really sufficiently clear. For example, if using MSYS2, and I want to use the MSYS2 version of Python, why would I install Windows Python? It would be helpful to have an end-to-end set of instructions for building on MSYS2, using native MSYS2 GCC and Python, etc.
It would be even better if PyPI could host the resulting packages ;-) But as noted, there may be issues with CUDA support in MSYS2 (not a big deal for me, but certainly it would be for others).

I'm in a similar situation. I need to adapt an open source application that was build under Windows using MYSYS2. Now we want to add a tensorflow model to the application. Two things are now bothering us. First tensorflow doesn't work under MYSYS2 (at least we can't get it to build/work). Secondly, From Tensorflow 2.11 GPU support is only under WSL2, but not anymore under Windows directly. GPU accelerated computing is really crucial.

Most likely this should be closed as duplicate of #36167


Get the hand state

It would be nice if there was some way to get the hand state of a player. What I mean with this is to get if a hand is being used (rightclicking). In forge you have stuff like player.isHandActive() or player.getActiveItemStack(). One example of a use for this would be to do something special if a player is using a shield.
While it is possible to do something similar using UseItemStackEvent it feels cubersome, and also doesn't give you information about which hand the action happened in.

I would add a key Key<OptionalValue<HandType>> to represent the active hand and you should be able to get the ItemStack through the inventory api. A helper method would still be nice though.

What I was thinking as well. Even though from what I've seen vanilla keep the two concepts seperate I can't think of any case where that would really matter.

related:
https://github.com/SpongePowered/SpongeAPI/blob/bleeding/src/main/java/org/spongepowered/api/entity/ArmorEquipable.java#L125-L145
https://github.com/SpongePowered/SpongeAPI/blob/bleeding/src/main/java/org/spongepowered/api/data/property/entity/DominantHandProperty.java
https://github.com/SpongePowered/SpongeAPI/search?utf8=✓&q=HandType&type=Code
@ZephireNZ was working on hand stuff, maybe will continue?

PR merged (https://github.com/SpongePowered/SpongeAPI/pull/1969)


Failure when writing multipart to several zdbs

Issue migrated from https://api.github.com/repos/gigforks/minio/issues/70, opened by @grimpy
Expected Behavior
Able to write data with minio client
Current Behavior
Error happens when writing to minio with minio client
Using the following script i got errors writing to a minio setup to work against 4 zdbs
https://github.com/gigforks/minio/pull/66/files
Errors:
https://gist.github.com/grimpy/027fb3ef479d199411ac37b75c5d1dc8
Config used:
namespace: minio
password: rooter
datastor: # required
  shards: # required
    - <IP_ADDRESS>:9910
    - <IP_ADDRESS>:9911
    - <IP_ADDRESS>:9910
    - <IP_ADDRESS>:9911
  pipeline:
    block_size: 1048576
    compression: # optional, snappy by default
      type: snappy # snappy is the default, other options: lz4, gzip
      mode: default # default is the default, other options: best_speed, best_compression
    encryption: # optional, disabled by default
      type: aes # aes is the default and only standard option
      private_key: c2ym8g9b6sxow5ridf56gb9885wxb10i
    distribution:
      data_shards: 4

*commented by @iwanbk
Just FYI, writing files is a must-to-do tests for me.
So this bug is quite strange.
I'll try to mimic your config.*

*commented by @iwanbk
Hi @grimpy
I've tested it with latest code from zerostor branch, no issue for me.
I've tested it with small file and big (369M) file.
You might want to try these suggestions:

Did you use multiple/distributed minio? If yes please make sure you don't use filemeta, use mongodb meta instead
this config

    distribution:
      data_shards: 4

this part is actually quite strange, and i don't really sure how 0-stor works when got this config.
disribution with data_shards: 4  means we use erasure encoding with 4 data_shards? At least we need to spare some shards for the parity_shards, right?
(I've tested with above config as well, still working, it might be some config bug in 0-stor config).
So, please try it with  :

data_shards: 3
parity_shards: 1*

*commented by @muhamadazmy
I helped with debugging the issue, and it seems the problem is in the client side. Not minio nor the setup. Using other clients works perfectly fine.
@grimpy can review the test script, or try other versions of the python client.*

*commented by @zaibon
Data_shard: 4 is perfectly valid. This means we replicate the block on 4 shards. There is no erasure coding, just replication *

commented by @iwanbk
FYI, i've tested with the python client as well, and it worked.
(already reported to telegram chat)

this https://github.com/threefoldtech/minio/commit/669708f2facfe94a4b84282652a79a422a741300 fixed the issue


Update the docs for Google pub/sub

This pull request updates the Google pub/sub documentation to have the address in the referenced Provider secret instead of the spec. This is because the address for Google Pub/Sub is the project-id and fails the URL validation for the field.
We should also reconsider the validation for the spec.address field and how the current validation prevents some values from being specified in the spec. Some Providers (e.g. Azure EventHub) have address values that wouldn't pass the validation and use the address field instead of the secret instead. But this can come up after there has been some discussion around possible solutions.

@somtochiama I opened #565 for lifting the HTTP/S validation. In case it's approved/merged, I think we don't need to update the docs like this anymore

Closing in favour of #565


Alternate upstream renaming implementation

Compare with #35.

jdaviz 3.7.1 is released, so we can move forward with #35 instead.


Add LogTarget::AppDir

This adds the AddDir option to the LogTarget enum, it will acts basically the same as the Folder target but chooses the appropriate directory based on tauri::api::path::app_dir.
This has the convenience that users don't need to interact with the unstable output of tauri::generate_context when configuring the plugin.

Actually I just realized I somehow merged some other stuff into this branch... Shall I just recreate this PR?

I saw the webview target, you can just put everything on this PR since we didn't release this plugin yet.


[fix][client] Fix possible npe

Motivation

NPE can occur in extreme cases.
For example: when thread A is executing here: https://github.com/apache/pulsar/blob/b6f0f91e099c47cd18cd901d5e7ebc7c4e5c0406/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ClientCnx.java#L1298
another thread has consumed all requestTimeoutQueue data.
Modifications
Add NPE check
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Codecov Report

Merging #18406 (41974b4) into master (b31c5a6) will decrease coverage by 10.38%.
The diff coverage is 4.54%.

@@              Coverage Diff              @@
##             master   #18406       +/-   ##
=============================================
- Coverage     46.98%   36.60%   -10.39%
+ Complexity    10343     1938     -8405
=============================================
  Files           692      208      -484
  Lines         67766    14385    -53381
  Branches       7259     1571     -5688
=============================================
- Hits          31842     5266    -26576
+ Misses        32344     8534    -23810
+ Partials       3580      585     -2995

Flag
Coverage Δ

unittests
36.60% <4.54%> (-10.39%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

.../java/org/apache/pulsar/client/impl/ClientCnx.java
30.07% <0.00%> (-0.09%)
:arrow_down:

...a/org/apache/pulsar/client/impl/TableViewImpl.java
0.00% <0.00%> (ø)

...ar/client/impl/conf/ProducerConfigurationData.java
84.70% <ø> (-0.18%)
:arrow_down:

...va/org/apache/pulsar/client/impl/ConsumerImpl.java
15.09% <12.50%> (+0.05%)
:arrow_up:

...va/org/apache/pulsar/broker/service/ServerCnx.java

...org/apache/bookkeeper/mledger/LedgerOffloader.java

...er/loadbalance/impl/PulsarResourceDescription.java

...ction/buffer/impl/TopicTransactionBufferState.java

.../org/apache/pulsar/broker/admin/v1/Properties.java

...pache/pulsar/broker/web/ResponseHandlerFilter.java

... and 479 more

But still it seems weird.
If this patch works, shall we recheck the request polled not fit isTimedOut? Otherwise, who is competing here?

I second @eolivelli that scheduleAtFixedRate should keep the submitted task executed individually. That is, before the current checkRequestTimeout returns, there's no new execution to checkRequestTimeout when be triggered.

/pulsarbot run-failure-checks

ping @eolivelli

@eolivelli Thanks for your input.
Merging...


Work around github actions checkout not creating a file for the remote HEAD

github actions/checkout@v2 does not git clone a repository, and as a result the remote HEAD ref does not exist.
This creates it pointing at the default branch discovered from the github API to allow devbox to discover the ref.

What actions/checkout does is:

create directory
git init
git remote add
git fetch
git checkout

This set of steps creates a different .git state from a plain git clone


Flannel: Pod unable to connect to itself via service IP

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create cluster with flannel CNI
Create a deployment using for example an Nginx image
Create a service of type clusterIP that maps to port 80 of the deployment
Exec into the pod that has been created by the deployment
Execute curl http:://<Service Cluster IP>

Result:
Curl command fails with connection refused or timeout
Other details that may be helpful:
The flannel template used by RKE is out of sync with the recommended upstream configuration and does not enable hairpin mode for the bridge interface.
Use cases for Pods connecting to their service IP:
Clustered applications like Mongo, Cassandra where pods must connect to their peers using the service IP.
Environment information
Rancher v<IP_ADDRESS>

https://github.com/rancher/rke/issues/1168

https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/#a-pod-cannot-reach-itself-via-service-ip
It says “If the effective hairpin mode is hairpin-veth, ensure the Kubelet has the permission to operate in /sys on node.”
I think RKE doesn’t give kubelet that permission. So we hit this issue.
A workaround is running for intf in /sys/devices/virtual/net/cni0/brif/*; do echo 1 > $intf/hairpin_mode; done on the node manually.

For flannel, there was no image update, but there was a template update. To verify template update, check kube-flannel-cfg config map (kube-system namespace) - it should have the following parameters set:
delegate": {
            "hairpinMode": true,
            "isDefaultGateway": true
          }

Tested with rancher server built from master-head (Jul 17)
Created a RKE cluster uisng flannel network mode.
hairpinMode is enabled as expected

kubectl get configmap kube-flannel-cfg -n kube-system -o json
{
"apiVersion": "v1",
"data": {
"cni-conf.json": "{\n  "name": "cbr0",\n  "plugins": [\n    {\n      "type": "flannel",\n      "delegate": {\n        "hairpinMode": true,\n        "isDefaultGateway": true\n      }\n    },\n    {\n      "type": "portmap",\n      "capabilities": {\n        "portMappings": true\n      }\n    }\n  ]\n}\n",
"net-conf.json": "{\n  "Network": "<IP_ADDRESS>/16",\n  "Backend": {\n    "Type": "vxlan",\n    "VNI": 1,\n    "Port": 8472\n  }\n}\n"
},
"delegate": {\n        "hairpinMode": true,\n        "isDefaultGateway": true\n      }\n    },\n

Create a deployment
Create a service of type clusterIP that maps to port 80 of the deployment
Exec into the pod that has been created by the deployment
Execute curl http:://<Service Cluster IP>
Able to reach itself successfully.

root@mytest1-7d8497cdb-pq52f:/# curl <IP_ADDRESS>/name.html
mytest1-7d8497cdb-pq52f
root@mytest1-7d8497cdb-pq52f:/#


Unable to download shape files larger than 1GB

curl -O https://healthsites.io/media/shapefiles/World.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
 50 2038M   50 1038M    0     0  2871k      0  0:12:06  0:06:10  0:05:56 2916k
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)

curl -O https://healthsites.io/media/shapefiles/World.zip
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
50 2038M   50 1038M    0     0  2871k      0  0:12:06  0:06:10  0:05:56 2916k
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)

it seems that:
proxy_max_temp_file_size 4096M;

fixes problem - please confirm.


Message is split in chunks of 2^14 bytes

It seems that Channel.unary returns a response whose body is split in chunks of approximately 2^14 bytes.
As a result, Stub.parse_unary_response can fail to parse a message, since it's seeing only the first 2^14 bytes of it.
Due to this, I'm seeing the following error:
** (MatchError) no match of right hand side value: "(very long string of a bit less than 2^14 bytes)"
             lib/protobuf/decoder.ex:163: Protobuf.Decoder.decode_type/3
             lib/protobuf/decoder.ex:30: Protobuf.Decoder.do_decode/4
    (elixir) lib/enum.ex:1229: Enum."-map/2-lists^map/1-0-"/2
             lib/grpc/stub.ex:157: GRPC.Stub.parse_unary_response/2

Changing parse_unary_response like this seems to fix the problem for me:
  defp parse_unary_response({_headers, data_list}, unmarshal) do
    data_list
    |> Enum.join("")
    |> GRPC.Message.from_data()
    |> unmarshal.()
  end

@arnaud-lb I think you are right. How about sending a PR to fix it? 😁

I'll try, but I promise nothing, given my current level in elixir.


Create a Sample Application on Cloud Foundry Using SAP Cloud SDK

Tutorial URL: https://developers.sap.com/tutorials/s4sdk-cloud-foundry-sample-application.html
Please specify the step you are referring to
I tried
mvn archetype:generate -DarchetypeGroupId=com.sap.cloud.sdk.archetypes -DarchetypeArtifactId=scp-cf-tomee -DarchetypeVersion=RELEASE
and do
mvn install
but the java.security.acl.Group was marked as deprecated and seems to be removed.

Hi burreo, I tried reproducing the issue on my machine but it went through smoothly, I didn't see any warnings.
Could you please run install with the -X flag and attach the relevant log output? Sorry for the late response.

Thank you for your feedback. We haven't heard from you in a while, so we are closing the issue.
If you still have questions, feel free to reopen the issue.


Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

tweak: Pulling objects is generally faster on most surfaces.
tweak: Crates and lockers are now lighter and can be dragged easier.
tweak: You can drag objects while in space. Not that Newton's laws still apply and you won't be getting anywhere.
tweak: Dragging objects while on a grid in 0 gravity now works.

cl: not that


Add recovery state

If device in recovery, device.State() will return adb.StateRecovery instead of adb.StateInvalid

Closed. Forgot to remove testing logs


shiba: use 'extract_dir'

https://github.com/rhysd/Shiba/issues/52
https://github.com/lukesampson/scoop-extras/pull/2217#issuecomment-498330926

Thx~