Enable CockroachDB in CI and update documentation

hi @kibertoad,
does that mean the new 'CockroachDB' dialect is ready to be used (or at least tested) by the community?
I see in latest change logs (0.95.12 at time of this writing) the following:

New dialect: CockroachDB #4742

But at the same time, I see in the installation instructions the below:

If you want to use CockroachDB or Redshift instance, you can use the pg driver.

So I'm wondering if the doc will get updated, and if I can already reference the new crdb dialect (or driver, a bit confused with the terminology here to be honest, between the new crdb dialect, and the pg driver..), and if so, how exactly/what exact string I need to use in the knex config to leverage that new crdb dialect?
thanks!

@Frank-D Both are correct. You should specify "cockroachdb" as a dialect, and have pg available as a dependency. crdb doesn't have a driver of its own. And yes, it is ready to be used.

Wow, lightning fast response @kibertoad !
Alright, so if we were to summarize super briefly the installation and configuration of such setup, would that be around those below lines?
Installation (as seen on your site here):
1- npm install knex --save
2- npm install pg --save
Configuration (similar to what can be seen on your side here under the "...PostgreSQL adapter to connect a non-standard database..." section, but this time with a small change to the client? Not sure if changing the client is what you meant when suggesting to plug in the new 'cockroachdb' dialect...in knex world, does such 'client' == 'dialect', or the 'client' is really the 'driver', and that should remain 'pg' here in this case, and plugging the crdb dialect should be done/configured differently?
Note: The database version can be added in knex configuration, when you use the PostgreSQL adapter to connect a non-standard database.

const knex = require('knex')({
  client: 'pg',  *** Replace with 'cockroachdb' instead? else, where should we configure this new 'cockroachdb' dialect?
  version: '7.2',  *** Is that version still needed, when using the 'cockroachdb' dialect/client? I believe it can now be dropped?
  connection: {
    host : '<IP_ADDRESS>',
    port : 3306,
    user : 'your_database_user',
    password : 'your_database_password',
    database : 'myapp_test'
  }
});

Sample Cockroachdb config:
  cockroachdb: {
    client: 'cockroachdb',
    connection: testConfig.cockroachdb || {
      adapter: 'cockroachdb',
      port: 26257,
      host: 'localhost',
      database: 'test',
      user: 'root',
      password: '',
    },
    pool,
    migrations,
    seeds,
  },

@Frank-D I ask you to take into account the given list

@kibertoad, thanks much appreciated. Any reason why the 'cockroachdb' client can't hide setting the adapter (which takes the same value 'cockroachdb') internally, rather than having to provide the adapter in the knex.connection config? Otherwise, much appreciated!
@intech, 100%, thanks. Just to be sure (since that page/list doesn't contain any explanation), are we saying that this is the list so far that has been identified in terms of known gaps between postgres and cockroachdb, that will need to be taken care over time in this new 'cockroachdb' knex dialect (..so items unchecked are not expected to work/be supported as of now)? ..and so, once an item of that list is checked, it means, a fix was provided, either as part of a given knex crdb dialect version (wondering how we'll know which item comes in which knex version..), or perhaps the fix may be done directly in crdb for some items...is that how we should read this list?)
thanks

@Frank-D It might actually be redundant, I'll need to check.

@Frank-D If you are using cockroach then I suppose because of its peculiarities. And they are not backward compatible with the pg dialect. It extend it with additional commands. Therefore, the transition from pg to crdb will not be any different, but if you are already using some of the cockroach features, then you should check against this list.
I will try to keep it up to date at all times and mark the versions in which it appears (thanks for the hint).

Thanks @intech, that's great.
And to one of your point, I am actually not using any of their crdb specific features (at least not yet), and I selected them not because of their specific features, but rather because of their hosting offerings (especially, their new crdb "serverless" offering, which seems to be great to start with, compared to many other db cloud hosting offerings I looked at..), or else, I would have probably stick with some very standard native postgres db and would have avoided those challenges! But cloud hosting/offering has become over the years almost as important as the product features themselves, if not, sometimes, more important, based on your scenarios etc).
And so, short to mid term at least, I'm not necessary planning on falling into any of those limitations, but who knows, fingers crossed! For time being, I'm just really happy that you guys have spent all this work to make such initial crdb support, that's really great news for the community, giving them more options! ✌


Pitchdeck - https://pitch.threadr.ai/

Need everyones feedback on the pitchdeck content please. After you have read the deck we should be evaluating it to make sure we have market fit, a unique value proposition and trying to understand and validate that our product fits into at least one of these categories:

Urgency - the problem our product addresses is immediate and pressing for our target customers
Underserved - the target market or customer segment feels that current solutions do not meet their needs
Unworkable - the issue or problem is so significant that it makes current processes or solutions ineffective. This can relate to situations where the problem our product solves is causing significant inefficiencies or obstacles for our customers.
Unavoidable - Is the problem tied to mandatory requirements or regulations that demand compliance, making a solution essential?

Startup Secrets

Please comment here with any feedback.
✨ https://pitch.threadr.ai is now available

I think our Example Queries are kind of weak and don't speak to the unique value prop that we have -- our ability to infer relationships, store them, and analyze them..

The pitch looks great!! We have covered all the points.
However, I thinks the slides are pretty verbose (giving a feel its AI generated). The slide content can be more point-based like slides 7, or point + small explanation like slide 9. What say? The present slide content would be more of what we speak during the pitch (in case we present), while the slide's actual content being reduced to only point + 1 liner.

Good advice, will try and condense it and add slide notes.

A slide after "Example Queries" could be more of a chatbot where we can show the queries asked to the bot, and the response by the bot. For example,
What were the top 3 conversations of utmost importance over the last week?

Search system was down for an hour in production impacting all the customers. The revenue impact is still uncertain.
2. We signed up with 3 new customers: ABC, DEF and XYZ.
3. One more...

Does Jason from Sales team know our Platform Engineer Mike?

There has been no direct communication between them, neither have they been part of the same thread. Hence, it is unlikely they know each other.

How many PagerDuty alerts fired over the last month along with their teamwise split?

There were 152 PagerDuty alerts in total that were fired.
Here is the split:
Platform team : 67
DevOps team: 29
CustomerSupport team: 10
ABC team: 46

I think we need to add a slide in here that covers our Agenda (first slide):

Team
Business Overview
Market Opportunity
Value Proposition
Go To Market Plan
Business Model
Financials

I think we need to add a slide in here that covers our Agenda (first slide:
Agenda

Team
Business Overview
Market Opportunity
Value Proposition
Go To Market Plan
Business Model
Financials

I'm going to also try and reshape/rework/remove/add slides to fit into this outline as well

Was just thinking abt a similar outline. Glad we already got it going.

going to close this out, the pitch-deck is created, we will probably keep iterating on it for a long time.


Census info does not display for certain states

Steps to reproduce:

Select Wyoming
Select all service areas
Select any provider dataset

@tetraptych How can I reproduce this? How do I select Wyoming providers?

Ah can I just upload any provider dataset? Lemme try now.

Ok, census info is all there except age. Is the age table missing Wyoming on that environment (presumably)? Is that data missing on the other environments too?

Age is missing for Colorado and others, could we add to all envs @philipdickinson ?

Just saw this after commenting on #371. I can add it now. CC @viviandien

With the USA-wide datasets, it seems like Georgia (and possibly others) are still missing age info.

@philipdickinson could you maybe have a shot at this?

Confirmed - my transformation script produces an empty file for GA. Will need to look at why now.

Crossposting from IM - added GA to all databases.

@philipdickinson do you have a PA / OH census tract on hand? I can start to look into where this information is being lost between the db and the frontend.

As an aside @tetraptych, I just wanted to check what state this was from (got it from my shell history) - how is there no reverse census tract geocoder?! Give<PHONE_NUMBER>0 a spin.

The first two digits correspond to the state FIPS code, which is roughly alphabetical. 40 is Oklahoma, 42 would be PA.

Looks like the data/ages/raw/ages-pa has the following row:
1400000US46013951400,46013951400,"Census Tract 9514, Brown County, South Dakota"

which does not appear to be in Pennsylvania.


Update and lightweighting of container base images

Discussed in https://github.com/cloudforet-io/community/discussions/115

Originally posted by jihyungSong February 13, 2023
Most Cloudforet's Core and Plugin container images are using python:3.8.
I suggest using python:3 instead of python:3.8 for image updates.
It is not just for the purpose of upgrading the python version, but for the purpose of updating the basic OS(debian) and libraries of the image. latest OS libraries can also resolve container image security vulnerabilities.
Along with this, if you use python:3-slim instead of regular python:3 , you can further lightweighting the image and reduce the size of the container image to less than half.

Thank you for your request.
It is merged here =>  https://github.com/cloudforet-io/plugin-grafana-mon-webhook/commit/a849958362d586e46253c82cd0611b7997757ed4

Closing because it is solved


You're not here at Tokyo Rubyists October

Hey,
So I'm leaving at the end of the month, and I was hoping to grab you for a chat at my last Tokyo Rubyists meetup this month!  But you didn't make it.    If not, that's cool.
Zach

@corps: I'd love to meet up; get in touch with me either via private message to my 0cjs account on Gitter or, failing that, the e-mail address on my GitHub profile page (but the latter won't get to me nearly as fast).


[Feature Request] Mac 128 keyboard support

First of all, let me just say that this is an awesome project!! I have been able to get my modern mechanical keyboard working on many old systems. Since there are many extra GPIO pins on the Pico, I was thinking it might be cool to be able to get this to work on the Mac 128 - Mac Plus that have those reversed 4 pin RJ-9 ports. Possible???
I will be covering this project on an upcoming episode of the Retro Hack Shack once I have done some more testing. Keep up the good work!

Cool thanks, I already knew your channel!
Please note: I've still one last major issue with mouse support left before I release version 1.0.
For the pre-ADB Mac support I found a similar adapter: http://www.synack.net/~bbraun/mackbd/
The hardware with clock/data looks identical, only the connector is different and it should be not too hard to implement this!
Main problem here is I don't have any pre-ADB Macs to test this with, so that makes it difficult again.
Maybe I could test with something like this: https://www.tinkerboy.xyz/product/tinkerboy-m0110-keyboard-to-usb-converter-for-the-apple-macintosh-128k-512k-plus-keyboard/

If you are in the SF Bay area, I can hook you up. 😀 Otherwise, I am happy
to do any testing you might need. I know it's not the same, but I am happy
to help if I can.
Thanks,
Aaron
On Tue, Mar 12, 2024, 10:43 PM No0ne @.***> wrote:

