Saga doesn't dispatch new events

I wrote a test application using saga's and it seems that I cannot figure out how to dispatch new actions. All the examples show using the put command with the action data to dispatch a new action, but I cannot get it to work.
I've tried
yield put(actions.receiveTodos(todos));

yield put({
  type: 'RECEIVE_TODOS',
  todos
});

The only way I was able to get it to work was with the following (which required exporting the store to the window):
yield put(window.store.dispatch(actions.receiveTodos(todos)));

Source: https://github.com/steven10172/todo-list/blob/master/src/sagas/index.js#L8
If someone could point me in the right direction I'd greatly appreciate it.

You had configured store in some wrong way, I've tweaked your configuration and its working now
import { createStore, applyMiddleware, compose } from 'redux'
import createSagaMiddleware, { END } from 'redux-saga'
import rootReducer from '../reducers'

export default function configureStore(preloadedState) {
  const sagaMiddleware = createSagaMiddleware();
  const composeCreateStore = () => compose(
    applyMiddleware(sagaMiddleware),
    window.__REDUX_DEVTOOLS_EXTENSION__ ? window.__REDUX_DEVTOOLS_EXTENSION__() : fn => fn,
  )(createStore)
  const finalCreateStore = composeCreateStore()
  const store = finalCreateStore(rootReducer, preloadedState)

  store.runSaga = sagaMiddleware.run;
  store.close = () => store.dispatch(END);

  return store;
}

additionally you are desctructuring wrongly your takers with this configuration
yield take(({action}) => action && action.type === ADD_TODO);
should become
yield take((action) => action && action.type === ADD_TODO);
or even more concise for this simple use case
yield take(ADD_TODO);
I hope it helps

Thanks. I will try it out later today. I only had the yield statements like that due to how the data was being passed to them, but that was probably due to the store constructing issue.

Did it help for you? I would like to close the issue, but aint sure if your problem got resolved.

Thanks. I was able to play around after your suggestion and it seems that there was an issue with the window.__REDUX_DEVTOOLS_EXTENSION_ initialization.
After using your line to initialize redux dev tools everything was working as expected: https://github.com/steven10172/todo-list/commit/c949601bb239f3674bff94af05bad7554f777647


environment install using pip

ERROR: tf-nightly-2-0-preview 2.0.0.dev20191002 has requirement gast==0.2.2, but you'll have gast 0.3.2 which is incompatible.
ERROR: tf-nightly-2-0-preview 2.0.0.dev20191002 has requirement numpy<2.0,>=1.16.0, but you'll have numpy 1.15.1 which is incompatible.
ERROR: tf-nightly-2-0-preview 2.0.0.dev20191002 has requirement tb-nightly<2.2.0a0,>=2.1.0a0, but you'll have tb-nightly 1.14.0a20190505 which is incompatible.
ERROR: tensorflow-gpu 2.0.0a0 has requirement tb-nightly<1.14.0a20190302,>=1.14.0a20190301, but you'll have tb-nightly 1.14.0a20190505 which is incompatible.
when i use pip install requirement.txt the error occor

I think your environment have tf 2.0 installed, whose version is not exactly the same as the version we use.
I suggest you using conda as an environment managing tool so you can make sure that the environment is not polluted.

i have same problem before.
you can check tensorflow version. it should be same with tensorflow version
you can check the keras version. it should capable
https://docs.floydhub.com/guides/environments/


Using lemmas (especially for Arabic)

I wanted to check to make sure UniversalPetrarch is using the word lemmas, since this is an especially important issue for Arabic. This line seems to imply that it's potentially preferring the raw text instead of the lemmas. Am I reading that right, @JingL1014? More broadly, is UP working on lemmas instead of raw tokens?

For verbs, it is working on lemmas. But for nouns, it now checks raw text first and then checks lemma. Because the nouns in the English patterns are not all in lemma form now.

This really a crucial point. Udpipe produced two lemmas for each verb, like the following:
قال	قَال	VERB	VP-A-3MS--
The difference between the two is that one contains short vowels (the left-most one), and one does not. Do you know which lemma is petrarch using here ?

From UDpipe, the first word is the original form and the second word is the lemma form. Right now UDpetrarch uses the lemma form of verbs. If the verbs of Arabic verb dictionary don't have diacritics, we can first use packages such as PyArabic to remove the diacritics of lemmas first and then do event coding.

where in preprocessing exactly can I do that ?

You can modify the variable parsed in the preprocessing code generateParsedFile.py by adding this additional preprocessing step. But this code is for all three languages, you need to add an argument to make sure this only works for Arabic inputs. Or you can write another code to only process Arabic documents.

Ok. I have resolved this.


iOS build failing to be assigned to proper flight teams.

The iOS build is failing with: "Build is not assignable. - Build is not in an externally assignable state." Need to R&D to figure out why this is happening.

Not sure why it failed. It was assigned to another external team just file. I think Apple must be glitching so I'll retry a 2nd build before I look into this more.


Update mancy.rb version to 2.0.1

Thank you for the contribution. It was merged directly as 86becae9f6de3ae129da1624731cd04396c3633c to keep commit history cleaner. Your contribution is still credited to you.


Fix first pull errors on new system

Immediately after init on a new system, when pulling files down from repo, get error if tracked file doesn't already exist on machine.

dotdock init
dotdock pull

Password for '<repo>':
From <url>
 * branch          master          -> FETCH_HEAD
Error: Unable to find file '...'


PCTCreateBase option to specify source database

Add option to start from non empty database
As far as I know it's not possible to create a database starting from an existing database
e.g. the equivalent of prodb sports2000 sports2000
A workaround exists by calling prodb (see  build.xml) but it would be nice if PCTCreateBase had this option

Seems like a duplicate of #31 ?

closed as duplicate of #31


SPIFFS Mount Failed -10025