Cool thanks, I already knew your channel!
Please note: I've still one last major issue with mouse support left
before I release version 1.0.
For the pre-ADB Mac support I found a similar adapter:
http://www.synack.net/~bbraun/mackbd/
The hardware with clock/data looks identical, only the connector is
different and it should be not too hard to implement this!
Main problem here is I don't have any pre-ADB Macs to test this with, so
that makes it difficult again.
Maybe I could test with something like this:
https://www.tinkerboy.xyz/product/tinkerboy-m0110-keyboard-to-usb-converter-for-the-apple-macintosh-128k-512k-plus-keyboard/
—
Reply to this email directly, view it on GitHub
https://github.com/No0ne/ps2x2pico/issues/27#issuecomment-1993611567,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA7Q3NB3YZBYPDOGNZRV3LYX7ROTAVCNFSM6AAAAABETOHNGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJTGYYTCNJWG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks, that would be very nice but I'm in Austria, so not really nearby 😏.
I'll try to reimplement this: https://github.com/n055/ps22plus
Let you know if there is something new to test!

Great! If this works out, I would be happy to make a little daughter board
for this that includes a few level shifters to make it easier for people to
use.
Thanks,
Aaron Newcomb
Retro Hack Shack https://www.youtube.com/channel/UCN_u47_wJuhh249H9E8sjtw/
Benicia Makerspace http://beniciamakerspace.org
Linux for Makers https://amzn.to/2BwPjlj
TWiT Network https://twit.tv/people/aaron-newcomb
On Wed, Mar 13, 2024 at 12:28 AM No0ne @.***> wrote:

Thanks, that would be very nice but I'm in Austria, so not really nearby
😏.
I'll try to reimplement this: https://github.com/n055/ps22plus
Let you know if there is something new to test!
—
Reply to this email directly, view it on GitHub
https://github.com/No0ne/ps2x2pico/issues/27#issuecomment-1993722398,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA7Q3OWTJAVJTG6WILD65TYX75X7AVCNFSM6AAAAABETOHNGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJTG4ZDEMZZHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I've cobbled together a really quick&dirty test to see if I'm on the right path: the only keys working are A-Z, 0-9, enter, backspace, tab, space, -, =, [, ] and .
https://github.com/No0ne/ps2x2pico/raw/27-mac-128-keyboard-support/hid2mac.uf2
Please try it on a real Mac: connect HV1 to data and HV2 to clock on the Mac side.
LV1 and LV2 on the Pico side should already be GPIO11+12.
I will move this to a new repository since there will be no PS/2 code anymore.

Did you have time to try it out?

Perfect timing. Sorry it has taken so long, but when I went to find an
early Mac to test with all of the ones I have were having issues. So I was
actually just fixing up one of them and it's ready to go now. I will give
it a try and let you know how it goes.
Thanks,
Aaron
On Sat, Apr 6, 2024, 8:05 PM No0ne @.***> wrote:

Did you have time to try it out?
—
Reply to this email directly, view it on GitHub
https://github.com/No0ne/ps2x2pico/issues/27#issuecomment-2041289285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA7Q3M3XIFNWKYTQJ3ZMVDY4CZZNAVCNFSM6AAAAABETOHNGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGI4DSMRYGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

OK. Just got done making the adaptor. Everything is working perfectly. 😀
One watchout that I found is that there is a warning in the manuals not to
draw more than 200ma through the keyboard port on an early Mac. I tested
the current and it showed 41.5 mA with a basic USB keyboard, but an RGB LED
keyboard with backlit keys would probably be a problem.
Thanks,
Aaron Newcomb
Retro Hack Shack https://www.youtube.com/channel/UCN_u47_wJuhh249H9E8sjtw/
Benicia Makerspace http://beniciamakerspace.org
Linux for Makers https://amzn.to/2BwPjlj
TWiT Network https://twit.tv/people/aaron-newcomb
On Sat, Apr 6, 2024 at 11:38 PM Aaron Newcomb @.***> wrote:

Perfect timing. Sorry it has taken so long, but when I went to find an
early Mac to test with all of the ones I have were having issues. So I was
actually just fixing up one of them and it's ready to go now. I will give
it a try and let you know how it goes.
Thanks,
Aaron
On Sat, Apr 6, 2024, 8:05 PM No0ne @.***> wrote:

Did you have time to try it out?
—
Reply to this email directly, view it on GitHub
https://github.com/No0ne/ps2x2pico/issues/27#issuecomment-2041289285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACA7Q3M3XIFNWKYTQJ3ZMVDY4CZZNAVCNFSM6AAAAABETOHNGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBRGI4DSMRYGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Holding arrow keys in file selector can cause the highlighted item to disappear

go file editor in a big folder
hold down
highlighted item slowly moves up the screen when going down until it's no longer there.

actually this happens without holding

also huge folders lag every time u click up/down

It's a problem with the math calculation, will fix it in the next build

presumably fixed in v1.1.1


@clerk/upgrade does not seem to work via yarn

Preliminary Checks

[X] I have reviewed the documentation: https://clerk.com/docs
[X] I have searched for existing issues: https://github.com/clerk/javascript/issues
[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction
https://example.com/not_applicable
Publishable key
pk_not_applicable
Description
Steps to reproduce:

yarn dlx @clerk/upgrade

Expected behavior:
It should do whatever it's supposed to do
Actual behavior:
It errors
$ yarn dlx @clerk/upgrade
➤ YN0000: · Yarn 4.1.1
➤ YN0000: ┌ Resolution step
➤ YN0058: │ marked-terminal@https://github.com/jescalan/marked-terminal.git#commit=44f5ab42076e16937f56d645d3d7264675558ea1: Packing the package failed (exit code 1, logs can be found here: /tmp/xfs-303b25cc/pack.log)
➤ YN0000: └ Completed in 8s 790ms
➤ YN0000: · Failed with errors in 8s 810ms
$ cat /tmp/xfs-303b25cc/pack.log
Packing marked-terminal@https://github.com/jescalan/marked-terminal.git#commit=44f5ab42076e16937f56d645d3d7264675558ea1 from sources
Using npm for bootstrap. Reason: found npm's "package-lock.json" lockfile

Environment
System:
    OS: Linux 6.8 Ubuntu 24.04 LTS 24.04 LTS (Noble Numbat)
    CPU: (16) x64 AMD Ryzen 7 2700 Eight-Core Processor
    Memory: 18.82 GB / 31.29 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  npmPackages:
    @clerk/nextjs: ^5.0.5 => 5.0.5
    @headlessui/react: 1.7.19 => 1.7.19
    @heroicons/react: ^1.0.6 => 1.0.6
    @hookform/resolvers: ^3.3.4 => 3.3.4
    @mailchimp/mailchimp_transactional: 1.0.59 => 1.0.59
    @next/eslint-plugin-next: ^14.2.3 => 14.2.3
    @ngrok/ngrok: ^1.2.0 => 1.2.0
    @sentry/nextjs: ^7.110.1 => 7.110.1
    @tailwindcss/forms: ^0.5.7 => 0.5.7
    @tailwindcss/typography: ^0.5.12 => 0.5.12
    @testing-library/dom: ^9.3.4 => 9.3.4
    @testing-library/jest-dom: ^6.4.2 => 6.4.2
    @testing-library/react: ^14.3.1 => 14.3.1
    @testing-library/user-event: ^14.5.2 => 14.5.2
    @types/jest: ^29.5.12 => 29.5.12
    @types/luxon: ^3.4.2 => 3.4.2
    @types/mailchimp__mailchimp_transactional: ^1.0.9 => 1.0.9
    @types/node: ^18.19.31 => 18.19.31
    @types/node-fetch: ^2.6.11 => 2.6.11
    @types/pg: ^8.11.5 => 8.11.5
    @types/react: ^18.2.78 => 18.2.78
    autoprefixer: ^10.4.19 => 10.4.19
    axios: 0.21.4 => 0.21.4
    babel-jest: ^29.7.0 => 29.7.0
    concurrently: ^8.2.2 => 8.2.2
    dotenv: ^16.4.5 => 16.4.5
    eslint: ^8.57.0 => 8.57.0
    eslint-config: ^0.3.0 => 0.3.0
    eslint-config-next: ^14.2.3 => 14.2.3
    eslint-config-prettier: ^9.1.0 => 9.1.0
    eslint-plugin-jest-dom: ^5.2.0 => 5.2.0
    eslint-plugin-simple-import-sort: ^12.0.0 => 12.0.0
    eslint-plugin-testing-library: ^6.2.2 => 6.2.2
    husky: ^9.0.11 => 9.0.11
    jest: ^29.7.0 => 29.7.0
    jest-environment-jsdom: ^29.7.0 => 29.7.0
    jest-watch-select-projects: ^2.0.0 => 2.0.0
    jest-watch-typeahead: ^2.2.2 => 2.2.2
    jose: ^5.2.4 => 5.2.4
    jwt-decode: ^4.0.0 => 4.0.0
    knex: ^3.1.0 => 3.1.0
    lint-staged: ^15.2.2 => 15.2.2
    luxon: ^3.4.4 => 3.4.4
    msw: 1.0.1 => 1.0.1
    next: ^14.2.3 => 14.2.3
    node-fetch: ^2.6 => 2.7.0
    node-mocks-http: ^1.14.1 => 1.14.1
    npm-run-all: ^4.1.5 => 4.1.5
    pg: ^8.11.5 => 8.11.5
    plaid: ^23.0.0 => 23.0.0
    postcss: ^8.4.38 => 8.4.38
    postcss-import: ^16.1.0 => 16.1.0
    prettier: ^3.2.5 => 3.2.5
    prettier-plugin-tailwind-css: ^1.5.0 => 1.5.0
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    react-hook-form: ^7.51.3 => 7.51.3
    react-plaid-link: ^3.5.1 => 3.5.1
    react-tooltip: ^5.26.3 => 5.26.3
    swr: 2.2.5 => 2.2.5
    tailwindcss: ^3.4.3 => 3.4.3
    ts-brand: ^0.1.0 => 0.1.0
    ts-node: ^10.9.2 => 10.9.2
    tsconfig-paths: ^4.2.0 => 4.2.0
    typescript: ^5.4.5 => 5.4.5
    typescript-eslint: ^7.7.0 => 7.7.0
    yup: ^1.4.0 => 1.4.0

Hi, thanks for the issue!
I tried yarn dlx @clerk/upgrade on an example repo of mine and it works:
clerk-nextjs-app-quickstart on  main [⇣!?] via ⬢ v20.11.1 took 2.7s
➜ yarn dlx @clerk/upgrade
➤ YN0000: · Yarn 4.0.1
➤ YN0000: ┌ Resolution step
➤ YN0085: │ + @clerk/upgrade@npm:1.0.6, @alcalzone/ansi-tokenize@npm:0.1.3, @babel/code-frame@npm:7.24.2, and 230 more.
➤ YN0000: └ Completed in 5s 441ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ 233 packages were added to the project (+ 18.66 MiB).
➤ YN0000: └ Completed in 0s 345ms
➤ YN0000: ┌ Link step
➤ YN0000: └ Completed in 0s 553ms
➤ YN0000: · Done in 6s 367ms

 █▀▀ █   █▀▀ █▀█ █▄▀   █ █ █▀█ █▀▀ █▀█ ▄▀█ █▀▄ █▀▀
 █▄▄ █▄▄ ██▄ █▀▄ █ █   █▄█ █▀▀ █▄█ █▀▄ █▀█ █▄▀ ██▄

✓ File scan complete. See results below!

Navigation Instructions:
Navigate through items with ↑ and ↓ arrow keys. Expand the details of any item with space bar. ↓ key on the last item goes to the next page, ↑
on the first item goes to the previous page. To exit this interface, use "control + c".

[...]

Some questions for you:

Are you able to provide a repository where this always happens for you?
If not, can you provide the error logs you're getting?
Is this also happening with npx @clerk/upgrade?

If you have yarn installed you also have npm installed, so you can use npx @clerk/upgrade to unblock yourself (if it works). You don't necessarily have to use yarn 👍

I can't seem to make a reproduction in codespace, I ended up doing it manually anyhow, and I'll close this for now.


Isolating why Connect-PnPOnline fails for some accounts?

We've run into a scenario where Connect-PnPOnline fails for some accounts that are configured (as best we can tell) identically.  Using PnP version - SharePointPnPCoreOnline.3.23.2007
All these accounts succeed with -UseWebLogin and other variations of auth, but we're finding that the same call to pass creds will fail on some of the accounts.  All of them are setup the same in terms of AD enabled legacy and excluded from MFA.  It's not clear if this is a bug or there's some other difference.
For example making the same call with three identically configured accounts and passing creds:
Connect-PnPOnline -Url "https://mytenant.sharepoint.com" -Credentials $creds
Error<EMAIL_ADDRESS>:  The sign-in name or password does not match one in the Microsoft account system.
Error<EMAIL_ADDRESS>:  The sign-in name or password does not match one in the Microsoft account system.
Success<EMAIL_ADDRESS><EMAIL_ADDRESS>:  Microsoft.SharePoint.Client.IdcrlException: The sign-in name or password does not match one in the Microsoft account system.
at Microsoft.SharePoint.Client.Idcrl.IdcrlAuth.GetServiceToken(String securityXml, String serviceTarget, String servicePolicy)
...
Is there a recommended way to further isolate this (specific logs or tracing to show why it fails) or known issues that might cause the because?

Hello @breakpoint7
how are you?
Thanks for your feedback.
Even though the PnP documentation articles are on this repository, I need to kindly redirect you to open PnP cmdlets issues here, in that repository, a member of the PnP community will handle your request.
Thank you!

@get-itips  Thank you very much for the contribution and sharing this explanation. @breakpoint7 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


made compatible with latest oculus v 1.6.13

turns out the issues with latest oculus were due to misconfigured gradle files, this should fix it
do note that this mod now uses embeddium cause oculus doesnt like base rubidium.
didnt test for oculus 1.6.13a due to it being corrupt.
lemme know if theres any issues
Fixes #91

Will there be support for 1.6.15?

can you build this

Will there be support for 1.6.15?
I have supported 1.6.15, you can have a look at my warehouse

I have supported 1.6.15, you can have a look at my warehouse

I can confirm that the version of the compat that Ayou has in their github repo works with oculus 1.6.15 and embeddium 0.3.1. Thank you!


#update deploy to github package

As a developer, it is hard when finding an application to test with the Livekit server. When I use example, it takes many steps to join a room. With this application, developers can set up an application for local testing and development. Therefore, I suggest pushing the container image to the GitHub package or docker hub to pull quickly.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.trinhdaiphuc seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Adding idcs documentation

Adding IDCS Events Registration Documentation

@anil-gangwal @Apoorva2405 Please work on fixing the review comments.

@shikhartanwar @Apoorva2405
accommodated the changes, please review.

@shikhartanwar  We would like to merge this PR and not have this change show up on production just yet. Would that be possible? If that is the we will go ahead and merge this PR

@shikhartanwar We would like to merge this PR and not have this change show up on production just yet. Would that be possible? If that is the case we will go ahead and merge this PR

No that's not possible.


MB-3622 move details shipment mutation

Description
Makes it so we're using useMutation for our updating of the MTO Shipment statuses from the Move Details page on the TOO app.
Setup
Add any steps or code to run in this section to help others prepare to run your code:
make db_dev_e2e_populate

Code Review Verification Steps

[ ] If the change is risky, it has been tested in experimental before merging.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
Any new migrations/schema changes:

[ ] Follow our guidelines for zero-downtime deploys (see Zero-Downtime Deploys)
[ ] Have been communicated to #g-database
[ ] Secure migrations have been tested following the instructions in our docs

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-3622

  Generated by :no_entry_sign: dangerJS against 42c1561eedc654128b97460e6ebe1ad44619f9d4

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-3622

  Generated by :no_entry_sign: dangerJS against 42c1561eedc654128b97460e6ebe1ad44619f9d4


Update set-up-communications-credits-for-your-organization.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/4932
Changed wording

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@CarolynRowe PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Remove version: Microsoft.Edge version 114.0.1823.43

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

URL: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/938cc6b4-2ed8-4599-89ae-7d5725372f51/MicrosoftEdgeEnterpriseX86.msi
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 912)


Fix ElmScope to consider format string when creating scope message.

@suhasj @rynowak @loudej
Related(but not dependent) PR: https://github.com/aspnet/Logging/pull/159

Hi @kichalla, I'm your friendly neighborhood Microsoft Open Technologies, Inc. Pull Request Bot (You can call me MSOTBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Kiran Challa). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla2.msopentech.com.

TTYL, MSOTBOT;

/cc: @Eilon

Closing this PR as these changes are no longer required due to following changes in logging recently:
https://github.com/aspnet/Logging/commit/d2ff516e8d01b867abf04ed7c41d58cb35f72a8a


Discussion: A race-free version of the Take() operator

I would like to discuss the semantics of Take(): Currently this operator is implemented completely without any form of synchronization, e.g. see https://github.com/dotnet/reactive/blob/d8dbf12254c0916ee4cdc5f0f3ddd312f4fefa93/Rx.NET/Source/src/System.Reactive/Linq/Observable/Take.cs#L54-L64
This leads to severe problems when sources generate overlapping OnNext() calls, E.g. here a minimal repro that gets stuck most of the time after less than 100 repeat-iterations:
class Program
{
    static async Task Main(string[] args)
    {
        async Task Generate(int i, IObserver<int> o)
        {
            for (; ; )
            {
                o.OnNext(i);
                await Task.Yield();
            }
        }

        var s = new Subject<int>();

        // spawn to background generators...
        var tasks = Enumerable.Range(0, 2).Select(x => Generate(x, s)).ToArray();

        int i = 0;
        s.Take(1).ObserveOn(TaskPoolScheduler.Default).Repeat().Subscribe(x =>
        {
            i += 1;
            Console.WriteLine(i);
        });

        await Task.WhenAll(tasks);
    }
}

Of course I understand that this can be quickly fixed by inserting a Synchronize(gate) before Take(1)... I am opening this issue because I spent a whole week debugging a similar race-condition in production code which only triggered after a long time and the last thing I had on my list for potential failures was  the RX Take() operator. I think with minimal code changes like e.g. Interlocked.Decrement() this race condition could be addressed even without introducing any locking.
Maybe @bartdesmet or somebody from the core team could take a look (believe me - I had a hard time debugging this).

The error is in your code because Subject.OnNext  (or more generally any IObserver method) shouldn't be called concurrently from multiple threads.
There is a synchronization wrapper somewhere in Rx that you can use to wrap the Subject's IObserver side.

@akarnokd Yes, it is correct that the subject was also in the real world example called from multiple threads. But since these errors are extremely hard to debug I would recommend from a dev perspective that either the wrong use of subjects is detected/synchronized or that operators like Take are slightly modified to become more robust. Right now the "concurrency contract" is not strictly enforced by Rx and I can easily shoot myself in the foot - something I have never experienced with Tasks for example.

@akarnokd thanks for pointing out that subject.Synchronize() exists ... probably I should use that throughout  my code-base wherever I use subjects.

It interesting that no overload of Subject.Synchronize() exists to allow passing a custom synchronization object (gate), the subject instance is always used: https://github.com/dotnet/reactive/blob/e483d14c0c090ae739626af547c72a0a30c23797/Rx.NET/Source/src/System.Reactive/Subjects/Subject.Extensions.cs#L77

The unprotected non-thread-safe behavior of naked Subject<> is clearly documented: Using Subjects. Probably these design decisions have been made long ago and it is now way too late to discuss it.