Hi,
after a lot of Troubleshooting i need to ask.
Is there an known Problem with SPIFFS`
I get the Message after Flashing
   31 INFO             InitState.cpp:  415 PIXELIX starts up ...
    32 INFO             InitState.cpp:  416 SW version: v5.0.3:lc
    33 INFO             InitState.cpp:  417 SW revision: c0bae8e9375ec54c6ab148b037bdde6e7a96b5ae
    42 INFO             InitState.cpp:  418 ESP32 chip rev.: 1
    47 INFO             InitState.cpp:  419 ESP32 SDK version: v3.3.5-1-g85c43024c
    55 INFO             InitState.cpp:  420 Wifi MAC: 78:E3:6D:11:8A:60
    61 INFO             InitState.cpp:  421 LwIP version: 2.0.3
    69 ERROR                   SPIFFS:    0 mount failed, -10025

[E][SPIFFS.cpp:89] begin(): Mounting SPIFFS failed! Error: -1
79 FATAL            InitState.cpp:  144 Couldn't mount the filesystem.
86 INFO            ErrorState.cpp:   73 Going in error state.
92 INFO            ErrorState.cpp:   80 Low level error 4.
Did i miss something or do i got Bad Luck with the ESP-Modules?
Change the hardware and Tried Erasing the Flash with 2 different Programs.
Even with the precompiles bin.
Same outcome...

Did you flash the filesystem first?

Thats a good point. Thanks for the clarification.


[feat] Duration of brightness change on Android

Description (What is the problem)
There is no way to control how fast the brightness changes on Android.
Solution suggestion
A 'duration' property that lets you set the duration with the Duration class. Is this possible?

Hi @francistac. If I am right,  you would like to change the brightness changing animation duration. Right?

Correct

Hi @francistac. If I am right, you would like to change the brightness changing animation duration. Right?
Correct

Hi @francistac, for Android, there isn't any native provided method to change the screen brightness with duration. Any suggestion  and what you are trying to achieve?

Hi @francistac, for Android, there isn't any native provided method to change the screen brightness with duration. Any suggestion and what you are trying to achieve?

I guess there is no possible way to change the duration then, thanks for looking anyways. Thank you for your work so far with this plugin, & thank you for your time.

Is there a way to remove the brightness 'fade' animation? Like just an immediate change between different brightness values, with no animation between the transition.

Nope I don't think so. It depends on the Android ROM.


Changed time buffer for MarketOnClose order submit from 11 to 16 minutes

Thanks Stefano. For others reading this -- the NYSE changed the market on close order time to 15 minutes prior to close.


Image matching similarity

How do I get two Image matching similarity through these keypoints?

Hello @Simpsoncompal, thank you for your interest in our work!
If I understand correctly, you are referring to the semi-dense matching setting. You can obtain the distances of the coarse features by computing the similarity matrix (also called brute-force matching) between the two feature sets. Please take a look at this function.

Closing due to inactivity. Please feel free to reopen if the issue remains unresolved.


REQUEST:  repo for multi-cluster scheduling

Name for new repository:
volcano-global
Who should have admin access(subproject owners)?
@kevin-wangzefeng
@william-wang
Who should have write access?
@william-wang
@kevin-wangzefeng
@lowang-bh
@hwdef
@Monokaix
Who should be listed as approvers and reviewers in OWNERS?
approvers:
@william-wang
@kevin-wangzefeng
@Monokaix
reviewers:
@william-wang
@kevin-wangzefeng
@lowang-bh
@hwdef
@Monokaix
What should the repo description be?
Repository for federation scheduler for multi-cluster
Additional context for request.
This repository was created previously with the name federation, We'd like to replace the repo name from federation to volcano-global.  We had many discussion about multi-cluster scheduling previously. This year we are designing and implementing this feature in LFX project. Right now we'd like to contribute it to community.
https://github.com/volcano-sh/federation
related issue:
https://github.com/volcano-sh/volcano/issues/3310

+1
That's a great feature!

glad to see it

+1

+1
Looking forward to seeing this feature

Looking forward to it! Hope to contribute

Related issue: https://github.com/volcano-sh/volcano/issues/3731
it included the all components now

Repository setup done at: https://github.com/volcano-sh/volcano-global
As volcano/federation was not used, there's an automatic redirect behavior to volcano-global now.

The repo is ready now, close the issue.


No support for InstaX3 and X4

Any plans for supporting the x3 and x4 in near time?
Thanks!

do you have a sample file?

sorry for my late answer. I just recorded some seconds so that you have the native file format from my instax3.
here is the data for you to download:
https://we.tl/t-G6xLapz7LA
can you provide a general idea if you are able to support the x3 or x4 in the near future? it would be very helpful.
thanks.

it already parses that file correctly

Ah okay. It doesnt appear under supported formats. But good to know that. I will try it now.


Refactor buttons to follow OOTB behavior

Business value
As a content author/editor, I want a clear and standardized way to choose the styling of buttons across all blocks and pages.
Description
The current implementation of blocks has button styling defined by the order buttons are placed, i.e. when there are 2 buttons one below the other, the 2nd one is treated as a secondary button.
This implementation needs to be changed to align with the OOTB Franklin behavior, where variations of buttons are defined by the emphasis of the text in the Word document (e.g. bold or italic).
Acceptance Criteria

[ ] Button styling is dictated by the emphasis of the text in the Word document (e.g. bold, italic, underline, etc.) rather than the placement of the buttons.

Notes
Franklin OOTB Buttons docs

This issue will be solved in conjunction with #115

This ticket is on hold until the end of the redesign due to code changes needed for the button that would conflict with the changes needed for redesign.

Kamino cloned this issue to hlxsites/vg-macktrucks-com


Fastapi To Robyn

I want to migrate my fastapi application to robyn. I read the documentation of robyn. Its usage is indeed very similar to fastapi, but it does not support pydantic.  I think it would be better if robyn could support pydantic for data verification, so that my fastapi application can basically be seamlessly migrated to robyn.  Secondly, I am still concerned about whether robyn can fully support sqlalchemy's async connection. I read the official document and the example above uses synchronous pymysql, not asynchronous aiomysql.  I really like this project, thank you for your efforts

Hey @Xingsandesu 👋
Thank you for opening the issue 😄 .

I think it would be better if robyn could support pydantic for data verification, so that my fastapi application can basically be seamlessly migrated to robyn.

This is a top priority issue for us! It will be definitely implemented within the next few weeks 😄

Secondly, I am still concerned about whether robyn can fully support sqlalchemy's async connection. I read the official document and the example above uses synchronous pymysql, not asynchronous aiomysql.

Robyn supports all sorts of async tasks. But if you have something in mind that you'd like to clarify, I would be happy to have a look

Robyn supports all sorts of async tasks. But if you have something in mind that you'd like to clarify, I would be happy to have a look

thank you very much for your work😄.
This is part of my database code.This example uses sqlalchemy.ext.asyncio and aiomysql to implement an asynchronous database session, and uses the fastapi dependency to use an asynchronous database session. This will prevent various database operations from forming performance bottlenecks due to the bottleneck of pymysql. I think I should be able to use a similar method if I migrate from fastapi to Robyn. Thank you very much for your work. When pydantic is supported, I will cooperate with you to test this version as soon as possible if possible.
setting.py
....
DATABASE_URL = f"mysql+aiomysql://{DATABASES['USER']}:{DATABASES['PASSWORD']}@{DATABASES['HOST']}:{DATABASES['PORT']}/{DATABASES['NAME']}"
....

models.py
from sqlalchemy.ext.asyncio import create_async_engine, AsyncSession
from sqlalchemy.orm import sessionmaker, declarative_base
from settings import DATABASE_URL, DATABASE_ENGINE_ECHO, DATABASE_ENGINE_POOL_SIZE, DATABASE_ENGINE_MAX_OVERFLOW, DATABASE_ENGINE_POOL_TIMEOUT, DATABASE_SESSION_EXPIRE_ON_COMMIT

engine = create_async_engine(
    DATABASE_URL,
    echo=DATABASE_ENGINE_ECHO,
    pool_size=DATABASE_ENGINE_POOL_SIZE,
    max_overflow=DATABASE_ENGINE_MAX_OVERFLOW,
    pool_timeout=DATABASE_ENGINE_POOL_TIMEOUT
)

SessionLocal = sessionmaker(
    engine,
    expire_on_commit=DATABASE_SESSION_EXPIRE_ON_COMMIT,
    class_=AsyncSession
)

Base = declarative_base()

async def get_db():
    session = SessionLocal()
    try:
        yield session
    except Exception as e:
        logger.error(f"error:：{str(e)}")
    finally:
        await session.close()

...

view.py
...
async def add_user(user: UserCreate, db: AsyncSession = Depends(get_db)):
    if await record_exists(db, "users", {"userName": user.userName}):
        raise HTTPException(status_code=400, detail="User name already exists")
    else:
        db_user = User(**user.model_dump())
        db.add(db_user)
        await db.commit()
        await db.refresh(db_user)
        return db_user
...


remove binary objects from source tree

https://github.com/neuvector/neuvector/tree/main/dp/third-party/.objs
this and its subdirectories should not be part of the sources imho. Please delete it

These are pre-built object files, so not everything has to been built from the scratch.


Feat: add include polyfill option

Changes

Add  the option for include as a polyfill option. This option only includes specified packages.
If no include option is given, keeps the current behavior, adding all packages.
If protocolImports is true, also adds node:[module], only to specified packages in include.
If both include and exclude options are given, the exclude option is ignored.
Also, adds a list of all available modules to README.md.

Fixes #24

@leticiavna Thank you so much for this PR! 🎉


Upgrade Go to 1.13

https://golang.org/doc/go1.13
Fixes W-6833321.

Travis is failing with errors like:

This appears to be due to  CL 173722, which according to the Go 1.13 release notes means:

Testing flags are now registered in the new Init function, which is invoked by the generated main function for the test. As a result, testing flags are now only registered when running a test binary, and packages that call flag.Parse during package initialization may cause tests to fail.

And busl calls flag.Parse() during init() here:
https://github.com/heroku/busl/blob/b8a2c337ce97d86b27158512ffd8d18d1a36e9ba/broker/redis.go#L45-L52
The purpose of init() (something I wasn't familiar with) is described here:
https://golang.org/doc/effective_go.html#init
So sounds like we need to move the flag parsing (and thus also Redis connection pool setup) out of init and into TBD.

Flag parsing shouldn't happen in a package. It should happen in the main one, and the value should be passed as configuration to the appropriate methods.

Agreed; though this now means quite a refactor of broker usage is required.

Agreed; though this now means quite a refactor of broker usage is required.

learning by doing :p
on a more serious note, i think we should do this because otherwise we are locked to 1.12

So I got this kind working after a refactor, however to then get the tests passing would have required duplication of main setup in test setup, or else yet more refactoring (eg to break out config from main).
Whilst many of these changes would likely be a good thing to do longer term, I'd like to avoid mixing too many changes into one PR (given the issues we had around eg the Metaas Go upgrade that touched hundreds of files).
As such I think the best way to solve this is just to remove support for the -redisUrl flag entirely, since it's not actually used, given that tests+production use the REDIS_URL env var instead.

Deployed to production


C++\error\patterntriangle.cpp

The sample input and output is mentioned in the code !!
You have to find the error
NOTE:- Screenshot of the code and output is required

Can you please assign this issue?


Refactor Tests + Light Other Refactoring

Requirements

Filling out the template is required.

All new code requires tests to ensure against regressions.

However, if your PR contains zero code changes, feel free to select the checkmark below to indicate so.

[X] Have you ran tests against this code?

[ ] This PR contains zero code changes.

Description of the Change
While I know it's worrisome to modify tests after creation, rest assured this PR changes no content of tests other than the paths within require statements.
This PR aims to reduce how messy some aspects of the codebase has become.
Namely the exists of multiple folders within ./src that were different folders for tests to reside in. As well as the existence of dev-runner folder within ./src that contained the initial-migration of database data for the test suites, as well as the built in mock GitHub ExpressJS Server.
Firstly, this PR removes ./src/git.js since it is no longer used within the codebase, it's accompanying test file and the GitHub ExpressJS Server.
Otherwise this PR moves all tests into the ./test folder, using the file names to differentiate between different test types, such as unit, integration, vcs. Although these test types matter a whole lot less with the new mock capable framework used by the VCS modules, which means things like a mock GitHub server are no longer needed once tests are fully converted.
Additionally better mocking could allow the other edges of the testing platform to be remedied such as interactions with Google Cloud.
Since otherwise by mocking web requests from VCS, the Dockerized DB (That has existed for some time) Google Cloud Storage interactions are the last sections of code that haven't been fully tested due to the fact they reach the outside world. But mocking this we could fully be able to run all tests without much issue or concern.

While this PR doesn't address all the goals stated above, it starts the changes needed to make it happen.

So I did end up having to modify a few tests that had somewhat relied on the state of the database. Things like checking the order of packages returned by checking specific package names returned. Which could change if packages are deleted in another test, or receive more or less stars in other tests.
This does bring up a great point, something I'd love to see is to ditch the global state of the db during tests. Where rather we could have each test clear the whole db except tables. Then we have each test create the resources it'll be used within their test. So there is less guesswork, and makes things much more obvious


Fix queue name

Coverage remained the same at 93.225% when pulling f53c31668dad711cd14f346c8e18f5291c08b305 on incubus:master into 9ee66afaaf4533172c689ecf77ad83983d61ff65 on ondrejbartas:master.

Coverage increased (+0.09%) to 93.316% when pulling 821d6593b3d6083af58c3b0b89687c487c29f952 on incubus:master into 9ee66afaaf4533172c689ecf77ad83983d61ff65 on ondrejbartas:master.


feat(security): Introduce CodeQL security scanning on push, PR and an…

Adding non-blocking CodeQL vulnerability scanning on push and PR, as well as an hourly schedule.

Is it still active? Or else we will close it.

Close for no activity on it.


extend darksidewallet locking

Closes #433. This is a test-only bug-fix. See #433 for a detailed analysis. This PR tightens up the locking, moving the mutex out of the state structure so that Reset() doesn't re-create the mutex. That mutex should never be recreated (if it is, it's difficult to know that there aren't any locking bugs).

I found a bug (in this PR, not in master) that explains what you're seeing, please try the latest, 0a68f1955528403cfa7ff79a24ad8f8bf721e0b2

I see test failures for those involving retrieving submitted transactions. with this RPC /cash.z.wallet.sdk.rpc.DarksideStreamer/GetIncomingTransactions. I'll follow up with more details.

Force-push to fix a GetIncomingTransactions bug (introduced only in this PR), @pacu, please try again, it should be fixed.


added Endpoint to calculate Number of Periods - PV & FV

functions.py

main .py

sample result

Looks Good!


(next-urql) - Node crashes with  { ssr: true }

urql version & exchanges:
  "dependencies": {
    "@urql/exchange-graphcache": "^4.3.6",
    "@urql/exchange-refocus": "^0.2.5",
    "graphql": "^15.8.0",
    "next": "^12.1.0",
    "next-urql": "^3.3.2",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-is": "^17.0.2",
    "urql": "^2.1.3"
  },

Steps to reproduce

git checkout https://github.com/longfellowone/tools.git
cd tools/web
git checkout bug
npm install
npm run dev
Navigate to http://localhost:3000/
Page should work load ok
In tools/web/components/EmployeeOption.tsx uncomment line 18  // const [{ data }] = useEmployeeListQuery()
Page does not load / Node crashes

Might have something to do with useEmployeeListQuery() needing to be deduped as its called within a loop
Expected behavior
Should work
Actual behavior
Page does not load / Crash

We often ask for a minimal reproducible example as we can't really go through the full code of everyone 😅 hence I made a small repro already here and will try to shed some light on the difference betweeen ssr: true and not.
As you might have noticed the new next method getXProps are happening outside of React land which makes us do a lot of passing stuff through to each other, this was not always the case. Before this getInitialProps was the way to go, this method had access to the React tree and we can invoke react-ssr-prepass which allows us to resolve all the useQuery calls. So this option is basically a more automated way but does not protect the user of making unintentional waterfalls

my node version is 16.14.0
I just tried with 16.7.0 and am getting the same results. Did you do the step below?

In tools/web/components/EmployeeOption.tsx uncomment line 18 // const [{ data }] = useEmployeeListQuery()

useEmployeeListQuery() is generated from graphql-code-generator if you use const [{ data }] = useQuery({ query: EmployeeListDocument }) in its place I still get the same result. (node hangs, and page does not load)
I also tried deploying to vercel and the page will not load. the only difference is commenting/uncommenting const [{ data }] = useQuery({ query: EmployeeListDocument })

Well I think it is because as alluded to you are causing a 38 request waterfall and afaik next api functions (ssr) times out in 15 seconds 😅

Well I think it is because as alluded to you are causing a 38 request waterfall and afaik next api functions (ssr) times out in 15 seconds 😅
EDIT: hmm looking into it as essentially these should be identical queries... hard to dive into the project as there's some redundant logic too 😅 this seems to be caused by the new use-sync-external-store

Correct, they are all duplicate queries, so should it not be deduped?
redundant logic? sorry I am still new to this 😅

My best guess is currently that in prepass for concurrently running queries this line https://github.com/FormidableLabs/urql/blob/main/packages/react-urql/src/hooks/useQuery.ts#L84 should move into the scope of getSnapshot


Display Weeknumber

Bug, feature request, or proposal:
Feature Request
What is the expected behavior?
It would be great if you could display the week numbers in the calendar (month view).
What is the use-case or motivation for changing an existing behavior?
Most companies organize themselves largely over the calendar week, starting with delivery dates to all other types of appointments.
Kind regards,
Alex

I have made a fork for my Company.
You may use our repository for displaying week numbers.
just install md2 with: npm install --save https://github.com/mcl-de/md2 should do the Trick.

https://github.com/Promact/md2/pull/327


fix: sdjwt-v5 type parameter

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (951dc5e) 85.66% compared to head (ef71904) 85.66%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   85.66%   85.66%
=======================================
  Files          72       72
  Lines        8330     8330
=======================================
  Hits         7136     7136
  Misses        942      942
  Partials      252      252

Files Changed
Coverage Δ

verifiable/credential_sdjwt.go
91.40% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cotabox added to Enterprise Usage

close due to in-activity.
if you hope push this PR again, you can push it as new PR. :)


Auto bucket creation option

This adds a new option to gofakes3: WithAutoBucket, which is off by default. The idea is that instead of failing when a bucket doesn't exist, it gets automatically created before first use. The use case I have is supplying a fake s3 instance as part of a wider suite of development helpers for an environment with a lot of services that expect the existence of lots of buckets. Being able to just presume any bucket we try to use is valid saves a fairly substantial setup step. I have a couple of other minor changes that relate to this workflow, with a view to supplying a more useful Dockerfile in a later PR than the one I chucked in there a few years ago.
I've added the "ensure bucket" check to each operation that needs to trigger the autobucket logic, but it raises another interesting conundrum: we don't really try to emulate any of the atomicity guarantees that S3 has. This change potentially makes that problem worse by expanding the surface of TOCTOU that we have (I haven't thought this through fully yet, just calling out that it's on my mind), but I think some sort of opt-in atomicity support might be something I could try to tackle later?

Codecov Report

Merging #65 (c45911a) into master (532d036) will decrease coverage by 1.09%.
The diff coverage is 11.62%.

:exclamation: Current head c45911a differs from pull request most recent head a52390b. Consider uploading reports for the commit a52390b to get more accurate results

@@            Coverage Diff             @@
##           master      #65      +/-   ##
==========================================
- Coverage   68.04%   66.94%   -1.10%
==========================================
  Files          28       28
  Lines        2497     2529      +32
==========================================
- Hits         1699     1693       -6
- Misses        563      584      +21
- Partials      235      252      +17

Impacted Files
Coverage Δ

error.go
76.13% <ø> (ø)

option.go
63.63% <0.00%> (-6.37%)
:arrow_down:

gofakes3.go
63.54% <12.19%> (-4.50%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 532d036...a52390b. Read the comment docs.

@shabbyrobe it just looks like one of the tests is now failing, even though without a lot of information.

Sorry @johannesboyne, adding you to the PR wasn't intended to be a nudge, it was more meant to say "hey I think I'm actually ready now" 😆
I'll fix that test right away.

Haha ;-)! I for sure would have needed the nudging!

Test is fixed! I think the codecov diff is getting tanked a bit by adding more "assumer" tests; we don't run the assumer in the build (and I don't reckon we should - it's part of the reason why go's test framework isn't used, to avoid it getting picked up by someone running go test ./...)

Agree, it's just confused. Let's merge.


Better Gist support

To use this tool right now with a Gist you have to paste in the full raw URL - which people may find confusing.
I added a trick a while ago so URLs like https://github.com/simonw/scrape-san-mateo-fire-dispatch/blob/main/incidents.json would be automatically rewritten:

#46

Could I do something similar for Gists?

The challenge with Gists is that they can contain more than one file, and each file is shown on the same page. They do have anchor references, but these may be hard to explain to people.
Consider https://gist.github.com/simonw/7eacc70cd8b2868be0a18796cec078b9 - which contains a single JSON file.
https://gist.github.com/simonw/7eacc70cd8b2868be0a18796cec078b9#file-incidents-json is the anchor reference.
https://gist.githubusercontent.com/simonw/7eacc70cd8b2868be0a18796cec078b9/raw/e4d59d40b1e816ef8abe0ea5b9b195329531f048/incidents.json is the raw link
But... interesting twist! https://gist.githubusercontent.com/simonw/7eacc70cd8b2868be0a18796cec078b9/raw/e4d59d40b1e816ef8abe0ea5b9b195329531f048 (without the /incidents.json) also serves the same content! Maybe it serves from the "first" file in the Gist?

So at least for single file Gists having https://gist.github.com/simonw/7eacc70cd8b2868be0a18796cec078b9 rewrite to https://gist.githubusercontent.com/simonw/7eacc70cd8b2868be0a18796cec078b9/raw could work.


Unable to configure controller and webhook deployments to pull images from private registry

The pipeline and triggers controller and webhook Deployments created by the openshift-pipelines-operator include image references specific to quay.io. This is a problematic for users that must host these images in a private registry or for disconnected users. Provide a mechanism to make these image references configurable.

/kind feature
This is more or less in the roadmap (to support air-gapped installation for example) :angel:


Keep jcmd in JRE images to enable on demand flight recorder

The JRE images are purging[1] everything but the jre/bin directory. In order to enable flight recorder[2] on demand[3], jcmd should also be persisted.
[1] https://github.com/anapsix/docker-alpine-java/blob/8u172b11/8/172b11/server-jre/standard/Dockerfile#L40
[2] https://github.com/anapsix/docker-alpine-java/pull/6
[3] https://docs.oracle.com/javase/8/docs/technotes/guides/troubleshoot/tooldescr006.html

jdk images do not have it removed
could that not be used to debug things?

We have switched back to the JDK image for now, but we would like to use the JRE image because of the size.


add two university

www.glut.edu.cn
www.ncist.edu.cn

@huyaohuyao Pull request merged. Thank you!


chore: make Java breaking changes non blocking

🧭 What and Why
🎟 JIRA Ticket: -
Changes included:
It's not possible to easily debug issues like https://github.com/algolia/api-clients-automation/pull/1474 as the artifact is not generated when the CI fails, and therefore the file not accessible. This PR changes the CI check to be non blocking but to print the file if it exists

I've ported the change to https://github.com/algolia/api-clients-automation/pull/1474 to see if it works

I've ported the change to #1474 to see if it works

all good

I'm not sure that's the point of the check, it should fail if the public API changed, unless the PR title starts with feat! for example

yes it make sense but the clients are not yet GA, we can keep it and print it but changes are expected
BTW the changes I've made are additions and shouldn't be considered as breaking changes, which is weird


Avoid hardcoded ExcludedNamespaces override for serverless module

Description
Only namespace where serverless is installed should be excluded from docker registry credentials propagation ( to avoid OOM and infinite loops ).

We should not have any hardcoded lists of "system" namespaces (list1, list2)
serverless secret propagation across namespaces should exclude the namespace where serverless CR is created

Reasons
The notion od "system-namespaces" becomes a dynamic term as a set of installed modules is dynamic. It should not be hardcoded. We should avoid hardcoding that in serverless module.
Attachments
https://github.com/kyma-project/kyma/issues/8237

APP_KUBERNETES_EXCLUDED_NAMESPACES is redundant because the serverless installation namespace is already provided.
    - name: APP_KUBERNETES_BASE_NAMESPACE
      value: serverless
    - name: APP_KUBERNETES_EXCLUDED_NAMESPACES
      value: serverless


Map + InfiniteHits has weird behavior: loading next items removes previous items from map

🐛 Current behavior
I'm using react-instantsearch-hooks-web to render both a map and InifiteHits. This combination leads to weird behavior: when clicking the Show more results button, the first page results disappear from the map.
I'm not entirely sure if this could be classified as a bug, but the behavior is definitely confusing to users.
🔍 Steps to reproduce

Create a useGeoSearch connector for a map (docs)
Use InfiniteHits component.
Do a query, press show more results
See how the first x results disappear from the map

Live reproduction
no
💭 Expected behavior
the items from useGeoSearch (= useConnector) should return all items from currently shown list in InifiniteHits
Package version
"react-instantsearch-hooks-web": "6.38.3"
Operating system
macOS m1
Browser
Chrmoe
Code of Conduct

[X] I agree to follow this project's Code of Conduct

The reason this happens is because the full list of items of infiniteHits is stored inside infiniteHits itself, not somewhere global, meaning that geo search doesn't have access to that.
A workaround could be to use useGeoSearch for the boundaries etc, but still use useInfiniteHits for displaying the hits on the map, as you can still access _geoLoc.
Would that work for your use case?

That's a great idea! Works perfectly :)


Issue 155 Timeline starts and stops at relevant dates

Ended up having to modify how the timeline and filters are generated to allow for zooming.
At the moment, the data type filters for types that aren't within the zoomed in date range still show up as checkboxes. Need to decide how to handle this. If i don't show the filters for the types out of range, it may seem like the CVE doesn't have those data types, unless the user zooms out.

I'm okay with that behavior with the filters for now. Gonna go ahead and merge. Thank you!!!


Vertical scrollbar present

At least on my work laptop there's a vertical scrollbar on the whole site: seems like the overflow is only a pixel though.

It's not happening on my work desktop machine.


How safe is this?

If I'm not mistaken this counts as self botting, but how safe is this?

Discord prohibits the automation of the public API, use at your own risk.


Database seeding

New PR for:
https://github.com/meanjs/mean/pull/785

Before @ilanbiala asks whats up with package.json....  For some reason my npm --save alphabetizes but I don't see that as a bad thing...  the only thing this adds is crypto.

Cool, thanks @trainerbill - I like it.

Thanks @trainerbill this looks good.

Awesome.  @codydaig I think we should document this on the README and any other documentation we have...
Development will seed admin and user everytime.  Just grab the pass out of the console
MONGO_SEED=true grunt

Production:
MONGO_SEED=true grunt prod

Will seed the admin user one time if it does not already exist.  You have to copy the password and save it.


Quirks for Foluu Smart Thermostatic Valve Regulator

Tested using Home Assistant + ZHA
Seems to be an Zonnsmart style TV05-ZG as described here
Link to Product: Amazon.de

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5269

Relevant Lines:
7358

💛  - Coveralls

By the way you is having some extra chaster or tabs in the added code.
Copy this over the new added line then its "clean" and shall passing the tests:
            ("_TZE200_mudxchsu", "TS0601"),

It seems to be the final colon

Where can I find the support matrix?

Now all looks very nice !!!
Its in one discussion for trying getting little structure if the tuya mess of there TRVs.
https://github.com/zigpy/zigpy/discussions/653#discussioncomment-314395


Move to trunk-based development

Earlier context in this discussion
We spend a bunch of time juggling the dev and main branches which complicates some of our automation and development flows. It also means that main and dev are divergent. Which one is the authoritative history of the project? Who really knows?
The desired end state is to get rid of dev and branch everything off of main.
We want to keep building nightly builds, and have tagged release versions.
Maybe we want to unify our tag/scheduled builds?
TODO @jdangerx - refine these success criteria to be more... declarative.
### Success criteria
- [ ] push stuff to nightly namespace in cloud storage buckets + update the nightly branch when a nightly-XXXX tag is pushed
- [ ] push stuff to stable namespace in cloud storage buckets + update the stable branch when a vXXX tag is pushed
- [ ] redeploy datasette on nightly pushes
- [ ] only archive vXXX tags on Zenodo
- [ ] write an action to trigger RTD build on push to nightly/stable
- [ ] write an action to create nightly tags automatically
- [ ] force main to look like dev, then remove dev

On the archive to Zenodo on tag, I think you're talking about the data releases, but there will be 2 kinds of archives that get sent to Zenodo: software and data.  The software archive-on-tag is working now, and is only triggered on v20* tags (because GitHub releases are only triggered on v20* tags, and that's what the GitHub to Zenodo integration watches for).
By unifying the scheduled and tagged builds, do you mean that we only ever build on a schedule, and every tagged release would just be adding an additional tag to the successful nightly build that we've decided to use as a new versioned release?  So we could just package up that commit and its build outputs without needing to re-run anything?  That sounds nice and clean to me!  One issue that might come up there is that typically there's a post-build edit to the release notes that happens to close off the old section (which is changes that go into the release) and open up a new section.  But I imagine lots of other software also has this problem so there must be some way around it.

@zaneselvans with RTD, we're currently set up to include these versions on our website:

latest corresponds to main;
0stable corresponds to our new stable branch;
dev corresponds to dev;
tag builds

I think in the main-only future, we would have:

latest corresponding to main
stable corresponding to stable
tag builds

I think the nightly version in the docs wouldn't actually be helpful and instead would sow confusion about the difference between nightly and `latest.
reasons to drop `nightly` in docs build
Thinking about use cases:
- someone who is developing PUDL using the website as a reference: likely to be on the latest commit of `main` regardless of nightly build passing
- someone who is debugging a specific nightly build failure: likely to be on some `nightly-XXXX-XX-XX` tag
- someone who's using a pinned numeric version of PUDL: likely to be using that specific version
- someone who's using an installed version of PUDL pinned to some git branch like `main` - likely to be on some random commit that is some amount behind the head of `main`
The first case is the most common one, and best served by latest pointing at the latest commit on main. The second case is somewhat likely, but also not that well-served by a nightly docs build, because it's hard to tell if nightly points at nightly-XXXX-XX-XX or nightly-YYYY-YY-YY. The third case is well served by the vXXXX versions, and the fourth case is completely hopeless / best served by latest pointing at main.

I think the nightly branch could also be dropped in favor of just using the nightly tags, but I can see it being useful still.
Pros of keeping the nightly git branch:

to find the latest code that ran a successful nightly build, you just have to check out nightly.
easy to link to most recent successful output: s3://pudl.catalyst.coop/nightly/ has the latest passing build

Cons of keeping the nightly git branch:

if the update process fails between uploading the output and pushing the git ref, or if it's just taking a long time, or if people just forget to pull the latest nightly from the remote, the correspondence between output <-> code will be subtly wrong
maintaining nightly branch from within Docker seems like a pain in the butt

Pros of dropping the nightly git branch:

avoid most subtle wrong states of above - nightly-XXXX-XX-XX output will correspond to the nightly-XXXX-XX-XX code, unless we failed in the middle of our S3 upload.
easy to check out the code associated with a specific nightly build for debugging purposes
don't have to deal with maintaining the nightly branch from within the docker container

Cons of dropping nightly git branch:

harder to link to most recent successful output: s3://pudl.catalyst.coop/nightly/XXXX-XX-XX might have the latest passing build, but users would have to look at a list of what's in nightly/ and assess what the latest date there is.

WDYT about dropping nightly in docs/git/both @zaneselvans ? I'm personally somewhat in favor of dropping nightly from the docs, but pretty on-the-fence for git. Maybe slightly pro dropping from git too, if I had to pick.