Yes, this goes back all the way to the start of Rx, where we initially had subjects with implicit synchronization. However, these go against the design philosophy in .NET (e.g. ArrayList and List<T> also don't synchronize by default), so you have to opt in to synchronization.
Moreover, subjects are also used in operators such as Publish where the (required) sequential (non-concurrent) nature of the upstream producer is the safety property that should "flow" through the internal subject, so it doesn't need to do any synchronization by itself (it just adds cost that cannot be taken away, while an opt-in to synchronization is just that: an opt-in).
Long story short, in Rx 1.0 betas, we had Subject<T> et al. do synchronization. In a subsequent Rx 1.0 beta, we renamed these to SafeSubject<T> et al. while also introducing non-synchronizing variants that became Subject<T> as we know them today. By the time we shipped Rx 1.0, we deleted SafeSubject<T> et al. in favor of a compositional approach with Synchronize operators.

One more thing that was part of the design decision around this is that given that a Subject<T> is an IObserver<T>, it should obey by the rules that conform to the message grammar for observers (no concurrent calls). We merely provide Synchronize methods to let us deal with conformance if the upstream caller can't guarantee it (and such uses of Synchronize should only occur on the "edge" of Rx, where it interacts with the outside world).

@bartdesmet Thanks a lot for taking the time to address my question. After re-reading parts of the documentation it became clear to me that I just had forgotten/ignored the rules. In my real use case the OnNext() call on the subject was triggered indirectly by a member function that was called potentially from concurrently running async-methods... I have many custom operators that are created with Observable.Create() in which I everywhere use synchronization objects when async/scheduled background tasks are involved. Only for the subjects I had forgotten the rule and interestingly this was in most places no problem, e.g. everywhere I used Observable.Merge() since Merge synchronizes internally.
I have equipped some of my simple subjects with Subject.Synchronize() ... hoping that this will not introduce new deadlocks (btw I probably will create a custom version of Synchronize which allows me to hand in a specific synchronization object instead the subject instance itself).


Remove description about ‘tsd’ from contributing guide and package.json

What problem does this feature solve?
It's an additional issue about  #1106
Since we have removed 'tsd', I think we should delete 'tsd' info in contributing.md and package.json
What does the proposed API look like?
:>

https://cs.github.com/vuejs/core/blob/ec795bfc517266387bb21729a0b0cb4ad8256eef/.github/contributing.md#L270
https://cs.github.com/vuejs/core/blob/ec795bfc517266387bb21729a0b0cb4ad8256eef/package.json#L34


Speed up creating RealmSwift.Realm instances

Nothing particularly exciting, but while checking why the relevant perf test was failing I noticed it was spending a lot of time on unnecessary things. This makes both Realm() and self.testRealmPath() (in our tests) take about a third less time, and switches the testRealmCreationCached test over to testing what is hopefully a more realistic scenario.

👍

👍


🤖 robot

[x] sweet looking robot
[x] rigged mesh is interchangeable with human forms
[x] keyframes for aiming all the way down, and all the way up
[x] animations for standing, walking, running
[ ] animation for blinking eye display

done


Only enable vulkan's extension when it's either supported or required

Previously, it was checking for availability before enabling them, but now it fails on some hardwares.
Could you bring back the checks or allow developers to explicity specify them programmatically?
https://github.com/NVIDIAGameWorks/NRI/blob/1d52b40bbf46d895457eecce29b1f20977f4d244/Source/VK/DeviceVK.cpp#L367-L376

Thanks. I'm fixing this too right now. Which ext didn't initialized?
VK_KHR_SWAPCHAIN_EXTENSION_NAME - I assume it's always available (bad assumption, I know)
VK_KHR_SYNCHRONIZATION_2_EXTENSION_NAME - mandatory, fallback to classic method is possible, but undesired
VK_KHR_DEFERRED_HOST_OPERATIONS_EXTENSION_NAME - ?
VK_KHR_SHADER_NON_SEMANTIC_INFO_EXTENSION_NAME - ?

Will look like this:
    // Mandatory
    desiredExts.push_back(VK_KHR_SYNCHRONIZATION_2_EXTENSION_NAME);

    if (IsExtensionSupported(VK_KHR_SWAPCHAIN_EXTENSION_NAME, supportedExts)) // TODO: move to supportedFeatures?
        desiredExts.push_back(VK_KHR_SWAPCHAIN_EXTENSION_NAME);

#ifdef __APPLE__
    if (IsExtensionSupported(VK_KHR_PORTABILITY_SUBSET_EXTENSION_NAME, supportedExts))
        desiredExts.push_back(VK_KHR_PORTABILITY_SUBSET_EXTENSION_NAME);

    if (IsExtensionSupported(VK_KHR_DYNAMIC_RENDERING_EXTENSION_NAME, supportedExts))
        desiredExts.push_back(VK_KHR_DYNAMIC_RENDERING_EXTENSION_NAME);
#endif

    // Optional
    if (IsExtensionSupported(VK_KHR_DEFERRED_HOST_OPERATIONS_EXTENSION_NAME, supportedExts))
        desiredExts.push_back(VK_KHR_DEFERRED_HOST_OPERATIONS_EXTENSION_NAME);

    if (IsExtensionSupported(VK_KHR_SHADER_NON_SEMANTIC_INFO_EXTENSION_NAME, supportedExts))
        desiredExts.push_back(VK_KHR_SHADER_NON_SEMANTIC_INFO_EXTENSION_NAME); // at least for "printf"

Fixed. Feel free to reopen if it doesn't work for you.


Consider removing background settings

backgroundColor it's optional by default, so if you remove this line nothing will change.

@NSCopying open var backgroundColor: UIColor?

Hey,
fixed this in v2.4.3, thank you for the suggestion.

Hey,
fixed this in v2.4.3, thank you for the suggestion.


Remove deprecated widget names

Things like ButtonWidget, IntTextWidget, etc... were deprecated in 3.0, is 4.0 too soon to remove them?  @minrk @jasongrout @SylvainCorlay

:+1:

I'm all for removing them

Actually, on second thought, we might as well make them part of the directory deprecation.  When that goes away, remove them

A corollary of my comment would be to not support the deprecated widget names from the ipython_widgets namespace, but only from the IPython.html.widgets namespace.

That may be tricky, given how the shims work, but a good idea in principle.

Can we just change the shim so instead of importing ipython_widgets, it imports, say, ipython_widgets.deprecated_names or something?

Is it worth touching the shims to remove deprecated classes?

I would say that a deprecation period of several months is way too short (3.0->4.0 timeframe).  At least a year is better, in my opinion, especially in this case where it is easy to support the old names in the old location.

@jasongrout that's not how the widgets have behaved yet, though. If anything, the widgets are still in '0.x' pre-alpha territory.

@minrk: We did put a deprecation warning in, which showed some sensitivity to people using the old names.  And we support people using old locations (IPython.html.widgets) for the 4.0 transition.  So we are already doing a minimal amount to support 'legacy' users of widgets.

But the status quo is to just leave the deprecated names in the current codebase (in the new location) for a bit longer.  I'm fine with that too.


Weight initialization might be superfluous

It appears that the way weight_norm works in Pytorch makes this line in TCN/tcn.py superfluous, because this line registers a forward prehook that overwrites module.weight every forward pass. (FYI)

Yes, indeed, L34 is not effective here. Thanks for pointing this out :-)


HuggingFacePipeline does not use chat template

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Hugging Face pipeline now has support for chat templates. This calls the apply_chat_template() of the tokenizer. This is a super useful feature which formats the input correctly according to the model. To apply the template one needs to pass a messages list to the pipeline as input (and not a prompt text).
Langchain's HuggingFacePipeline class is written in a way that only prompt text is passed to the pipeline. We can see this in the HuggingFacePipeline._generate method. As a result the prompt is constructed using Langchain's default template which is not the same as what the model works best with.
Let's build an example.
import torch
from langchain_core.prompts import ChatPromptTemplate
from langchain_core.output_parsers import StrOutputParser
from langchain_community.llms.huggingface_pipeline import HuggingFacePipeline

def test_agnostic_prompt(llm):
    prompt = ChatPromptTemplate.from_messages(
        [
            ("human", "When was Abraham Lincoln born?"),
            ("ai", "Abraham Lincoln was born on February 12, 1809."),
            ("human", "How old was he when he died?"),
            ("ai", "Abraham Lincoln died on April 15, 1865, at the age of 56."),
            ("human", "{question}"),
        ]
    )

    output_parser = StrOutputParser()

    chain = prompt | llm | output_parser

    reply = chain.invoke({"question": "Where did he die?"})

    print(reply)

hf_llm = HuggingFacePipeline.from_model_id(
        model_id="TinyLlama/TinyLlama-1.1B-Chat-v1.0",
        task="text-generation",
        pipeline_kwargs={"max_new_tokens": 128})

test_agnostic_prompt(hf_llm)

This sends the following prompt.
Human: When was Abraham Lincoln born?
AI: Abraham Lincoln was born on February 12, 1809.
Human: How old was he when he died?
AI: Abraham Lincoln died on April 15, 1865, at the age of 56.
Human: Where did he die?

The correct prompt, if chat template was applied, would be:
<|user|>
When was Abraham Lincoln born?</s>
<|assistant|>
Abraham Lincoln was born on February 12, 1809.</s>
<|user|>
How old was he when he died?</s>
<|assistant|>
Abraham Lincoln died on April 15, 1865, at the age of 56.</s>
<|user|>
Where did he die?</s>
<|assistant|>

Error Message and Stack Trace (if applicable)
No response
Description
The HuggingFacePipeline class should what is necessary to convert the ChatPromptTemplate to a messages list and then pass it to the pipeline. This will cause the pipeline to use apply_chat_template() of the tokenizer to correctly format the prompt.
System Info
System Information

OS:  Linux
OS Version:  #1 SMP Sat Feb 24 09:50:35 UTC 2024
Python Version:  3.10.13 | packaged by conda-forge | (main, Dec 23 2023, 15:36:39) [GCC 12.3.0]

Package Information

langchain_core: 0.1.38
langchain: 0.1.14
langchain_community: 0.0.31
langsmith: 0.1.24
langchain_openai: 0.1.1
langchain_text_splitters: 0.0.1

Packages not installed (Not Necessarily a Problem)
The following packages were not found:

langgraph
langserve

Let me see

any workaround available?

A workaround is using HuggingFacePipeline via ChatHuggingFace. This is actually somewhat documented:

Instantiate the ChatHuggingFace to apply chat templates
https://python.langchain.com/v0.2/docs/integrations/chat/huggingface/#2-instantiate-the-chathuggingface-to-apply-chat-templates

Note that until a release of langchain-huggingface beyond 0.0.3 is made, you need to apply the following commit manually because of #22804:
https://github.com/langchain-ai/langchain/commit/4796b7eb15b4c3a352c950f56a30659f0379f6e2

A workaround is using HuggingFacePipeline via ChatHuggingFace. This is actually somewhat documented:

Instantiate the ChatHuggingFace to apply chat templates
https://python.langchain.com/v0.2/docs/integrations/chat/huggingface/#2-instantiate-the-chathuggingface-to-apply-chat-templates

Note that until a release of langchain-huggingface beyond 0.0.3 is made, you need to apply the following commit manually because of #22804: 4796b7e

Hello, do you have any examples of code that uses both HuggingFacePipeline and ChatHuggingFace? My attempts to use both keeps resulting in errors.

I am facing the same problem with quantized variants of Meta Llama 3 8B-Instruct

A workaround is using HuggingFacePipeline via ChatHuggingFace. This is actually somewhat documented:

Instantiate the ChatHuggingFace to apply chat templates
https://python.langchain.com/v0.2/docs/integrations/chat/huggingface/#2-instantiate-the-chathuggingface-to-apply-chat-templates

Note that until a release of langchain-huggingface beyond 0.0.3 is made, you need to apply the following commit manually because of #22804: 4796b7e

Can you please specify?
I am learning Langchain and I have had to just use pipeline directory instead of the HuggingFacePipeLine or ChatHuggingFace abstractions. Still trying to figure out to intregrate this with the rest on Langchain.

I believe I fixed the issue! I detailed pull request will be submitted tomorrow! Everything should work through ChatHuggingFace in my fork

my solution
#!/usr/bin/python3

from typing import Any, Union
from collections.abc import Sequence
from transformers import AutoTokenizer
from langchain_core.prompts import ChatPromptTemplate, MessagesPlaceholder
from langchain_core.messages import HumanMessage, AIMessage, SystemMessage
from langchain_core.prompt_values import ChatPromptValue, PromptValue

# NOTE: langchain-core >= 0.3.15

class HFChatPromptValue(ChatPromptValue):
  tokenizer: Any = None
  def to_string(self) -> str:
    hf_messages = []
    for m in self.messages:
      if isinstance(m, HumanMessage):
        role = 'user'
      elif isinstance(m, AIMessage):
        role = 'assistant'
      elif isinstance(m, SystemMessage):
        role = 'system'
      else:
        raise Exception(f'Got unsupported message type: {m}')
      hf_messages.append({'role': role, 'content': m.content})
    return self.tokenizer.apply_chat_template(hf_messages, tokenize = False, add_generation_prompt = True)

class HFChatPromptTemplate(ChatPromptTemplate):
  tokenizer: Any = None
  def format_prompt(self, **kwargs: Any) -> PromptValue:
    messages = self.format_messages(**kwargs)
    return HFChatPromptValue(messages = messages, tokenizer = self.tokenizer)
  async def aformat_prompt(self, **kwargs: Any) -> PromptValue:
    messages = await self.format_messages(**kwargs)
    return HFChatPromptValue(messages = messages, tokenizer = self.tokenizer)