main: the bleeding edge. May be broken. Has no outputs associated with it. main is only really interesting in a development context -- it's what we're all branching off of to make new code. If we were going to hide something from the docs, I think I would be most inclined for it to be this.  The nightly builds are kind of our final CI test, and we don't really want the public working with / referring to that until we know the builds pass. Generally this will only be a day or two ahead of nightly.
nightly: the most recent known-to-work code. Has ephemeral outputs associated with it. nightly is useful for folks like RMI or other who prioritize freshness over long-term guarantees of accessibility. If we merge in a PR addressing e.g. RMI's needs and it takes a month or more for those changes to show up in stable, I think they will often prefer to access the nightly outputs, at least for the purpose of their own testing and development in the interim. And I think if the data is going to be out there in use by people, there should probably be publicly visible docs that go along with it.  I would be inclined to connect nightly to latest as in "latest thing that you should probably be looking at, if you're not doing development."  Dunno.  We could make nightly/latest the default landing page for RTD, but also have main there if someone wants to see it for development.
stable: the most recent known-to-work code with persistent outputs available (via S3, GCS, Zenodo, etc.). If we get to where we're cutting monthly releases, I think that this is probably what we want to point most users at.  Though I suspect that there will still be breaking changes between versions due to schema drift. So maybe we actually want most users to rely on a specific version if they need stuff to not go down.
v202Y.MM.DD: a particular past tagged stable release, so folks can pin and know nothing will change. We should definitely persist these docs builds to annotate the persistent outputs they're associated with.

Ah! We could point latest at nightly instead of main, in RTD settings. That seems like the nicest way to do this. What that means is, for Cats, the documentation will potentially be a couple commits out of date... but I think that's fine. Since you're probably working on changing some documented behavior anyways, and Cats are best equipped to Just Look in the Damn Code for their answers anyways.

I think that would also imply that we want the AWS outputs to have s3://pudl.catalyst.coop/latest/pudl.sqlite instead of /nightly/pudl.sqlite - and maybe we want the nightly branch to be named latest instead? Just to make everything consistent?

Hmm.  I really like nightly because it communicates the frequency with which it's being potentially updated whereas latest could be three months ago without additional context (and nightly updates are very rare among the people that we're trying to serve).  Can we not change the RTD naming?  Or if we can't get ride of their latest have an identical alias that's nightly?

It looks like we can set the default version to nightly under Advanced Settings, and let latest point at the default branch main which is the normal RTD behavior.

Works for me!
Zane Selvans @.***>于2023年12月20日 周三下午6:09写道：

It looks like we can set the default version to nightly under Advanced
Settings, and let latest point at the default branch main which is the
normal RTD behavior.
image.png (view on web)
https://github.com/catalyst-cooperative/pudl/assets/596279/5c26b06a-1250-4d05-9fdf-b7d3cca2ef21
—
Reply to this email directly, view it on GitHub
https://github.com/catalyst-cooperative/pudl/issues/3140#issuecomment-1865259640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATBKMWMOWEP6K7HUMHF3PLYKNV2NAVCNFSM6AAAAABANIPUB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRVGI2TSNRUGA
.
You are receiving this because you were assigned.Message ID:
@.***>

OK, I went and fiddled with RTD settings. I think that if the nightly build works and pushes nightly branch, RTD should make a nightly version that will appear on the website. Once that docs build exists we can switch the default to nightly, move latest to main, and hide dev from view.

I'm gonna give the build and all the new machinery like a 10% chance of succeeding. 🤞🏼

I went ahead and updated the RTD configuration, so it is now building and serving the main (latest), nightly, and stable branches, with nightly as the default if you don't specify a version.


eslint: add eslint-plugin-import plugin

I think I wanted this mostly because of the "you're importing a file that doesn't exist" warnings as well as the "you're importing a named export that doesn't exist" ones.  It's nice to catch that when writing code, specially with the vscode eslint integration.
https://github.com/benmosher/eslint-plugin-import has the full list of rules
I considered https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/newline-after-import.md but that makes things look weird like:
import chai from 'chai'; // wants a newline after this, but it's nice to group?
const { assert } = chai;

I also considered https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-mutable-exports.md, but I need to figure out what's going on with export let gPopupText; first.


Property-test the mempool with ledger tables

Write state machine tests (using either QC dynamic or QC state-machine) to exercise the mempool API, including concurrent access to it (checked using prop_parallel in QC state-machine).
For UTxO HD, we need the mempool API to be defined and relatively stable before starting this task (see https://github.com/input-output-hk/ouroboros-network/issues/4035), however, we could start writing the tests for the baseline version.
To test the mempool we will need to use a test-block. At the moment there are different test blocks in the system. For simplicity we could create an additional test block. @Jasagredo worked on the unification of test blocks (see #3965) however the task involves an enormous amount of changes non-related to UTxO HD, therefore we currently prefer to create a new type of test block.

Currently blocked by #4161

This only needs cleanup and should be ready to review


[PackageDescription][SR-3858] Error out for dup target

Fix SR-3858: No error if a target is defined twice in manifest
Dependencies:

[x] PR #1177

@aciidb0mb3r Done with changes, please review.

@aciidb0mb3r Done with changes, please review.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@shahmishal Can you check why @bhargavg is unable to trigger CI? He has commit access.

I'm not sure if the failure is related to this path:
output: error: unableToLoadBundle("/var/folders/_8/79jmzf2142z2xydc_01btlx00000gn/T/Miscellaneous_SwiftPMXCTestHelper.Mxu2HI/Miscellaneous_SwiftPMXCTestHelper/.build/debug/SwiftPMXCTestHelperPackageTests.xctest")

@swift-ci please smoke test OS X

Looks like this failure is related to SR-4876

@swift-ci please smoke test OS X

@swift-ci please smoke test OS X


terra-date-time-picker date and time fields not reflecting updated value

Bug Report
Description
Attempting to update the terra-date-time-picker value via a button does not get reflected in the fields.
Steps to Reproduce
Added code sandbox to display issue:

Click on 'Reset' Button
Values in date time fields do not get updated.

https://codesandbox.io/s/trusting-poincare-oxopd?file=/src/App.js
Additional Context / Screenshots
Expected Behavior
Value in date and time fields to be updated to reflect latest value in state
Possible Solution
Environment
Chrome/IE
@ Mentions

@leducquan, date-time-picker is an uncontrolled component. Therefore it isn't supposed to update programmatically.
You can go through issue #1000 for more information.

Closing as a duplicate


Recognize format "ASCII"

Reading a file that uses format="ASCII" currently results in the error
XML(Deserialization(Custom("unknown variant `ASCII`, expected one of `appended`, `binary`, `ascii`"))).
Given the fact that the vtk specification only uses format="ascii", this technically is correct but also accepting files with format="ASCII" would be a minor change, which would make the crate more flexible. Paraview also accepts these files.

Nice catch, thank you for the issue!

Fixed by #53


Support syntax highlighting for OSS build (Arch linux)

First of all, let me mention my appreciation for the work you are doing with this extension.
I do understand that you may only be supporting the microsoft build of vscode. But, I want to point out that syntax highlighting does not seem to work for notebooks (apart from python). Below is how an notebook rinning the R kernel looks like in the code - oss build of arch linux:

As you can see, there is no highlighting at all. Here the equivalent with vscode:

(These both are in the 1.53.1 build, but the problem appeared in every previous build.)
It appears that the extensions folder of the code - oss build may not be parsed correctly for syntax highlighting? I can give you any info you need in case you can help with this issue.

Thanks for the bug. Yes we don't really support the OSS build. It looks like you're running an older version of it though. The newer version should have notebooks that use the new VS code notebook editor. Something that looks like so:

@rchiodo I understand you do not support these builds, but just a quick question: I am actually using 1.53.1 of code, and latest jupyter notebook extension. I was under the impression you can only get the native notebooks in insiders versions. Can one also enable them in the "stable" version? I could not find a way to do so...

Can one also enable them in the "stable" version? I could not find a way to do so...

No sorry not at the moment.

@rchiodo ok, many thanks. I really hope native notebooks get pushed soon to stable. I cannot find any roadmap on this.


Light sensor and IR.

The light sensor uses a camera to take a picture, it calculates the
average color of the image and uses the formula Luminance = 0.2126Red+
0.7152Green + 0.0722*Blue. Then the console outputs the value which
has a range 0-1023 (0 being the darkest and 1023 the brightest) The IR
sensor does the same as the light sensor, but the sensor points and
simulates a sensor that calculates the reflectiveness of the lower
surface. The image size is much smaller as well. The buzzer has been
implemented but commented out. Future development may include a
cross-platform way of doing this.
The light sensor uses a camera to take a picture, it calculates the
average color of the image and uses the formula Luminance = 0.2126Red+
0.7152Green + 0.0722*Blue. Then the console outputs the value which
has a range 0-1023 (0 being the darkest and 1023 the brightest).
The buzzer has been implemented but commented out. Future development
may include a cross-platform way of doing this.

@scanese merged, thsnks!


Value method in V2 not present

Value method in V2
I am switching from GORM V1 to V2. When get a user record from the DB I used the Value method in order to return the value. However, this method is not available in V2.
My code looked like this (in combination with Fiber):
func UserGetByID(c *fiber.Ctx) error {
	id := c.Params("id")
	db := database.DBConn

	user := entities.User{}
	record := db.Preload("GeneralData").Find(&user, id)

	if record.Error != nil {
		return c.Status(500).SendString(record.Error.Error())
	}

      return c.JSON(record.Value)
}

What can I do to get this functionality in V2?

Just use the user here.

I think this pattern does not work for cases like these:
func UserCreate(c *fiber.Ctx) error {
	db := database.DBConn

	user := &entities.User{}
	if err := c.BodyParser(user); err != nil {
		return c.Status(503).SendString(err.Error())
	}

	// Try to save the user in DB
	record := db.Create(&user)

	if record.Error != nil {
		return c.Status(404).SendString("User can not be saved in DB!")
	}
   return c.JSON(record.Value)
}

Why was the Value method removed? What can be used instead?

the Value is the value you passed in, here it is the user, if you don't want to use it, use the result.Statement.Dest

Okay, thank you!


Add Debt Token exists assertion

This PR introduces the following changes:

Added invariant for asserting debt token exists
Refactored so Assertions constructor doesn't require web3
Miscellaneous cleanup

LGTM!
Ideally, in the future, this could be split into two separate PRs. One removing web3. The other adding the invariant.


Allow to full text search in all of local history

would it be possible add an option to full text search in all local history entries (a new feature in v1.66)?

If you right click on an entry you can select to open its location on disk and could trigger a fulltext search over the parent folder.

If you right click on an entry you can select to open its location on disk and could trigger a fulltext search over the parent folder.

i mean something like Search across files - it would be a tedious process to open dozens of file snapshots to find what we are looking for

@pskink sure, the workaround is to open the local history folder as a workspace in VSCode and just fulltext search?

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Is it working?

A test:
Model         TIME(sec) PACKETS SAMPLES DDOS% ACC    ERR    F1     PPV    TPR    FPR    TNR    FNR    Data Source SYN2020-LUCID     0.022 0001761 0000352 0.497 0.9972 0.0981 0.9971 0.9943 1.0000 0.0056 0.9944 0.0000 10t-10n-SYN2020-dataset-test.hdf5
It's not able to detect a slowloris attack. The accuracy is 99%..... I'm using a newer tshark version than recommended. Oops my interface would be enp4s0

Something happened while slowloris attack:
[sudo] Passwort für france1:
Prediction on network traffic from:  enp4s0
2022-03-05 21:01:17.062500: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN)to use the following CPU instructions in performance-critical operations:  SSE4.1 SSE4.2 AVX AVX2 FMA
To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags.
2022-03-05 21:01:17.080559: I tensorflow/core/platform/profile_utils/cpu_utils.cc:104] CPU Frequency:<PHONE_NUMBER> Hz
2022-03-05 21:01:17.080784: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x562150de9260 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2022-03-05 21:01:17.080846: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
/home/france1/anaconda3/envs/python38/lib/python3.8/site-packages/sklearn/metrics/_classification.py:1318: UndefinedMetricWarning: Precision is ill-defined and being set to 0.0 due to no predicted samples. Use `zero_division` parameter to control this behavior.
  _warn_prf(average, modifier, msg_start, len(result))
/home/france1/anaconda3/envs/python38/lib/python3.8/site-packages/sklearn/metrics/_classification.py:1580: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 due to no true nor predicted samples. Use `zero_division` parameter to control this behavior.
  _warn_prf(average, "true nor predicted", "F-score is", len(true_sum))
lucid_cnn.py:412: RuntimeWarning: invalid value encountered in long_scalars
  fnr = fn / (fn + tp)
lucid_cnn.py:413: RuntimeWarning: invalid value encountered in long_scalars
  tpr = tp / (tp + fn)
Model         TIME(sec) PACKETS SAMPLES DDOS% ACC    ERR    F1     PPV    TPR    FPR    TNR    FNR    Data Source
SYN2020-LUCID     0.110 0000817 0000117 0.000 1.0000 0.0000 0.0000 0.0000 00nan 0.0000 1.0000 00nan enp4s0

/home/france1/anaconda3/envs/python38/lib/python3.8/site-packages/sklearn/metrics/_classification.py:1318: UndefinedMetricWarning: Precision is ill-defined and being set to 0.0 due to no predicted samples. Use `zero_division` parameter to control this behavior.
  _warn_prf(average, modifier, msg_start, len(result))
/home/france1/anaconda3/envs/python38/lib/python3.8/site-packages/sklearn/metrics/_classification.py:1580: UndefinedMetricWarning: F-score is ill-defined and being set to 0.0 due to no true nor predicted samples. Use `zero_division` parameter to control this behavior.
  _warn_prf(average, "true nor predicted", "F-score is", len(true_sum))