if __name__ == "__main__":
  messages = [
    ('system', "you are a helpful AI bot. Your name is {name}"),
    MessagesPlaceholder('chat_history'),
    ('human', '{user_input}')
  ]
  tokenizer = AutoTokenizer.from_pretrained('Qwen/Qwen2.5-7B-Instruct')
  prompt = HFChatPromptTemplate(messages, tokenizer = tokenizer)
  txt = prompt.format(**{'user_input': 'what is your name', 'name': 'robot test', 'chat_history': [HumanMessage(content = 'your name is awesome!'), AIMessage(content = 'Thanks!')]})
  print(txt)


SHA224 or SHA256 for PolicyID/CurrencySymbol?

Area
[x] Plutus Foundation Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
[] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
[] Marlowe Related to Marlowe
[] Other Any other topic (Playgrounds, etc.)
Summary
In Plutus, CurrencySymbol is a SHA256 digest, however cardano-cli transaction policyid yields a SHA224 digest. Why there is this difference? Which hashing algorithm will be the final one?
Versions
cardano-node: alonzo-purple-1.0.1
plutus: 826c2514a40e962c2e4d56ce912803a434cc28fe

hi @longngn looks like you just missed the changes by a few commits from https://github.com/input-output-hk/plutus/pull/3559 in your plutus version which should make this consistent with your version of cardano-cli

hi @longngn looks like you just missed the changes by a few commits from #3559 in your plutus version which should make this consistent with your version of cardano-cli

I used the Plutus version from the cabal.project file of cardano-node at revision alonzo-purple-1.0.1 so I guess that Plutus version was outdated.
I'll close this issue now. Thank you

This was actually still an issue. It's fixed by https://github.com/input-output-hk/plutus/pull/3902.


Hop通过什么来定时调度任务

许多人会使用 cron 或其他一些调度程序，例如 AWS Eventbridge。

许多人会使用 cron 或其他一些调度程序，例如 AWS Eventbridge。

我希望在任务调度方面hop可以有自己的任务调度平台，而不是使用其他别的项目，例如CKettle那样的集成调度平台，hotput任务调度就非常不错，不用再去找其他的调度平台。希望大佬们考虑一下

许多人会使用 cron 或其他一些调度程序，例如 AWS Eventbridge。

【【国产化Kettle】CKettle调度与监控系列 - 02Hotpot使用-哔哩哔哩】 https://b23.tv/aQ5r3mm  可以看下我觉得这种方式非常不错，如果Hop能集成这样的调度也是非常不错的

We as a project have decided that we would not focus on scheduling, there are so many different ways all with their pros and cons that it would be too much work and it would all depend on your architecture

We as a project have decided that we would not focus on scheduling, there are so many different ways all with their pros and cons that it would be too much work and it would all depend on your architecture

调度不重要吗？？


Query on lucene index slower after rebuilding indexes (2.1rc2 and 2.1rc3)

After rebuilding the lucene index in versions 2.1rc2 or 2.1rc3, the query on this index gets about 3 times slower. Means if query time is 1s, duration is 3s after the 1st rebuild and 9s after the 2nd rebuild and so on.

hi @quantussoftware  can you retry with 2.1.2 ?


Small additional refactoring + VS Code features

I've used prettier and adding a de-DE.json interaction model. Also, I've added a basic VS Code launch.json, so everybody can test it if SDKs installed on VS Code as well.

Hi @omgitsjan , thank you for the PR! 🙌 DE addition is really appreciated!
I will take some time later to review this, probably approve (first look is good!)
Cheers!


Consolidate code

Update make_eb_box() to use amrex::BoxIF. This allows specifying internal or external flow.
Remove incflo::set_velocity_bc functions in favor of using PhysBCFunct, which is needed to set the inflow bcs during FillPatch. Now we only need one function to set the inflow bc.
Rename file to better reflect contents which includes setting density and tracer EB bcs.  Renamed: incflo_set_velocity_bcs.cpp -> incflo_set_bcs.cpp

@asalmgren this passes the regression tests


XcodeTaskTest remove incremental inputs + testing

XcodeTask changes:

Remove unused IncrementalInputs
workingDir => setWorkingDir for convention on testing

XcodeTaskTest changes:

Fairly complex testing of command line and Podfile / podspec outputs
testXcodeConfig_Basic
testXcodeConfig_NeedsPodInit
testWriteUpdatedPodFileIfNeeded_NotNeeded

MockProjectExec:

Added workingDir verification step
Avoid string interpolation which throws exception for closure arg

@advayDev1, @confile - PTAL. Main things are removing the unused incremental inputs on the XcodeTask and thorough testing of what it's doing.

LGTM

@brunobowden - i thought we were adding a warning to open the .xcworkspace?

I'll do a separate PR for the warning.


docker: 19.03.5 -> 19.03.6

https://github.com/docker/docker-ce/releases/tag/v19.03.6
https://github.com/docker/docker-ce/tree/v19.03.6/components/engine/hack/dockerfile/install/

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg  test docker

nixpkgs-review passed ok. In addition following tests passed ok:

docker.nix
docker-containers.nix


Save button

I'm submitting a feature request
Description
_A feature: Can we have a save button on the editor by default or is there a way to add custom buttons?
Version Information
ngx-editor: 3.2.1
angular: 4.4.6

save what? and Can you explain the motivation of this feature?

To save content written into the editor. I'd like the save button to be on the toolbar. The motivation for this is for user initiated saving. Or are there ways for me to trigger saving without having to put a save button below the editor?

Right Now. There is no such option to add custom button to the toolbar. Instead. There is a proposal I made to another feature. I think that may be useful in your case

Since all components are capable of working individually. Alternatively, What I can do is I can expose the API's for toolbar and Message component. You can disable the default toolbar and design your own and then you can interact with the Editor.

Discussion here #58

Yeah that would be great.

So closing this issue now. Follow the above thread for details


Add ping-tester functionality

create ping tester functionality using foxglove/electron-socket and display ping on the component

Need contribs?


Merge darwin/libdispatch-1121 to master

Merge tag darwin/libdispatch-1121 on darwin/trunk.
This includes the latest Apple source drop libdispatch-1121 (up from libdispatch-913.1.4 in #447), on top of darwin/darwin-012.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@compnerd would you mind test building this branch to verify that it builds successfully on Windows?

@swift-ci please test

@ktopley-apple - nope, no problem, I'll do that (worst case might be tomorrow or so)

@ktopley-apple - nope, no problem, I'll do that (worst case might be tomorrow or so)

Thanks. Monday would be fine. Enjoy your weekend ;-)

ooh boy, this definitely does not yield a happy time, the build breaks on windows ... https://paste.ee/p/Lq6eN ... going to have to take a look at the LIST_ENTRY and _dispatch_uptime stuff.

_dispatch_uptime is broken because it's guarded with TARGET_OS_WIN32 which isn't actually defined anywhere. The correct way to check for Windows is with defined(_WIN32).
I should point out too that the use of QueryPerformanceCounter() is really broken here. The timestamp it returns is (roughly) in units of the processor's TSC frequency, so QueryPerformanceFrequency() has to be used in order to convert it into nanoseconds.
Also, QueryPerformanceCounter() includes time spent during suspend, and the comment above the function states that this is undesirable. The closest Windows equivalent to Linux's CLOCK_MONOTONIC is QueryUnbiasedInterruptTimePrecise(), however, using that is slightly annoying because you have to GetProcAddress() it from KernelBase.dll. (It's a documented interface, but Microsoft doesn't include it in any import libraries for whatever reason.) QueryUnbiasedInterruptTime() is a simpler alternative which master is currently using, but the value it returns is only updated at the system interrupt frequency.
If we can switch the QueryPerformanceCounter() call to QueryUnbiasedInterruptTime() for now to avoid a regression then I don't mind submitting a follow-up patch to improve upon it.