lucid_cnn.py:412: RuntimeWarning: invalid value encountered in long_scalars
  fnr = fn / (fn + tp)
lucid_cnn.py:413: RuntimeWarning: invalid value encountered in long_scalars
  tpr = tp / (tp + fn)
Model         TIME(sec) PACKETS SAMPLES DDOS% ACC    ERR    F1     PPV    TPR    FPR    TNR    FNR    Data Source
SYN2020-LUCID     0.025 0001896 0000209 0.000 1.0000 0.0000 0.0000 0.0000 00nan 0.0000 1.0000 00nan enp4s0

But.. What's that.

0.166 is the ddos percentage while a slowloris attack is running. Now I begin to understand but it doesn't seem to detect. What's the problem with newer tshark versions?

Hello,
sorry for the late reply. LUCID has been design as a DDoS detection system, it does not implement any packet filtering mechanisms. In your case, I would suggest to take the list of malicious IP addresses given by LUCID and used them to configure IPTABLES. You can use the "keys" tuple at line 377 in lucid_cnn.py to obtain the list of malicious source addresses.
Hope this helps.

Ok I got it. Now my problem is that this is not only monitoring incoming traffic but outgoing traffic so the server IP is maked as an attacker. I might be able to exclude that...
Another problem is the size of that file. It's huge instead of only one IP per print() # I used print to see what's in keys.
I'm going to try to implement something..

I ran into a problem pretty quick...
f=open("example.txt", "r")
list=f.read()

for i in range(len(list)):
    print(list[i])

print()
print()
print(list[1])
print(list[2])

This prints every single character that's in example.txt (the keys file)
Isn't keys an array with tuples in it? I thought I could get the length of the array and then go through every element of the array (so every tuple that's in it) and then get the attacker IP, put the IP into a wordlist or a new array. To prevent false positives I'd have to count in how many tuples the attacker IP is and trigger at like about 50 times.

https://stackoverflow.com/questions/71873752/iterating-through-a-python-array-does-not-work/71874037#71874037
Ok closing now.


Nocode, no license

Since there's no code, you need no license and anything else at all.

I believe what you are proposing would make this creative work fall under the domain of an implied license. Oh, yeah, and the IANAL disclaimer bit, so I could be totally wrong.

I believe that John Cage's 4'33" is copyrighted.


fix migration:create

Hi,
I found a small issue in migration create command. this will fix :)

Guess I glanced over the previous pull request too fast. Thanks for catching these.


HTML entities not rendered correctly in h1 headlines

In post titles, HTML entities like & or > and so on are not rendered as & or < and so on.

I've updated to the latest Grav version, which is when I noticed the behaviour, but I didn't notice at what version exactly it appeared.

I've noticed that XML entities such as ' and & are also not rendered, but again just in titles / headings.  They render as expected in the body of a post.

Thanks, that's great information.  Solved the issue.


[WIP] Add some JS tests and fix some JS dependencies

Still need to make these run in Travis

Codecov Report

Merging #66 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #66   +/-   ##
=======================================
  Coverage   77.21%   77.21%
=======================================
  Files          45       45
  Lines        2611     2611
=======================================
  Hits         2016     2016
  Misses        595      595

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c2d4d6f...4a81433. Read the comment docs.


[C++] Utility method to ensure an array object meetings an alignment requirement

This would look something like:
EnsureAligned(Buffer|Array|ChunkedArray|RecordBatch|Table, int minimum_alignment, MemoryPool* memory_pool);
It would fail if MemoryPool's alignment < minimum_alignment
It would iterate through each buffer of the object, if the object is not aligned properly, it would reallocate and copy the buffer (using memory_pool)
It would return a new object where every buffer is guaranteed to meet the alignment requirements.
Reporter: Weston Pace / @westonpace
Assignee: Sanjiban Sengupta / @sanjibansg
PRs and other links:

GitHub Pull Request #14758

Note: This issue was originally created as ARROW-18119. Please see the migration documentation for further details.

@westonpace, @sanjibansg: we are interested in this PR getting merged. cc @icexelloss.

Thanks @westonpace !


problems with UIManager.measure()

Hi, In addition to ex-navigator I am using another component from another library that positions itself based on the results of the measure fn, as described here: https://facebook.github.io/react-native/docs/nativemethodsmixin.html
unfortunately for the same navigator views that fn returns different results depending on whether it is the initial route or whether it was pushed (pageX prop returned from measure() is 0 or the same as screen width ). not sure if there is a better method to use for dimensions or some other trick to using ex-navigator to get consistent results?
thanks

I would expect the dimensions to be measured the same everywhere but the absolute position of the component of course will differ if it's sliding in from the right.

hm, ok. so it somehow it needs to get dimensions post-slide

Generally speaking, relying on pageX isn't what you want. Better to find the local X coordinate instead of the absolute one for robustness.

ok thanks


Call to users: looking for streams with MPE

Dear TSDuck users,
I am looking for real-life captured transport streams with MPE streams. It possible, I would appreciate encapsulated TS inside UDP, being encapsulated inside MPE streams, inside TS.
If you have such streams, please post them (or link to them) here.
Recent commits of TSDuck have added detailed MPE signalisation and a new plugin named mpe which extracts MPE streams (saved on files or forwarded as UDP for the moment). To add more interesting features on this plugin, I need real test streams.
Thank you in advance for your cooperation.

Is this what you're looking for?
https://mega.nz/#!FkRxiQAD!HmQVAD0GpaWktt4_Qbj5K_MmF56vqkuF9wBO4uUfI2E
https://mega.nz/#!I5QViLRK!_nTex16w-3oOftHbKt4wyfkX2ymtksbRJStGBdv2iag
It's a 1 minute from Tricolor OTT at 36E and some C-band stream, probably from 45W or close to it. I didn't have a chance to try MPE plugin yet so I'm not sure what would be the expected output from this. In the Tricolor OTT there are clearly video streams in it but I have no idea if there's any way to extract those properly. Please let me know if the files recorded are useful in any way.

Hi.
Thank you. I am away this week and will download the file next week. I heard that Tricolor was using MPE to feed ABR streams for local pseudo-OTT redistribution. This is probably that stream. I will let you know.

Hi Jan,
Thanks for the files. I just downloaded them.
The first file is clearly an MPE TS with correct syntax, correct INT, etc. I do not know yet how to interpret the content of each multicast stream. Using plugin mpe, I extracted the raw UDP content of one stream and tried to extract a valid TS from it.
tsp -I file 36.0E_12168.835_V_27500.ts -P mpe -d <IP_ADDRESS> -o <IP_ADDRESS>.udp -O drop
tsresync <IP_ADDRESS>.udp -c -m $((3*188)) -o <IP_ADDRESS>.ts

The strange usage of tsresync is a tweak. It takes a binary file with TS packets in the middle of various types of encapsulations and tries to extract as many valid TS packets as it can. This is a bit rude but it works on Wireshark capture files for instance (capture of an IP-TV UDP multicast stream). Here, I get a more or less valid SPTS file with a clearly identified service, PAT, PMT. But VLC plays it as garbage. So, I need to investigate a bit more.
The second file is not MPE, it is an RCS stream (Return Channel Satellite) as defined in ETSI EN 301 790. I have never investigated that kind of stream and I am not familiar with this standard. I keep this file for reference and I will probably get back to it later.
Thanks again.

In the MPE stream, using a new option --sync-layout in plugin mpe, we can display the layout of the 0x47 bytes in the UDP payload. The number between two [47] is the number of bytes between the two 0x47.
$ tsp -I file 36.0E_12168.835_V_27500.ts -P mpe -d <IP_ADDRESS> --sync-layout -O drop
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  101 [47] 78 [47] 187 [47] 187 [47] 187 [47] 187 [47] 187 [47] 187 [47] 57 [47] 53 [47] 47
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  33 [47] 14 [47] 187 [47] 40 [47] 146 [47] 187 [47] 125 [47] 61 [47] 187 [47] 187 [47] 187 [47] 103
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  104 [47] 166 [47] 20 [47] 133 [47] 53 [47] 187 [47] 60 [47] 40 [47] 85 [47] 187 [47] 182 [47] 4 [47] 187 [47] 47
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  160 [47] 187 [47] 163 [47] 10 [47] 12 [47] 136 [47] 42 [47] 7 [47] 64 [47] 122 [47] 187 [47] 187 [47] 179
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  28 [47] 57 [47] 60 [47] 40 [47] 27 [47] 61 [47] 77 [47] 47 [47] 187 [47] 153 [47] 33 [47] 187 [47] 187 [47] 187 [47] 123
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  84 [47] 108 [47] 78 [47] 81 [47] 83 [47] 21 [47] 118 [47] 68 [47] 153 [47] 33 [47] 187 [47] 187 [47] 187 [47] 67
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  140 [47] 187 [47] 145 [47] 41 [47] 126 [47] 60 [47] 25 [47] 90 [47] 70 [47] 58 [47] 128 [47] 129 [47] 57 [47] 187 [47] 11
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  196 [47] 28 [47] 158 [47] 77 [47] 58 [47] 50 [47] 54 [47] 55 [47] 76 [47] 187 [47] 187 [47] 187 [47] 143
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  64 [47] 187 [47] 187 [47] 5 [47] 181 [47] 187 [47] 29 [47] 40 [47] 116 [47] 187 [47] 127 [47] 59 [47] 87
* mpe: PID 0x07D2 (2002), src: <IP_ADDRESS>:5050, dest: <IP_ADDRESS>:5050 (01:00:5E:1E:00:14), 1468 bytes, fragment: 0x0000
  120 [47] 187 [47] 187 [47] 5 [47] 181 [47] 118 [47] 68 [47] 126 [47] 60 [47] 160 [47] 26 [47] 22 [47] 92 [47] 22 [47] 48 [47] 31
...

We can see the 187 values indicating packets without 0x47 in the middle. Otherwise, by grouping adjacent values, we can identify 188-bytes packets with a 0x47 in the middle.
But the global layout is very different from an IP-TV stream with a fixed size prefix and where the last TS packet always ends exactly at the end of the UDP payload.

Googling around, I found this topic: http://www.sat-universe.com/showthread.php?t=301973
which leads to http://www.mediafire.com/file/d9q3w3ucy4npe9x/OTTextractor(2).rar and with that, working video files are extracted from the MPE stream... so it can be done, somehow :)

Thanks for the link, I will have a look

I looked deeper inside the decapsulated UDP streams and found that the content format is Apple HLS. Apparently, the UDP packets contain a 20-byte header (proprietary?) followed by payload. The concatenated payloads form an original HTTP response stream, with HTTP headers, HLS manifests and HLS segments (which are in fact TS files).
I originally spotted the TS packets from the HLS segments but missed the HTTP headers and HLS manifests since they represent only a very small part of the data.
To detect missing DSM-CC sections/ MPE datagrams, a continuity counter seems to be present in the header.
The danger of that stack of protocols (TS -> sections -> DSM-CC -> MPE -> UDP -> HTTP -> HLS -> back to TS) is the impact of a missing TS packet in the satellite stream. Instead of losing one video TS packet (limited impact),  you loose one DSM-CC section, meaning several effective TS packets plus adjacent overlapping TS packets, not including the potential damages on the HLS structure. Add the fact that the reception takes place at a high latitude (Russia). It really looks like looking for trouble.

here's another stream but I'm not sure if it's really the kind of MPE that tsduck handles... looks like DStv service for mobile phones, recorded from 68E 12610H
https://mega.nz/#!clph1TzD!n-YCATnLV8vYRZLez2mhv6WRAAJouRSHaR2cnDQ3kkg

Hi Jan,
Thanks for the stream. TSDuck can extract UDP packets from this stream. The MPE structure and the INT seem correct. Currently, I have no idea of the format of the data inside the UDP datagrams.
Looking at the MPE stream for the service named Discovery for instance:
tsp -I file 68E_12610.912_H_6710.ts -P mpe --pid 2107 --log --dump-udp -O drop

The datagrams do not contain TS packets, with any kind of encapsulation. All datagrams start with either 80 60, 80 E0 or 80 E1. There are some repetitive patterns. Any idea of the format?

no idea, the only mention of something that could be this related to is DVB-H OMA/BCAST (https://www.naijatechguide.com/2008/05/nigeria-dstv-mobile-from-mtn.html)

Thanks for your efforts in searching, capturing and providing MPE streams.
Closing this topic now.


No module named open3d

ImportError: No module named open3d
[calib_camera_pose-2] process has died [pid 8784, exit code 1, cmd /home/div/6D_pose_ws/src/3D-Scanner-by-Baxter/src_main/calib_camera_pose/calib_camera_pose.py __name:=calib_camera_pose __log:=/home/div/.ros/log/c26552a8-bd93-11e9-926e-9c305bc8fc79/calib_camera_pose-2.log].
I have faced this issue. I tried installing pip install open3d-python too.. Also I found that, .log file is not present in .ros file.. Could you plz help me in this

@ramyagopinathpsg

About open3d, try this: $ pip install --user open3d-python
See this page: http://www.open3d.org/docs/release/getting_started.html#id2
About .log, I'm not sure what error you are talking about


Passing Parameter

I wonder how we can pass parameter to the function we want to daemonize.

You should do this by integrating daemonize into your project. Your application should import daemonize, accept all the parameters that you want to pass, and then daemonize itself.


Plausible account

Hi, apologies if this is not the right way to reach out to the maintainers.
I'm the developer behind Plausible Analytics and I saw that you're looking to integrate it to erlang.org. We rely on Erlang ourselves and would like to support the community by providing a free account for this project.
If you're interested, please write to me<EMAIL_ADDRESS>

Hello! We may very well take you up on that offer! The only reason I hesitate is that Netlify (where we host the website) provides statistics (for a price) that we possibly could use to improve the search results on https://erlang.org/doc/search and I've yet to decide if that is something we would like or not.

Sure, no pressure. Pick whatever works best for you. Just in case you do want to make use of Plausible, I'm available on that email address. Cheers!
You can close the issue if you want as well. Just wanted to let you know :)


Flow does not match on internal

Created two flows:
1 | internal(in_port=1) -> eth(src=ff:ff:ff:ff:ff:ff), output(2);
0 | * -> output(2);
Ran the simulation ...
Action list only shows output(2)

issue seems to be with matching on internal


Added parenthesis to content type of request body

Added parenthesis to content type of request body to be consistent with content type rendering of response model
This fixes issue #14

appreciate your help on this


Tweak 22F4 for ClimaRad

Compare to 22F2 modes. These new modes could also be applied to the existing packets.

This has opened a can of worms - I think easier if I do it, based upon your packet logs.
Please have a look at the 22F4 parser in the latest master, and submit another PR based upon that.


i18n(fr): Updating install/auto.mdx from #7846

Description (required)
Updating install/auto.mdx from #7846

Related issues & labels (optional)

Closes #
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note
Locale

src/content/docs/fr/install/auto.mdx
Localization changed, will be marked as complete.
fr

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Add abstract reader interface

This is preparation work for the Parquet reader. It moves some of the DWRF reader classes into dwio/common for shared usage and introduces abstract reader classes.

@mbasmanova I rebased the patch but didn't remove new dependencies on dwrf introduced in HiveConnector. This patch already looks big enough and I'd like to look at the new deps separately.
From the first glance, [Cached]BufferedInput has no DWRF specific code and can be moved to dwio::common if we want to remove all dwrf deps in HiveConnector. But these classes also have a bunch of dependencies in dwrf namespace, so the amount of refactoring will be enough for a separate PR :)

@ienkovich Make sense, Ilya. Thank you. Let us merge this one.

Hi @ienkovich ,
I am working on merging this pull request with internal facebook codebase. There are some internal tests which I need to look into and work on before this can be merged.
I will keep you updated here
Thanks.

I am working on merging this pull request with internal facebook codebase. There are some internal tests which I need to look into and work on before this can be merged.

Please note, that with these changes you would need to explicitly register DWRF reader in those internal tests if this reader is used.

@ienkovich Ilya, with @zzhao0's help we were able to merge this change.


chore: remove tests for deprecated SnapshotEnvironmentBinding controller