Okay, LIST_ENTRY is just something we need to add to generic_sys_queue.h as the usage is introduced here.  Ignoring the issue with QueryPerformanceCounter, changing to defined(_WIN32) is enough to get it building, and fixes for that can be done in a separate change.  That uncovers more issues, this time on aliasing - this might be the thing that @MadCoder and @jrose-apple were talking about a little while ago with using zero sized arrays to alias.
S:\swift-corelibs-libdispatch\src/queue_internal.h(1050,1):  error: static_assert failed due to requirement '__builtin_offsetof(struct dispatch_continuation_s, do_next) == __builtin_offsetof(struct dispatch_object_s, do_next)' "dispatch_continuation_s::do_next and dispatch_object_s::do_next should alias"
dispatch_assert_aliases(dispatch_continuation_s, dispatch_object_s, do_next);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
S:\swift-corelibs-libdispatch\src/internal.h(543,3):  note: expanded from macro 'dispatch_assert_aliases'
                dispatch_static_assert(offsetof(struct t1,f) == offsetof(struct t2,f), \
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
S:\swift-corelibs-libdispatch\src/internal.h(540,3):  note: expanded from macro 'dispatch_static_assert'
                _dispatch_static_assert(e, ##__VA_ARGS__, #e)
                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
S:\swift-corelibs-libdispatch\src/internal.h(535,44):  note: expanded from macro '_dispatch_static_assert'
#define _dispatch_static_assert(e, s, ...) _Static_assert(e, s)
                                           ^              ~
1 error generated.

Okay, seems that the src\queue.c changes need alteration too (due to the use of pthread_attr_*` which is not available on Windows.

https://github.com/apple/swift-corelibs-libdispatch/pull/449/commits/204c38a4ecc0906c4570b07c2eb1784dfab005bb has most of the hacks that I needed to mostly build ... the aliasing issue I think is something that needs a careful eye, and the src\queue.c changes need to be accounted for.  There are a few other warnings too.

@compnerd and @adierking - thanks for your comments and patches. I will update my local copy of the branch starting later today. Meanwhile I just pushed some changes that should result in the Linux build passing its tests.

@swift-ci please test

@ktopley-apple - if you could reply to the a couple of the unresolved comments I had, I might be able to update the patch to get those handled as well.

@ktopley-apple - if you could reply to the a couple of the unresolved comments I had, I might be able to update the patch to get those handled as well.

I replied to three open questions. Please let me know if I missed anything :-)

@ktopley-apple - okay, at least the aliasing issue is due to the use of __LP64__ which doesn't work for LLP64 (aka Win64).

@ktopley-apple - https://github.com/apple/swift-corelibs-libdispatch/pull/450
The top most commit there (bd2565e201769fd02aaae9060fcb0a00f052952e) is sufficient to make windows x64 build.  A test "hello world" program works with Swift with that.

@swift-ci please test

@ktopley-apple - #450
The top most commit there (33aaf78) is sufficient to make windows x64 build. A test "hello world" program works with Swift with that.

Thanks. I will be continuing this merge this week.

@ktopley-apple - #450
The top most commit there (33aaf78) is sufficient to make windows x64 build. A test "hello world" program works with Swift with that.

Looking at your 1121 PR, I see the topmost commit is 194f7ac, but you reference 33aaf78 here. What is the relationship between these two and which one should I take?

@ktopley-apple - #450
The top most commit there (33aaf78) is sufficient to make windows x64 build. A test "hello world" program works with Swift with that.

Thanks. I will be continuing this merge this week.

@compnerd Is the correct commit now 194f7ac?

@ktopley-apple - yeah, for 1121's build thats the patch that gets it to build; once that is in with 1121, I can bring over the cleaned up work that I did on the current master.

@swift-ci please test

@swift-ci please test

@ktopley-apple we are seeing this failure on 18.04, not sure if this is released to this PR.
01:05:35.076 FAILED: src/CMakeFiles/dispatch.dir/init.c.o
01:05:35.076 /usr/bin/clang -DDISPATCH_USE_DTRACE=0 -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -Ddispatch_EXPORTS -isystem /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/swift-corelibs-libdispatch/src/BlocksRuntime -I. 	Program arguments: /usr/lib/llvm-6.0/bin/clang -cc1 -triple x86_64-pc-linux-gnu -emit-obj -disable-free -disable-llvm-verifier -discard-value-names -main-file-name init.c -mrelocation-model pic -pic-level 2 -mthread-model posix -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -momit-leaf-frame-pointer -ffunction-sections -fdata-sections -coverage-notes-file /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/buildbot_incremental/swift-linux-x86_64/libdispatch-prefix/src/libdispatch-build/src/CMakeFiles/dispatch.dir/init.c.gcno -resource-dir /usr/lib/llvm-6.0/lib/clang/6.0.0 -dependency-file src/CMakeFiles/dispatch.dir/init.c.o.d -sys-header-deps -MT src/CMakeFiles/dispatch.dir/init.c.o -isystem /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/swift-corelibs-libdispatch/src/BlocksRuntime -isystem /usr/include/bsd -D DISPATCH_USE_DTRACE=0 -D HAVE_CONFIG_H -D _GNU_SOURCE=1 -D dispatch_EXPORTS -I . -I /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/swift-corelibs-libdispatch -I /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/swift-corelibs-libdispatch/src -I src -I /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/swift-corelibs-libdispatch/private -D NDEBUG -D LIBBSD_OVERLAY -internal-isystem /usr/local/include -internal-isystem /usr/lib/llvm-6.0/lib/clang/6.0.0/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -O3 -Wno-unknown-warning-option -Werror=unguarded-availability-new -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wmissing-field-initializers -Wimplicit-fallthrough -Wcovered-switch-default -Wdelete-non-virtual-dtor -Wstring-conversion -Werror -Wall -Wextra -Warray-bounds-pointer-arithmetic -Wassign-enum -Watomic-properties -Wcomma -Wconditional-uninitialized -Wconversion -Wcovered-switch-default -Wdate-time -Wdeprecated -Wdocumentation -Wdouble-promotion -Wduplicate-enum -Wexpansion-to-defined -Wfloat-equal -Widiomatic-parentheses -Winfinite-recursion -Wmissing-prototypes -Wnewline-eof -Wnullable-to-nonnull-conversion -Wobjc-interface-ivars -Wover-aligned -Wpacked -Wpointer-arith -Wselector -Wshadow -Wshorten-64-to-32 -Wsign-conversion -Wstatic-in-inline -Wsuper-class-method-mismatch -Wswitch-enum -Wunguarded-availability -Wunreachable-code -Wunused -Wno-unknown-warning-option -Wno-trigraphs -Wno-four-char-constants -Wno-disabled-macro-expansion -Wno-pedantic -Wno-bad-function-cast -Wno-c++-compat -Wno-c++98-compat -Wno-c++98-compat-pedantic -Wno-cast-align -Wno-cast-qual -Wno-documentation-unknown-command -Wno-format-nonliteral -Wno-missing-variable-declarations -Wno-old-style-cast -Wno-padded -Wno-reserved-id-macro -Wno-shift-sign-overflow -Wno-undef -Wno-unreachable-code-aggressive -Wno-unused-macros -Wno-used-but-marked-unused -Wno-vla -Wno-error=assign-enum -std=gnu11 -fconst-strings -fdebug-compilation-dir /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/buildbot_incremental/swift-linux-x86_64/libdispatch-prefix/src/libdispatch-build -ferror-limit 19 -fmessage-length 0 -fvisibility hidden -pthread -fblocks -fobjc-runtime=gcc -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -o src/CMakeFiles/dispatch.dir/init.c.o -x c /home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/swift-corelibs-libdispatch/src/init.c
01:05:35.076 1.	<eof> parser at end of file
01:05:35.076 2.	Code generation
01:05:35.076 3.	Running pass 'Function Pass Manager' on module '/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/swift-corelibs-libdispatch/src/init.c'.
01:05:35.076 4.	Running pass 'X86 DAG->DAG Instruction Selection' on function '@_dispatch_bug_kevent_client'
01:05:35.076 clang: error: unable to execute command: Segmentation fault (core dumped)
01:05:35.076 clang: error: clang frontend command failed due to signal (use -v to see invocation)
01:05:35.076 clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
01:05:35.076 Target: x86_64-pc-linux-gnu
01:05:35.076 Thread model: posix
01:05:35.076 InstalledDir: /usr/bin
01:05:35.076 clang: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
01:05:35.076 clang: note: diagnostic msg:
01:05:35.076 ********************
01:05:35.076
01:05:35.076 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
01:05:35.076 Preprocessed source(s) and associated run script(s) are located at:
01:05:35.076 clang: note: diagnostic msg: /tmp/init-f263a3.c
01:05:35.076 clang: note: diagnostic msg: /tmp/init-f263a3.sh
01:05:35.076 clang: note: diagnostic msg:
01:05:35.076
01:05:35.076 ********************

https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-18_04-long-test/1424/console

Note: The crash showed up in the same build this PR landed, so I think it's fairly clear this PR is what triggered it (not saying dispatch did anything wrong here, the compiler shouldn't crash!) probably via one of the changes in init.c.


Proj example

A readme describing the current state of Proj in mathlib and how graded algebra APIs are used has been added.


Return Nicer Errors when Non-Integer Values are Passed as Integer Arguments (CLI)

$ wsk action create actionName hello.js --timeout<PHONE_NUMBER>0303030303003
invalid argument "30303030300303030303003" for --timeout: strconv.ParseInt: parsing "30303030300303030303003": value out of range
$ wsk action create actionName hello.js --timeout asdf
invalid argument "asdf" for --timeout: strconv.ParseInt: parsing "asdf": invalid syntax

@dubeejw , I think this kind of error is throw by cobra package, right? can we control it?

I believe we can control the error message if we surround the strconv.ParseInt method calls in a try/catch, @lzbj.

If the issue is with Cobra we should open an issue with them.

Issue moved to apache/incubator-openwhisk-cli #132 via ZenHub


ubuntu 14. zookeeper/zookeeper.h: No such file or directory

After step cp jml-build/sample.local.mk local.mk
I run make compile NODEJS_ENABLED=0  And error missing file appear
           [C++] soa/service/zookeeper_configuration_service.cc
In file included from ./soa/service/zookeeper_configuration_service.cc:9:0:
./soa/service/zookeeper.h:9:33: fatal error: zookeeper/zookeeper.h: No such file or directory
 #include <zookeeper/zookeeper.h>
                                 ^
compilation terminated.

I check file is really not existed in project. which step config I missing?

Maybe you don't have rtbkit-deps installed in your machine. You will get zookeeper installed after rtbkit-deps installing.

I allready install that. After install rtbkit-deps. I clone rtbkit inside its folder and continue setup steps. And I try to find file zookeeper/zookeeper.h  in folder of rtbkit-deps, then still not found anywhere

@dieuit07 This file can be found in your system include directory, such as /usr/local/include, or /usr/include . Maybe you installed rtbkit-deps to a place which is not a usual include directory?

Yup, you right! I think I missing run make for rtbkit-deps ( in document not type that, but the main document  rtbkit-deps is exist ). thanks a lot @LycenYao


error in hellogdextension code

https://github.com/gilzoide/hello-gdextension/blob/main/1.hello-c/README.md
(EDIT: I mean error in the file 'hello.gdextension' shown in README.md, listing 8 )
linux.x86_64 = "libhello-gdextensions.so"
windows.x86_64 = "hello-gdextensions.dll"
macos = "libhello-gdextensions.dylib"

should be
linux.x86_64 = "libhello-gdextension.so"
windows.x86_64 = "hello-gdextension.dll"
macos = "libhello-gdextension.dylib"

(without character "s")
as the library file compiled by scons is named libhello-gdextension.so (in case of Linux target)
Otherwise running godot line gives error with strange path changes:
ERROR: Can't open dynamic library: {Godot project folder}/libhello-gdextensions.so.
Error: /home/USER/bin/godot-4.2.1/../lib/libhello-gdextensions.so: cannot open shared object file: No such file or directory.

Cheers!

Wow, true that! I made it right in the example file, but wrong in the article 😅
Thanks for spotting that out, I'll fix this right away!


Basemap mixed content issues

We have a couple of issues regarding secure basemap loading in the builder. The embeds are fine.

[ ] On every builder load, there is an http request to "http://a.basemaps.cartocdn.com/dark_nolabels/6/30/24.png" just after instantiation. The basemap changes but the coordinates doesn't, it is always that tile (south-west Spain/Portugal).

[ ] When changing the basemap, the new basemap will be requested by http. Refreshing makes it start requesting by https again.

cc @xavijam @matallo

this is related to the config basemaps, some of them might be setup with http:// instead of HTTPS, thus the mixing content issues
https://github.com/CartoDB/cartodb/blob/master/config/app_config.yml.sample#L351
this affetcs both the basemap and the thumbnails, in the thumbnials case it has already been reported too https://github.com/CartoDB/cartodb/issues/9445

Why don't we make that an application asset as any other UI related image?

Was looking at this and just found out that the config for prod still has the old category (CartoDB instead of CARTO). Staging is ok, though :confused:. We can fix it at the same time as the https changes. We will need to rerun the layer update rake.

Why don't we just use always https for basemaps?

we should send the right config depending on the protocol used:

if we are in the builder -> https
if we are sending viz.json:

send https urls if the viz.json is requested though https
http urls if the viz.json is requested though http

all the basemaps have a https url so let's start using it
Some background: we haven been doing that client side for years (https://github.com/CartoDB/cartodb.js/blob/develop/src/vis/layers.js#L11) so i guess is time to move it to the place it belongs

why don't we always send https urls on the vizjson?

why we would want to use https always? I understand there are some improvements if we use http2 but there should be a reason why adding such an overhead to render maps embedded in a newspaper

consistency and support for http2 when it gets enabled (our CDN already supports it on early preview, we haven't gotten to enable it yet)

ok, let's go for it

ENTERPRISE READY

Updated basemap config to use https. Only positron and dark matter with labels on top were affected by the change. The rest of the basemaps already used https.
Leaving open as we should also update existing layers.

Ok, rake is running to fix the category and attributions URL. This is not updating the source of the basemaps layers to https. I think the best option is not to touch that, and start using https only on new maps (which is already happening). I don't trust updating all layer sources with a rake, too many potential for problems for little gain.
Please reopen, if you feel that this is an important thing.

👏 thanks mate!


4.x: Upgrade to Java 21 (when ready)

[ ] change .github/workflows/validate.yml to use Java 21
[ ] check all instances of Java 17 and Java 19 (and all strings where Java version is mentioned) in documentation, javadocs and readme
[ ] change version.java in pom.xml
[ ] change maven.compiler.source in parent/pom.xml
[ ] change maven.compiler.source in examples/nima/quickstart-standalone/pom.xml
[ ] change maven.compiler.source in examples/quickstarts/helidon-standalone-quickstart-mp/pom.xml
[ ] change maven.compiler.source in examples/quickstarts/helidon-standalone-quickstart-se/pom.xml
[ ] change all Dockerfiles to use 21 - including native (where we need to use correct graalvm images), and templates

Usually requires:

[ ] change of Hibernate version
[ ] change of EclipseLink version

Hi, @tomas-langer I tried building the main branch with Java 21, and it failed because Java 20 is embedded in the poms, due to the --enable-preview. Would it make sense, seeing that this Nima branch requires virtual threads anyway, that we start building it on Java 21 directly, so that we don't need --enable-preview anymore?


Fix #518, Time Services Requirements Scrub

Describe the contribution
Updates TIME Services requirements, see issue for details.
Fix #518
Testing performed
None, doc update only
Expected behavior changes
None, doc update only
System(s) tested on
None, doc update only
Additional context
See related issues, #302, #519.  Review just the latest commit for changes directly related to the associated issue.
Third party code
N/A
Contributor Info - All information REQUIRED for consideration of pull request
Jacob Hageman - NASA/GSFC

CCB 20200226 - Approved

Closing since PR #526 includes this commit


Blogpost about comment locking and report categories

@eduardoj @saraycp @hellcp-work please have another look, I addressed your reviews

@eduardoj @saraycp @hellcp-work please have another look, I addressed your reviews

I still miss this suggestion: "I also suggest you write every sentence in a different line: it would make no difference when rendering the page, but it will make easier to review the text."

@eduardoj @saraycp @hellcp-work please have another look, I addressed your reviews

I still miss this suggestion: "I also suggest you write every sentence in a different line: it would make no difference when rendering the page, but it will make easier to review the text."

@eduardoj I overlooked it, its now applied

@saraycp done :)


MGSFragariaView refactored to eliminate MGSFragaria dependency

You mentioned this before; I simply wanted to capture it as an issue.

Fixed by c30dd8c.


Execute scripts when using html function.

This commit makes .html() to execute supplied scripts. Fixes https://github.com/fabiospampinato/cash/issues/366
jQuery realization is somewhat similar: https://github.com/jquery/jquery/blob/main/src/manipulation.js#L376-L400

Thank you! I'll get a few other changes in and make a release.

Btw I'm in the process of deleting pacco and its million of other dependencies from the dependencies list of Cash, so Cash should become easier to maintain and contribute to in the future.
I'd be happy if you'd like to contribute some more in the future. Sorry for the huge delay in getting stuff merged.

In hindsight getting this PR to work seems tricker than it seems 🤔 like if the string is a <script there are no script tags, or it could be <scripts /> or <script whatever="/>", like it's probably good enough, but I'm not sure what a perfect implementation looks like. I should check what jQuery is doing in this regard.

Here is what jquery logic looks like: https://github.com/jquery/jquery/blob/main/src/manipulation.js#L273-L297
Made a test on sites with jquery and cash:

function
jQuery
Cash

$('header').html('<script').html()
empty string
Exception is thrown: Failed to execute 'querySelectorAll' on 'Document': '<script' is not a valid selector.

$('header').html('<script>').html()
\x3Cscript>\x3C/script>
\x3Cscript>\x3C/script>

$('header').html('<scripts/>').html()
\x3Cscripts>\x3C/scripts>
\x3Cscripts>\x3C/scripts>

$('header').html('<script whatever="/>"').html()
empty string
empty string


Treehouse EIR. Closes #225

Good catch. Updated to point to the issue of that journal instead of the paper


TimeoutError: SMTP server started, but not responding within allotted time. This might happen if the system is too busy

Traceback (most recent call last):
File "C:/Users/Darkness/Desktop/crazy-email-recv-srv-master/dd.py", line 11, in
controller.start()
File "D:\python37\lib\site-packages\aiosmtpd\controller.py", line 315, in start
"SMTP server started, but not responding within allotted time. "
TimeoutError: SMTP server started, but not responding within allotted time. This might happen if the system is too busy. Try increasing the ready_timeout parameter.

You can try the ipconfig command to confirm the local IP address.
Plaese make sure that the IP <IP_ADDRESS> is the local IP and that there is no firewall blocking incoming connections.

I run it on my computer, the firewall is turned off, and there is no anti-virus software
------------------ 原始邮件 ------------------
发件人:                                                                                "aio-libs/aiosmtpd"                                                                                @.>;
发送时间: 2023年1月8日(星期天) 晚上8:35
@.>;
<EMAIL_ADDRESS>主题: Re: [aio-libs/aiosmtpd] TimeoutError: SMTP server started, but not responding within allotted time. This might happen if the system is too busy (Issue #362)
You can try the ipconfig command to confirm the local IP address.
Plaese make sure that the IP <IP_ADDRESS> is the local IP and that there is no firewall blocking incoming connections.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I run it on my computer, the firewall is turned off, and there is no anti-virus software

I run the same code with aiosmtpd 1.4.3 and it does not reproduce the problem.
My suggestion is still to check if the local IP address is correct, or you can bind <IP_ADDRESS> to test if you have the same fault.
If bind <IP_ADDRESS> is successful, you can run ipconfig and post the output to help diagnose the problem.

I run it on my computer, the firewall is turned off, and there is no anti-virus software

Yes, as @wevsty mentioned, can you verify that your computer's IP address is <IP_ADDRESS> and that IP address is active?
With no further information from you, I will close this issue because your error is not reproducible.


Research cluster crawling

Unit crawling is crawling with mutliple spiders on one domain and a single "brain"

My research indicated that there are a few ways to solve this:
Scrapyd: Although this is the preferred way of the author of 5 Steps to Building a Faster Web Crawler the problem with this solution is that there is no way to manage spiders that are dockerized. This product seems to only be able to manage spiders on the same machine (or VM in this case).
The only product I could find to solve this is
Scrapy Cluster: This seems to combine redis (which we weren't gonna use but since a job only requires temporary data while the articles URL we will still store persistently) apache kafka and dockerized spiders, seems like the perfect fit for us. The only problem stems from us having to get another database. But since we are making it temporarily stored, a small amount of space should suffice.

Scrapyd Redis


catch compare with one sample error gracefully

As mentioned by reviewer:

The tool generates an unfriendly error when I run the following command: strprofiler compare -scol "Sample Name" -o ./strprofiler_output ExampleSTR_long.csv  – “IndexError: single positional indexer is out-of-bounds”. I believe this is because there is only one sample in the file I provided, but a more helpful error message would be useful (I recognize that most users would know to do this in practice).

That test file actually has two samples, which still throws this error due to a hard-coded index during the sample-specific summary file generation (make_summary) whereby the "next hit" entry is pulled from the 3rd row of an ordered dataframe of all samples (the query followed by all the other samples).
Easy fix to check for this and avoid it.


fix(type): optimize event param types

Brief Information
This pull request is in the type of:

[ ] bug fixing
[ ] new feature
[x] others

What does this PR do?
This PR enhances the type of event params.  It will provide more detailed params on mouse events.
Fixed issues
https://github.com/apache/echarts/issues/14057

Is there any chance that we can export the types for the event callback parameters?


Plug-in does not work with the Gradle Kotlin DSL

When using the Gradle Kotlin DSL the plug-in does not work anymore. The reason seems to be the use of Groovy's metaClass to add addCucumberSuite. This is not available from the Kotlin DSL.
Since more projects are moving to the Kotlin DSL I hope that this plug-in can either support it or document a way how it can be used with it.

We would be open to accepting a merge request that resolves this conflict with the Kotlin DSL as long as it didn't break existing usages.


Add some of the perf tunning performed for 741 vm testing

Add some of the perf tunning performed for 741 vm testing
Partial #259

Closing as stale


Question regarding stage 4 HD image size

Hello,
Thank you for the great work!
For stage 4 (instruction tuning with HD data), the current code seems to resize/crop image to 224x224:
https://github.com/OpenGVLab/Ask-Anything/blob/main/video_chat2/scripts/videochat_mistral/config_7b_hd_stage4.py#L21
https://github.com/OpenGVLab/Ask-Anything/blob/main/video_chat2/dataset/__init__.py#L73
which means it's actually using 224x224 frames for training. Is that true? If so, what is this "HD" about? Or did I miss something?
Thank you!

224 is the input resolution of our vision encoder. You can refer to the dynamic resolution setting of HD https://github.com/OpenGVLab/Ask-Anything/blob/c3f07988b1db77ed24d706650d3cb23e3495a011/video_chat2/scripts/videochat_mistral/config_7b_hd_stage4.py#L85-L90
dynamic_config=dict(
local_size=224,
hd_num=6,
padding=False,
add_global=True,
),

Thank you for the swift response! I see how the dynamic resolution setting is working for HD training.
One followup question is - I saw the blocks is not used in videochat2 HD training.
https://github.com/OpenGVLab/Ask-Anything/blob/main/video_chat2/dataset/hd_utils.py#L93
However, in the InternVL code that videochat2 code is referring to, they used the blocks to generate (local_size x local_size) sub-images:
https://github.com/OpenGVLab/InternVL/blob/2d93b099ffbbf45d1db59710914f26fce4494104/README.md?plain=1#L752-L771
Does that mean videochat2 HD training doesn't use the sub-images, and uses the resized images instead? In that case, how does that work with the vision encoder 224x224 input setup?
Thank you!


Migrate from version 1 – 2

[ ] Check if updating to the latest version resolves the issue

Environment

[ ] I am using @preact/signals-core
[x] I am using @preact/signals
[ ] I am using @preact/signals-react

[ ] I understand usage changed in v2, and I've followed the React Integration instructions

Describe the bug
A clear and concise description of what the bug is.
Updating @preact/signals to version two throws a new error about cycle detected.
Uncaught Error: Cycle detected
    at ot.S (signals-core.module.js:1:3798)
    at at (signals.module.js:1:401)
    at signals.module.js:1:1526
    at signals.module.js:1:1359
    at V (preact.module.js:1:6239)
    at preact.module.js:1:9281

This is a deployment that demonstrates the issue: https://3e585ed9.vanishing-page.pages.dev/
The production deploy, that is the same code but is working.
Expected behavior
Should not throw, or the new behavior should be documented.

We need a minimal reproduction, not a deployed site please.

I have made this demo repo. I am working on getting a more minimal code pen going.
https://github.com/nichoth/signals-reproduction

Quick observation, somehow the buttons which only touch signals in their click callbacks are causing this. When I remove those buttons the issue goes away 🤔

Hmm, there are multiple versions of signals present
❯ npm list @preact/signals-core
<EMAIL_ADDRESS>/Users/jovi/Documents/SideProjects/signals-reproduction
├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>deduped
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>

Thank you for checking this out. That is indeed the problem. I updated the dependency to also use signals 2.0, and now it is working. Odd that it caused the "cycle detected" error, but thanks for looking into it 🙏

Yes, I am not quite sure what caused the cycle detected with that but it might just be that the signal gets fed into one of the computeds/effects used in @preact/signals which comes from a different version which can cause some hiccups


[BUG] Stubborn user blocking and strange overlay issues

Describe the bug
When a WoT blocked profile is unblocked Amethyst blocks it again almost immediately. When this happen a strange note residue is left in the feed. Please see the recording.
To Reproduce
Steps to reproduce the behavior:
Go to a profile blocked by the WoT feature. In my case npub10sa7ya5uwmhv6mrwyunkwgkl4cxc45spsff9x3fp2wuspy7yze2qr5zx5p and try to unblock it.
Expected behavior
User unblocking will have permanent effect and would take precedence over WoT.
Video and Screenshots
https://otherstuff.shaving.kiwi/52a58e9e83f171cddf0971ae4f6d7e98693d84c3f02af8cb189ec825614e7a05.mp4
Device (please complete the following information):

Phone Brand/Model: OnePlus 9 Pro
Android Version: 14
App Version: v0.91.0-play

It's not a WOT feature, it's the anti-spam feature. That account has 5+ completely equal posts in a short time and is classified as a spammer. You can turn the anti-spam filter off in the security filters on the left drawer OR you can follow the account.

Thank you for your answer. I can't get rid of the feeling that the behavior is strange and user action should take precedence over an automatic mechanic, but that is an opinion and not a bug. :-)
The overly residue to the other hand seems like a real bug.

Yeah, we should add custom code to deal with this case on the unblock button. We just haven't had the time yet. :)

Oh weird stuff like that has been happening to me too. I disabled the spam settings and the weird things stopped.
I like having control of everything , I myself want to decide if it's a spam profile or not.
Now I understand what was happening


Fix flickering when resizing visualization

Pull Request Description
Fix #9136.
Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[ ] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[ ] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

I don't fully understand why this works. I can see the feedback loop caused by resize observer action eventually causing node's width style to be updated, but this doesn't really address that issue. It just happens to break that feedback loop for some other reason. Do you have any explanation why?

The size of the node content is an input to the viz size computation, which is an input to the size of the container for the node's content. If the node content is display: flex, its size is dependent on the size of its container; making it inline-flex keeps the container size from affecting the content size, breaking the feedback loop.


Error parsing URL with "!" in it

Issue:
I am trying to install an environment containing x264 that uses --file <url-to-file-containing-package urls>.
When conda tries to parse the spec line for x264 it says:
CondaValueError: could not parse 'http://dist.ceda.ac.uk/jaspy/jaspy3.7/m3-4.7.10/linux-64/x264-1!152.20180806-h14c3975_0.tar.bz2' in: ./bin/../environments-ceda-jaspy-envs/py3.7/m3-4.7.10/jaspy3.7-m3-4.7.10-r20191126/channel-urls.txt

I can hack the conda library to overcome this but the error is due to a regex that doesn't like the ! character in the spec (URL), in:
conda/cli/common.py
Could you remove the ! from the URL in the next version? Thanks

! cannot be removed (it indicates the version epoch). Please open an issue against conda.

Thanks @sdvillal , I'll do that.


Can't testing Microsoft Bot Framework Emulator?

I'm new developer for skype bot. After I have created a bot application and then testing it but I can't.

You have to specify Microsoft App Id and Microsoft App Password in the fields on the top.

Where is Microsoft App Password?. I just create bot application and haven't programming yet.

Should be the same as in your Web.config. For local testing, these can be anything, but the values in the emulator should match the ones in your configuration. Later, you'll acquire these during the bot registration.

The exception message in your screen shot implies it's something related to SSL:
"System.IO.IOException: The handshake failed due to an unexpected packet format"
When using the emulator, you should be able to skip authentication by leaving those fields blank.

https is not enabled by default for localhost. Change the bot url to http://localhost:3979/api/messages instead of https://....

https://docs.botframework.com/en-us/csharp/builder/sdkreference/gettingstarted.html. I can see it that don't use microsoft app id...

@Englbach you don't need the MicrosoftAppId and MicrosoftAppPassword if you want to debug your bot locally. When you are not indicating those values the bot authentication will be disabled the for the bot.

thanks msft-shahins.

If I wanted to Debug it from Azure where is the AppPassword?  The source code came from Azure.  Where is the documentation on adding an AppPassword...


Make it possible to contain multiple messages for CPFormatViolation

In enrich we techincally can extract 1+ FailureDetails.CPFormatViolationMessage. But since Failure.CPFormatViolation supports only single message, we're forced to return NonEmptyList[BadRow.CPFormatViolation] in loaders, which is confusing and misleading - only single payload or single error can be returned by toCollectorPayload.
An easier workaround would be to short-circuit toCollectorPayload on first error as it's rare enough for two errors to happen at once, but I'd like to preserve as much info as possible.

This should be collector_payload_format_violation/2-0-0 and since we're bumping model anyway, it's worth to change property names to something less ambigous, e.g. messages to cpFormatViolationMessages - a very long name, but I think this namespacing is the best way to avoid collisions #50


Unable to pull data from GCP project

HI SM team,
I don't seem to be pulling data form my GCP project. AWS works fine.
I matched the name and the project ID, created and placed the credentials file in a readable spot and restarted the scheduler. The Accounts page has the correct entry/
Does the credentials file need to be in a specific folder/directory? It currently has 660 and is owned by ubuntu:www-data. I am using the json format.
What is the best way to debug this?
My Setup -
SecurityMonkey Front end in AWS
SecurityMonkey Postgresql in AWS on separate back end

cplvic gathering valuables to burn as an offering to the gods for wisdom

Do you have any errors in any of the /var/log/securitymonkey/*.log files?
I think I had some issues with my SM installation when I last tried it, but this was back in March. (I also installed SM on GCP, not on AWS.) I ended up assigning the "Storage Object Viewer" IAM role to the service account before I could see the GCP buckets. Unfortunately, this was awhile ago, so I don't know if doing that will address your issue.

HI @carise I don't actually see anything in the logs. Its very strange. I just got SSO working so I was concentrating on that last night. Now onto this GCP thing.

I don't know if this is the case for you, but I had to change the permissions on /var/log/securitymonkey/*.log, you might need to chown them to www-data.
Also, I have in my notes that /usr/local/src/* had to have the owner as www-data... I don't know why though, so maybe don't do that yet, just the logs.

the logs are working. I don't see anything (data) related to my GCP account after I added the account. I did make it active as well.  AWS is working just fine.

What roles does your GCP service account have?

Viewer and Security Viewer

Ok. So I just ran through a fresh install of Security Monkey and added my GCP account through the UI.
My project id is not the project number.
Credentials are stored in home directory (probably could be a better place, but for now, just for testing purposes)
and checked the "Active" box. Then I restarted.
Is this similar to what you have?

I matched the Name and Project ID.
I made a dumb assumption but the Project ID is a string based on what is in the json file correct?
so if it is
"project_id": "mycompany-dev"
then I would input mycompany-dev in the Project ID field in the UI?
Thanks for your help @carise

Yes, that is the correct project id. The name can be anything. My credential file permissions are 640 to ubuntu:www-data as well.
Hmm, I don't know :( That's really bizarre that you're not able to pull data still. I don't think I see any activity regarding GCP in the logs either...

Hi @carise - I am running on AWS,
I installed gcloud sdk. Did you install that under the ubuntu profile or install it it at all?

I haven't used the gcloud sdk on the ec2 instance where I installed SM. I don't think that should affect whether SM can auth your json key though.
The only thing I can think of that is affecting how SM can (or cannot) connect to GCP is through the service account configuration and perhaps the IAM API not being enabled. Assuming you followed this guide, were you able also to enable the IAM API? (gcloud service-management enable iam.googleapis.com or via the IAM API page)

yes. The admin confirmed the api is enabled as well.
I am going to setup a new staging instance  to see if I messed up on some install part

Ok. I would recommend also seeing if creating a separate service account under your project, exporting that key, and creating a new SM GCP monitor with this new key, would happen to work.

@carise : Thank you so much for your assistance! :)
@cplvic : Have you been able to get this to work?

I will have a new setup for this on Thursday or Friday.  after these messages, we'll be right back


componentWillReceiveProps deprecation

Will be working on this in the next coming days.

Thanks, looking forward to it
On Sat, Dec 28, 2019 at 9:43 PM Felipe Peña<EMAIL_ADDRESS>wrote:

Will be working on this in the next coming days.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Twotalltotems/react-native-otp-input/issues/28?email_source=notifications&email_token=AEH5IKC2ILZZ65TJJPIBLOLQ26F25A5CNFSM4JWKBPD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHYOYXA#issuecomment-569437276,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEH5IKCVIFOT4GQJ67QGF7DQ26F25ANCNFSM4JWKBPDQ
.

Is it okay to fix this and send a PR?

sure thing!

This issue had been validated to be fixed after #64 .


Get 1.17 in workflow

What about 1.17.1 instead?

The idea is to use minecraft-packets in prismarine-proxy, so ideally we would need both, but I was thinking maybe we do 1.17 and prismarine-proxy can point at the major version ( since I don't think packets change between minor versions)

Packets do change between minor versions
1.17.1 could be the reference for 1.17 no ?

Packets do change between minor versions

Oh I wasn't aware.

1.17.1 could be the reference for 1.17 no ?

Then we have to have a reference table, for what versions correspond to what packets.


Update TextileImage; add Avatar caching

Uses the image cache option to try and force it, but that's an incomplete solution. so here will also use the local ipfs node to grab avatars, meaning the app should look a lot better when on spotty internet or no connection

scratch the ipfs image part, just undid that. round about way of getting there but realized the avatar component was too aggressively refreshing content. when app goes into background, we don't want to trigger a refresh actually, so fixed that


Is it possible to keep blur without showing border?

I would like to hide border but keep window blur, is this possible?
I found I cannot do window_border_width 0 and I cannot disable border either as blur needs window_border on. Would appreciate any help :)

Maybe making the color transparent would be a workaround. yabai -m config active_window_border_color 0x00000000

Borders have been removed in the latest release (v6.0.0) (#1889) because of multiple issues present in both Ventura and Sonoma.