Description
As the SEB controller is going to be deprecated and removed by SPI team (see https://issues.redhat.com/browse/SVPI-728), we need to cleanup tests which are testing it
Issue ticket number and link
https://issues.redhat.com/browse/SVPI-763
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/retest

/retest

/retest

/retest

/retest

/retest

the failures in the CI job are not related to changes in this PR
giving the fact that the e2e CI job already passed for this PR, I think it's ok to merge it


Ansible: Update ovs and build

Bump OVS version to 2.10 - needed for Ubuntu 18.04.
Fix hang when building debs.

CC: @alinbalutoiu

I just deployed a cluster with these patches active and was able to run a pods on my Linux node, but my CoreDNS pods are not deploying and keep crashing with errors, I am uncertain if that is a result from these patches or some other problem.
https://gist.github.com/lanoxx/49df858803687ecb0cd76766c4d753c6

In the end I reverted the patches. I dont think these patches are needed for 18.04. I was able to get a working cluster without these patches.


0063-display-name-parameter

DisplayType Deprecated via this proposal
Add DisplayType via this proposal

Resolves #32


Implement PROVIDED_BLOCKBUILDER return place convention for scalar function

Currently the only return place convention for scalar function is STACK, and the callee will append the results value on stack into the result BlockBuilder (for out-most function call) or use it to invoke other functions (for inner/nested function call like f(g(x))).
For functions returns Slice and Block, this return place convention usually result in copying the data twice -- once generate the data, once copy the data into the output BlockBuilder.
This commit implements PROVIDED_BLOCK return place convention to allow scalar function implementation choice to directly write to the desired place. Similar to the BLOCK_POSITION null convention, a implementation choice used default STACK return place convention must be implemented. Besides STACK return place convention, the developer of the scalar function can choose to provide an additional implementation choice with PROVIDED_BLOCK return place convention.
In the future, an invocation adapter should be able to automatically adapt between different calling conventions (null convention and return place convention) when feasible.

Approved by @haozhun at https://github.com/prestodb/presto/pull/12166

there are no plans to merge this.
cc @martint @dain


Adding k8s plugin support to vscode

Description:
Added the kubernetes plugin to vscode, installed script to configure said plugin on start, added DescribeCluster capability to the iam role
Issue Reference URL
https://github.com/awslabs/aws-eks-data-maker/issues/

Do not change content below. Mark applicable check boxes only.
Thank you for submitting a contribution to AWS Orbit Workbench.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a ISSUE associated with this PR?
[ ] Does your PR title start with ISSUE-XXXX where XXXX is the issue number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[ ] Has your PR been rebased against the latest commit within the target branch (typically 'main')?
[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] Have you ensured that the full suite of tests is executed?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under Apache License 2.0?

static check is failing


Support SomeStruct::new() function call syntax

What is wrong?
Type-associated functions can currently be called by using a . but not a ::. For example:
struct Rectangle:
  h: u256
  w: u256
  pub fn square(x: u256) -> Rectangle:
    return Rectangle(h=x, w=x)
  pub fn area(self) -> u256:
    return self.h * self.w

fn do_square_things():
  let s: Rectangle = Rectangle::square(10)
  assert s.area() == 100

The Rectangle::square(10) call above panics with something like

thread 'struct_fn' panicked at 'not yet implemented: cannot access items in types yet', crates/analyzer/src/namespace/items.rs:106:30

changing it to Rectangle.square(10) works. This syntax should be disabled, and :: should be fixed.
How can it be fixed
:technologist:

Whoops, duplicate of #241


feat: introduce pb values in python + wrap/unwrap

this allows python code to use autokitteh values. this also introduces methods to wrap and unwrap them.

In general looks OK, but many small changes. Also, I don't see where this is going to get used. Is this another PR?

Will be done in another PR.


can't be found PART_EditableTextBox Template

PART_EditableTextBox template cannot be found.
VisualTreeHelper=>GetChildrenCount() returns 0!, if the combobox component is in the ChildWindow.

@ugrgnc That's not enough information! What are you try to do?

Hello,
I use SimpleChildWindow for my project. in the ChildWindow I have a Combobox.  I want to get "PART_EditableTextBox" template of Combobox with VisualTreeHelper class. but It cannot be found!
if the Combobox  ist in the MetroWindow or Window, it can be found.

TEST1
TEST2
TEST3
TEST4
TEST5

using System.Windows;
using System.Windows.Controls;
namespace Contacts.UI.Helper
{
public static class ComboBoxCharacterCasingBehavior
{
[AttachedPropertyBrowsableForType(typeof(ComboBox))]
public static CharacterCasing GetCharacterCasing(ComboBox comboBox)
{
return (CharacterCasing)comboBox.GetValue(CharacterCasingProperty);
}
    public static void SetCharacterCasing(ComboBox comboBox, CharacterCasing value)
    {
        comboBox.SetValue(CharacterCasingProperty, value);
    }

    public static readonly DependencyProperty CharacterCasingProperty = DependencyProperty.RegisterAttached("CharacterCasing", typeof(CharacterCasing), typeof(ComboBoxCharacterCasingBehavior), new UIPropertyMetadata(CharacterCasing.Normal, OnCharacterCasingChanged));

    private static void OnCharacterCasingChanged(DependencyObject o, DependencyPropertyChangedEventArgs e)
    {
        if (!(o is ComboBox comboBox))
            return;

        if (comboBox.IsLoaded)
        {
            ApplyCharacterCasing(comboBox);
        }
        else
        {
            comboBox.Loaded -= OnLoaded;
            comboBox.Loaded += OnLoaded;
        }
    }

    private static void OnLoaded(object sender, RoutedEventArgs e)
    {
        if (!(sender is ComboBox comboBox))
            return;

        ApplyCharacterCasing(comboBox);
        comboBox.Loaded -= OnLoaded;
    }

    private static void ApplyCharacterCasing(ComboBox comboBox)
    {
        var textbox1 = UIHelper.FindChild<TextBox>(comboBox, "PART_EditableTextBox");
        var textBo2 = comboBox.Template.FindName("PART_EditableTextBox", comboBox) as TextBox;
        if (textBo2 != null)
        {
            textBo2.CharacterCasing = GetCharacterCasing(comboBox);
        }
    }
}

}

@ugrgnc When do you try to find the inner TextBox? And why?

I want to use Combobox in Editable Mode to search, because of that I want to set some property of the Textbox like "MaxLength", "CharacterCasing". I use a Behavior for Combobox.  I try to get Template with VisualTreeHelper and FindName function. but I did not succeed. it returns always null.

@ugrgnc I think I can't help you enough without a sample app including your behavior.

@punker76
Sample application:
SimpleChildWindowTest.zip


nsc-events-nestjs_7_114_enable-nestjs-auto-assign-issues

Resolves #114
Once merged, this should auto-assign developers to the issues they create for this repo.

Just as added to the belinda project this feature will also work well with NSC events. Looks good


Send welcome mail on creation

Waiting for mail to work!

@joscdk we need to send mails via SMTP is that fine with you?
I created a small test acc with mailgun and it was np to setup. Do you see any conflict?


Add rsk-federated-sidechains-and-powpeg review to bitcoin-explained

This PR adds rsk-federated-sidechains-and-powpeg transcript review to the bitcoin-explained directory.

Hi @kouloumos, thank you for your feedback. I corrected the broken sentences.
Hope it can be merged now.

Hopefully we will see more transcripts from you in the future @jinformatique, thank you!

Currently, there are no more transcripts awaiting review. I’ll watch the repo to keep an eye for new ones.

Currently, there are no more transcripts awaiting review. I’ll watch the repo to keep an eye for new ones.

If you're looking for additional ways to contribute, consider suggesting sources for transcription. Curators are vital to this project—their selections shape the content available for review. Feel free to submit any high-quality, technical Bitcoin-related content you come across for potential transcription.


fix(deps): bump KMS with code change

Description
Update KMS all inclusive which removes key ring force delete because it is deprecated by the provider
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

 TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185:   # module.kms[0].module.kms_key_rings["postgresql-key-ring"].ibm_kms_key_rings.key_ring will be updated in-place
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185:   ~ resource "ibm_kms_key_rings" "key_ring" {
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185:       ~ force_delete  = true -> false
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185:         id            = "postgresql-key-ring:keyRing:crn:v1:bluemix:public:hs-crypto:us-south:a/abac0df06b644a9cabc6e44f55b3880e:e6dce284-e80f-46e1-a3c1-830f7adff7a9::"
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185:         # (3 unchanged attributes hidden)
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185:     }

This was the only error, so skipping update test.

/run pipeline

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

GitHub release
v3.17.12

Your semantic-release bot :package::rocket:


Drop mockista

We will drop mockista package. Mockery is more robust.

Done https://github.com/contributte/tester/commit/568b188917bf2d74116b536dc00e7c48bf636d99


Remove commons-httpclient

Description
Remove the commons-httpclient, this client has been superseded by the Apache httpclient. Not sure where this is being used, even the dependency tree does not show a trace:
$ mvn dependency:tree | grep -i commons-httpclient
∅

Looking at Apache Hadoop, the 2.7 branch is the latest one where the commons-httpclient » commons-httpclient is being used, after switching to Hadoop 2.8, the org.apache.httpcomponents » httpclient is used.
Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...

This PR has:

[x been self-reviewed.

Rebased onto master


Support serializer "hints" to use customized fields classes

DRF ModelSerializer has such hints as a class attributes:
    serializer_related_field = PrimaryKeyRelatedField
    serializer_related_to_field = SlugRelatedField
    serializer_url_field = HyperlinkedIdentityField
    serializer_choice_field = ChoiceField

DocumentSerializer uses hardcoded classes:

ReferenceField for 'relations'
GenericReferenceField for 'relations' w/out related_model
GenericEmbeddedDocumentField for generic embeddings

This should be moved into hints the same way as in DRF.
And classes to autocreate nested serializers should also be hintable (unike DRF), to allow recursive customized serializers.

Also:
DocumentSerializer itself for nested
EmbeddedDocumentSerializer for embedded
should also be hintable


Create dependabot.yml

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: link tbd.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] tooling / infrastructure changes
[x] Other... Please describe: Automatic dependency updates (via PR from dependabot)

What is the current behavior?

Currently the project maintainers have to update npm dependencies manually. Some things appear to be getting a bit stale.
Issue Number: N/A
There are various issues open about updating dependencies. This may not fully resolve all of them as some require major version upgrades which could require actual code changes. Dependabot will only update semver compatible versions.
What is the new behavior?
Dependabot will open PRs individually for each dependency that needs to update. Dependabot will run daily to determine if PRs are needed. It can also be run manually by a maintainer from https://github.com/namics/webpack-config-plugins/network/updates after being merged.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/keeping-your-dependencies-updated-automatically

Thanks fpr your contribution.
have not had a good experience with automatic updates, especially in a monorepo. These would only work well if all developers of all used packages would adhere to correct semantic versioning.
Instead of dependabot we use snyk in this repo. I think this is quite comparable. But you can see for yourself (https://github.com/namics/webpack-config-plugins/pulls) that the proposed updates all cause errors in the ci environment.
Instead of using another tool, I'm considering removing snyk.
Sorry for closing the ticket ;-)


Deprecating localai in favor of expanded openai_like

Description

Deprecates localai.LocalAI in favor of openai_like.OpenAILike with special parameterization
Expands OpenAI._update_max_tokens to have a backdoor for not adding max_tokens
Avoids duplication of OpenALike Field descriptions
Fixes testing in several ways

Stub tokenizer now delivers List[int]
Local testers can now run without OPENAI_API_KEY in their environment

Tightens test assertions

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

[x] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Also cc @benbot, I can't directly add you as a PR reviewer it seems

Will there also be embedding support with this?

@sfxworks it's a good question. Neither of the original LocalAI or OpenAILike here support embeddings.  This PR doesn't add embeddings support, it just merges LocalAI into a parameterization of OpenAILike.
Embeddings support for OpenAI-like models is a separate ask. There's definitely good possibility for either:

Generalizing OpenAIEmbedding to work with an OpenAI-like embedder
Creating a new OpenAILikeEmbedding class

This looks pretty clean @jamesbraza! Thanks for doing this. It seems we got good ol' conflicts with CHANGELOG.md.
Before merging just want to check with @Disiok if there is anything special we need to do since this would deprecating LocalAi.

Oh wow @sfxworks I didn't realize you're actually using LocalAI haha, awesome!  Now I will have us do a deprecation cycle for LocalAI, since it's actually being used.
This PR has been open for a few weeks, it's too bad we didn't move faster here, this change could've been merged before you made that demo.
llm = LocalAI(temperature=0, model_name="gpt-3.5-turbo", api_base="http://local-ai.default", api_key="stub")
llm.globally_use_chat_completions = True;

A few questions/comments on that part ^^^:

http://local-ai.default: why did you select this URL for api_base over something like <IP_ADDRESS>?
The LocalAI class automatically passes api_key="fake", no need to have api_key="stub" in the signature
You can have globally_use_chat_completions be directly in the signature, it could be all one line like the below

llm = LocalAI(
    temperature=0, model_name="gpt-3.5-turbo", api_base="http://local-ai.default",
    globally_use_chat_completions=True
)

http://local-ai.default: why did you select this URL for api_base over something like <IP_ADDRESS>?
I'm running localai "locally" on lan, specifically in a k8s deployment. This example runs in a python container in the cluster and uses the k8s dns naming convention to reference the deployment.

NAME               TYPE           CLUSTER-IP      EXTERNAL-IP    PORT(S)        AGE
service/local-ai   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   80:30364/TCP   31d

NAME                       READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/local-ai   1/1     1            1           35d

The LocalAI class automatically passes api_key="fake", no need to have api_key="stub" in the signature
You can have globally_use_chat_completions be directly in the signature, it could be all one line like the below
Ah good to know. Thanks!

Dang there were a ton of change in the last month 😆
I am breaking this PR up, instead of dealing with a ton of rebase conflicts. See:

Subset of tests to https://github.com/run-llama/llama_index/pull/9026

This has now been completely decomposed and merged in across 3 PRs.  All changes are available in today's 0.9.9 release.  Closing this out.

@sfxworks do you need help updating LocalAI docs? Feel free to tag me on a PR, or if you don't have the bandwidth I can update
- from llama_index.llms import LocalAI
- llm = LocalAI(temperature=0, model_name="gpt-3.5-turbo", api_base="http://local-ai.default", api_key="stub")
- llm.globally_use_chat_completions = True;
+ from llama_index.llms import LOCALAI_DEFAULTS, OpenAILike
+ llm = OpenAILike(temperature=0, model_name="gpt-3.5-turbo", is_chat_model=True, **LOCALAI_DEFAULTS)