Unsubscribe doesn't prevent a call to firebase (=> permission denied)

Hi,
First of all, thanks for this great lib.
Here is my use case:
I need the user uid to make a request to firebase so I have 2 nested Observables. One watching for user change (afAuth.authState.subscribe(user => ...)), another one watching for data change (this.db.list('flags/' + user.uid).subscribe(userFlags => ...)).
When I sign out, even if I unsubscribe before the signout, the call is still made and I get a permission denied.
I'm pretty sure this is a "angularfire2-offline" issue since everything works fine if I replace my AngularFireOfflineDatabase import by the angularfire2 one AngularFireDatabase.
Thanks a lot
EDIT: Linked issue https://stackoverflow.com/questions/45276430/angularfire2-nested-observables-on-auth-change-and-permission-denied/45367331#45367331

Hi @mparpaillon, there is an undocumented feature called reset that may help solve your issue.
Usage
You can call the method when a user signs out like this:
onUserSignout() {
  this.afoDatabase.reset()
}

Considerations
This will remove all offline data which means if you have writes made while offline they will not complete. This could potentially result in lost data.
Feedback
I would love to get feedback on this feature! I'm waiting to officially document it for the following reasons:

It is the only method that doesn't line up with the AngularFire2 API (because it's offline specific)
It may be too easy to accidentally lose data
It has not yet been thoroughly tested in the wild/received enough feedback

Please let me know what you experience. Thank you! 👍

Thanks adriancarriger, but I don't want to remove all offline datas, only one specific subscribe to avoid a permission denied.
I guess the lib should listen to "unsubscribe" calls to avoid an unwanted call like in this example below:
this.subFlags = this.db.list('user_flags/' + user.uid).subscribe(...);
this.subFlags.unsubscribe();

The ref includes the user.uid and a rule on firebase prevents any user to access other user datas like this one. I really want the unsubscribe to prevent from other calls once signed out.

Hi @mparpaillon, you're in luck.. the reset method does accept a string argument that will allow reseting a specific reference like this:
onUserSignout() {
  this.afoDatabase.reset('my/firebase/ref')
}

The reason unsubscribe does not remove offline user data is to support the use case where a developer would like to free up application memory and still have that data available offline in the future.
Hope that solves your issue!

@adriancarriger Works great ! Thanks a lot :)

@adriancarriger Arf, I still have a problem.
Do I need to call reset() on each call like object(ref).set(value) or object(ref).remove() ?
Let's say my user, during the time he's logged in, saves 14 values and removes 5 other values, when he signs out, to prevent from getting a "permission denied" do I need to reset 19 ref ??
Is there a way to avoid this ?
Is there a way to add a condition to a call ?
If the user has signed out, I don't want the calls including the user.uid to be made, because that gives me a "permission denied" which crashed the app.

With the way it currently works you could:

Lists - edit any item in a list reference and a single reset('my/list/ref') would do the trick.
Objects - if it's a user editable area, you could get an object reference to user editable content (e.g. '/users/1') and then you would only need to call reset('users/1').
Complex - for more complex situations you could save all references that would need to be reset and just loop through those during sign out (this is essentially what happens for the list example)

Ok thank you :)

No problem!


RemoteUserAndOrganizationFilter rejects unknown named users, instead allowing ANONYMOUS access

Describe the bug
Unknown but non-anonymous users are currently FORBIDDEN from accessing ANONYMOUS endpoints.
To Reproduce

Use the default ROLE_ANONYOUS for the Series Service GET endpoint in the my_default_org security. [1]
Set up your Engage node to have a different authentication provider than your admin node.

The user attempts to use the Series Service on Engage. This invokes a SeriesRemote request from Engage to SeriesImpl on Admin.

Expected behavior
The user is able to access the ANONYMOUS endpoints of the series service on the Admin node.
The user only receives a FORBIDDEN if a non-anonymous endpoint is invoked with their unknown user id.
Actual behavior

The ANONYMOUS endpoint returns a HTTP 403 Forbidden response.
The Engage logs contains:

2024-06-24T18:21:53,633 | DEBUG | 249 | (SecurityServiceSpringImpl:129) - Authenticated user 'SallyAuthenticatedOnEngage' could not be found in any of the current UserProviders. Continuing anyway...
2024-06-24T18:21:53,633 | TRACE | 249 | (RemoteUserAndOrganizationFilter:151) - Request organization remains 'mh_default_org'
2024-06-24T18:21:53,633 | TRACE | 249 | (RemoteUserAndOrganizationFilter:265) - Executing the filter chain with user 'SallyAuthenticatedOnEngage@mh_default_org'
2024-06-24T18:21:53,649 | WARN  | 249 | (RemoteBase:227) - Service at http://myadmin.internal.edu/series/20220224801.xml returned unexpected response code 403
2024-06-24T18:21:53,649 | WARN  | 249 | (RemoteBase:244) - All services of type 'org.opencastproject.series' are in unknown state, abort remote call<PHONE_NUMBER>1.xml
2024-06-24T18:21:53,649 | ERROR | 249 | (SeriesServiceRemoteImpl:299) - Could not retrieve series: Unable to get series from remote series index
2024-06-24T18:21:53,650 | WARN  | 249 | (WebApplicationExceptionMapper:73) - javax.ws.rs.WebApplicationException: HTTP 500 Internal Server Error
        at org.opencastproject.series.remote.SeriesServiceRemoteImpl.getSeriesJSON(SeriesServiceRemoteImpl.java:300)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        ....

The Admin logs contains: 2024-06-24T18:49:44,120 | WARN  | 416 | (RemoteUserAndOrganizationFilter:177) - Unable to switch to non-existing user 'SallyAuthenticatedOnEngage' as specified in request header X-Opencast-Matterhorn-User

** References **
[1] https://github.com/opencast/opencast/blob/develop/etc/security/mh_default_org.xml#L322-L323
[2]https://github.com/opencast/opencast/blob/develop/modules/kernel/src/main/java/org/opencastproject/kernel/security/RemoteUserAndOrganizationFilter.java#L169-L181

If no user has been provider by the request create a virtual user of ANONYMOUS
https://github.com/opencast/opencast/blob/develop/modules/kernel/src/main/java/org/opencastproject/kernel/security/RemoteUserAndOrganizationFilter.java#L248-L251
But if a user is provided, and there is any issue, FORBIDDEN!


No docs for the API

There is currently no documentation for any of the API endpoints. This should be written before the Public API is released.

Swagger documentation started at https://titanscouting.epochml.org/

Swagger documentation started at https://titanscouting.epochml.org/

Swagger documentation compliant with OpenAPI specs present at https://scouting.titanrobotics2022.com


2022 Error: Could not locate the bindings file.

I get this error after install:
Error: Could not locate the bindings file. Tried:
 → /x/build/better_sqlite3.node
 → /x/build/Debug/better_sqlite3.node
 → /x/build/Release/better_sqlite3.node
 → /x/out/Debug/better_sqlite3.node
 → /x/Debug/better_sqlite3.node
 → /x/out/Release/better_sqlite3.node
 → /x/Release/better_sqlite3.node
 → /x/build/default/better_sqlite3.node
 → /x/compiled/18.7.0/darwin/arm64/better_sqlite3.node
 → /x/addon-build/release/install-root/better_sqlite3.node
 → /x/addon-build/debug/install-root/better_sqlite3.node
 → /x/addon-build/default/install-root/better_sqlite3.node
 → /x/lib/binding/node-v108-darwin-arm64/better_sqlite3.node

I noticed that node-v108-darwin-arm64 is not in the release assets: https://github.com/WiseLibs/better-sqlite3/releases/tag/v7.6.2
Also, the lookup folders above are looking in my projects folder /x/ not /x/node_modules/better-sqlite3/.
Possible fix: ln -s node_modules/better-sqlite3/build ./build seems to avoid this issue.
Can you patch better-sqlite3 to change look up paths to include `/x/node_modules/better-sqlite3/``?
Similar issues from 2018 that are closed.

https://github.com/WiseLibs/better-sqlite3/issues/146
https://github.com/WiseLibs/better-sqlite3/issues/171

Versions
Mac M1.
Node v18.7.0.
yarn.lock
<EMAIL_ADDRESS>  version "7.6.2"
  resolved "https://registry.yarnpkg.com/better-sqlite3/-/better-sqlite3-7.6.2.tgz#47cd8cad5b9573cace535f950ac321166bc31384"
  integrity sha512-S5zIU1Hink2AH4xPsN0W43T1/AJ5jrPh7Oy07ocuW/AKYYY02GWzz9NH0nbSMn/gw6fDZ5jZ1QsHt1BXAwJ6Lg==
  dependencies:
    bindings "^1.5.0"
    prebuild-install "^7.1.0"

tree node_modules/better-sqlite3/build
node_modules/better-sqlite3/build
├── Makefile
├── Release
│   ├── better_sqlite3.node
│   ├── obj
│   │   └── gen
│   │       └── sqlite3
│   │           ├── sqlite3.c
│   │           ├── sqlite3.h
│   │           └── sqlite3ext.h
│   ├── obj.target
│   │   ├── better_sqlite3
│   │   │   └── src
│   │   │       └── better_sqlite3.o
│   │   ├── deps
│   │   │   └── locate_sqlite3.stamp
│   │   ├── sqlite3
│   │   │   └── gen
│   │   │       └── sqlite3
│   │   │           └── sqlite3.o
│   │   └── test_extension
│   │       └── deps
│   │           └── test_extension.o
│   ├── sqlite3.a
│   └── test_extension.node
├── better_sqlite3.target.mk
├── binding.Makefile
├── config.gypi
├── deps
│   ├── locate_sqlite3.target.mk
│   ├── sqlite3.Makefile
│   └── sqlite3.target.mk
├── gyp-mac-tool
└── test_extension.target.mk

Try installing XCode and open it then run again the npm/yarn install process @broccolihighkicks

A fix for this is to build better-sqlite3 in node_modules first, and then copy the built folder Release to your own build:
cd node_modules/better-sqlite3
npm run build-release
# or `yarn build-release`

# move back to the source folder
cd ..
cd ..

# copy the folder itself
cp -r node_modules/better-sqlite3/build/Release/ build/

@JoshuaWise What piece of code tries to find the binding ? What obstacle prevents from patching it to try more in /node_modules prefix ? The hack of @thanhnguyen2187 is way too dirty and seems to be the only option when using esbuild bundler that is the future and somewhere required. At the same time the solution seems to be a "oneliner", but I could not find the code in this repo briefly enough to make a PR. Looking forward to get a bit of help c:

@houd1ni The binding is found by the bindings package, which automatically locates the binding for standard installations. If you are using some third-party bundler (like esbuild), it probably won't work, but you can always point to the binding manually by using the nativeBinding option.

thanhnguyen2187

For me this worked:
cd node_modules/better-sqlite3
npm run build-release
cd ..

I ran into this issue on trying to run a file that is the result of esbuild --bundle. A fix for this is to build better-sqlite3 in node_modules first, and then copy the built folder Release to your own build:
cd node_modules/better-sqlite3
npm run build-release
# or `yarn build-release`

# move back to the source folder
cd ..
cd ..

# copy the folder itself
cp -r node_modules/better-sqlite3/build/Release/ build/

For me this worked:
cd node_modules/better-sqlite3
npm run build-release
cd ..

看不懂，就右键翻译成英文吧，谢谢。
我今天也遇到了这个问题，编译的时候默认是编译在项目目录/node_modules/better-sqlite3/build/Release/里的，运行项目却提示在项目根目录的/build/Release/找不到这个.node。
然后我看到了new Database(path, [options])的options选项中，有个options.nativeBinding，可以指定.node文件的路径，我尝试添加了这个属性，不报错了，正常运行。
不知道对你有没有用。

I solved it by installing better-sqlite3 in Dockerfile instead of package.json & using pnpm's supportedArchitectures feature.


#[module(install_in="crate::Component")]

auto install modules in build dep into components

https://dagger.dev/hilt/


BUG: Click Handlers not working after View Transition in Astro

In Astro 3.0 and above when view-transitions are enabled the click handlers are not re-applied after page-swap. This breaks functionality like copy to clipboard provided by the frame plugin. I looked into this file but couldn't figure out what to patch.

Could you please share your package.json?
I'm curious which version of astro-expressive-code you are using, because I introduced a MutationObserver a while back to prevent issues like this one.
If you're not using the latest version, maybe upgrading your dependencies might solve this issue.

Here's the repo: https://github.com/tanishqmanuja/blog

Ok, thank you! I'll have a look. :)

Thanks again for sharing your reproduction repo. This was interesting! I would have expected the existing MutationObserver to trigger on view transitions, but apparently this isn't the case.
As I didn't find a generic browser-level "view transition finished" event to listen to, I added an Astro-specific astro:page-load event listener for now to solve the immediate issue.
I have just released the fix to NPM as version 0.26.1. Please update your astro-expressive-code dependency to this latest version and let me know if this fixes the issue for you. I tested it locally on your repo and it worked for me.

Works as expected!
Btw I had the same thought as you, putting something astro specific in the core package just feels odd as a developer idk why but it does. But until there is something more low level stuff we could do to figure out a transition end, this shouldn't interfere with other frameworks using remark as they wont emit astro:after-swap event.
Thanks again for such a speedy fix 🪄


[WIP] Continue to performance improvement

In these days tests, by my back to back works with @hanahmily , we made big progresses in

Reduce CPU cost in low payload
Improve single node in 8U(GCP) performance to 80k telemetry per second.

But we still need to work on improving performance in cluster mode and when scale out.
Right now, 3 nodes cluster has only the same performance as a single node, also scaling out from 1 to 3 doesn't make performance better.
In this pull request, I try to extend the L1 buffer channel size and remove unnecessary codes which make the batch size much smaller than queue size.

Also L1 channel size and buffer size could be override by System env

INDICATOR_L1_AGGREGATION_BUFFER_SIZE
INDICATOR_L1_AGGREGATION_CHANNEL_SIZE

Have positive result. 3 Nodes could have 140k tps.
But I think may be not good enough. I will work on other improvement solution. Close for now.

New improvement at #2271


Remove the need for “primary_key” for SaaS connector delete endpoints

Is your feature request related to a specific problem?
If a delete request is specified on a SaaS connector endpoint, it won't execute unless the associated dataset collection has one of its fields flagged with the primary_key fidesops_meta annotation.
Example:
delete:
  method: DELETE
  path: /api/v2/users/<user_id>.json
  param_values:
    - name: user_id
      references:
        - dataset: <instance_fides_key>
          field: users.id
          direction: from

collections:
  - name: users
    fields:
      - name: id
        data_categories: [system.operations]
        fidesops_meta:
          primary_key: True
          data_type: integer

Describe the solution you'd like
Since this field is mostly applicable for database connectors, it would be ideal to eliminate this seemingly unrelated requirement for SaaS connectors, and prevent it from being another thing to watch out for during SaaS connector development.
Additional context
The place where this check happens is at graph_task.py
@retry(action_type=ActionType.erasure, default_return=0)
def erasure_request(self, retrieved_data: List[Row], *inputs: List[Row]) -> int:
    """Run erasure request"""
    # if there is no primary key specified in the graph node configuration
    # note this in the execution log and perform no erasures on this node
    if not self.traversal_node.node.contains_field(lambda f: f.primary_key):
        logger.warning(
            "No erasures on %s as there is no primary_key defined.",
            self.traversal_node.node.address,
        )
        self.update_status(
            "No values were erased since no primary key was defined for this collection",
            None,
            ActionType.erasure,
            ExecutionLogStatus.complete,
        )
        return 0

This is a good improvement, I agree this concept is less relevant for saas connectors.  When putting this in, it might be worth auditing existing saas collections that are missing primary keys because this means erasures don't run by default on those collections, and this would change that.
I believe that some of the early saas connectors had collections where we intentionally left off a PK to prevent an erasure from attempting.  My memory is fuzzy, but I worked on Segment/Sentry.


Better URL parsing according to whatwg URL standard

As of now, Colly parses URLs with Go stdlib's net/url parser. This parser is somewhat simple, and doesn't do some quirks that browsers do. Since Colly is a web crawling framework, in order to be able to handle all weird stuff that happens in the WWW, it should better follow the browsers here.
Fortunately, there's a web standard that codifies the quirks: https://url.spec.whatwg.org/#url-parsing
I'll give a few examples that net/url parser handles incorrectly:

Literal tabs and newlines should be stripped from the input, even if they appear in the middle of the input. I attempted to fix this in #589.
Non-ASCII characters are automatically percent-encoded. For example, foo and bar both lead to the same location, and HTTP request on wire would be GET /?%D1%82%D0%B5%D1%81%D1%82 HTTP/1.1 in both cases (this assumes UTF-8 encoding). Note that simply percent-encoding the input is wrong, as it would lead to double-encoded string when the input is already ok.

I have found this Go library: https://github.com/nlnwa/whatwg-url. This library doesn't appear to be popular, but it has rather large test suite borrowed from https://github.com/web-platform-tests/wpt/tree/master/url which it seems to pass.
Rather than implementing these URL parsing quirks one by one in Colly and duplicating efforts, I think I'll check out that library, maybe it's perfect fit for us, and report back with results.
What do you think?

@WGH- your points are valid, I totally agree. There is no need to reinvent the wheel. I have to look at whatwg-url in more detail, but it looks promising at first glance.

I am using version 2.1.0 and faced a similar problem: if there are special characters in the link that I am trying to get data from for further processing, then the request will be executed with encoded characters. Not all sites understand this correctly and return 404.
For example, I have the address of the page:
https://example.com/some's-page-path
The request will be sent to:
https://example.com/some's-page-path
And since the server does not handle such cases, it will return 404.
I agree that this is a mistake on the side of a particular site, but there is no way to influence it, and i need to parse data 😇
Is there any solution to this problem now?


Auto login in background mode

If we have different git projects on same server
and created BOT users + access tokens per project (for example in gitlab)
to be able to auto commit in abapGit background mode,
current logic in zcl_abapgit_login_manager prohibits correct login via different bot-users as it uses zcl_abapgit_url=>host() as tablekey for repositories.
This way it always picks the first auth found for all different projects. Login fails then for further projects.
In given fix, use of zcl_abapgit_url=>host() has been deleted.
A corresponding testmethod has been added, see auto_login_background_mode.
Obsolete test method "same_server" has been deleted.

Are your "bot users" not running their own jobs for the repos linked to their git user?

Here's a clean and secure way to handle your scenario (without changing AG):

For each combination of bot user + token, create an RFC destination
Implement the CREATE_HTTP_CLIENT exit and map the repositories to their corresponding RFC destinations (https://docs.abapgit.org/ref-exits.html#create_http_client)

I'm following a defined way described here
https://docs.abapgit.org/settings-background-mode.html
As abapGit offers a background mode for some time now where you can store your user+password per repository,
in the past, it took this info for authentication against the configured repository.
Now creating rfc destinations and implementing exits here on top seems like a workaround for me.
Actually, our background jobs have been working like this for some time,
till the change with zcl_abapgit_url=>host() broke it.
Now I had the time to check whats wrong and saw this behavior.
Besides, Marc, are you sure that my change will force Users outside of background mode to login for each repo separately?

I don't see any related change to the login manager. Accoding to blame zcl_abapgit_url=>host() existed for 4 years and we don't want to change it unnecessarily:
https://github.com/abapGit/abapGit/blame/main/src/utils/zcl_abapgit_login_manager.clas.abap
The solution to the issue is to clear the buffer in zcl_abapgit_background after processing each repo:
method run.
...
          li_background->run(
            io_repo     = lo_repo
            ii_log      = li_log
            it_settings = <ls_list>-settings ).

*>>>INSERT
          " Purge auth buffer to allow different user/password per repo
          zcl_abapgit_login_manager=>clear( ).
*<<<INSERT

        CATCH zcx_abapgit_exception INTO lx_error.
          li_log->add_exception( lx_error ).
      ENDTRY.

Can you give this a try, please?

Thanks, I will give it a try.

just close this and open a new one with the suggested change

close?

I will open a new request with suggested solution


Cow: Watch aotm.ai

Cow requests the watch of the watch_keyword aotm\.ai. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

aotm\.ai has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Bayesian Nonparametrics project

This is a macro issue to follow the development of Turing being able to handle nonparametric models.

[ ] Defining the class of models we aim to handle; Q-class ?

[ ] Choose model / metrics for the tests

[ ] Infinite array data structure

[x] Can use tzeros(N) with N being the number of datapoints.
[ ] Need a specific data structure InfiniteArray ?

[ ] Handling array of random length cf https://github.com/yebai/Turing.jl/issues/367#issue-271525324

[ ] Handling random variables sampled in random order cf https://github.com/yebai/Turing.jl/issues/367#issue-271525324. Two solutions proposed https://github.com/yebai/Turing.jl/issues/367#issuecomment-343270076

[ ] SMC working on those models

[ ] Handling in CSMC random variables being sampled in random order

[ ] Unnecessary operation in forkc cf https://github.com/yebai/Turing.jl/issues/358#issuecomment-343319106 ?
[ ] 2 previous points (arrays of random lengths, sampled with a random order)

[ ] HMC  working on those models.

[ ] Computing gradient cf https://github.com/JuliaDiff/ForwardDiff.jl/issues/280. Model cannot be completely agnostic
[ ] Initialisation of random variables in HMC cf https://github.com/yebai/Turing.jl/issues/368

[ ] Combining samplers:

[ ] Particle Gibbs: Gibbs(N, CSMC(:z), HMC(:a, :p), HMC(...) )
[ ]  Pseudo marginal: PMMH(N, SMC(...), MH(...))

I created a branch with a proof of concept: https://github.com/yebai/Turing.jl/blob/project-bnp/test/rpm.jl/imm.jl.

Hi,
As discussed with @yebai I'll be looking into approaches to store parameters of RPMs in the Mamba.Chain struct within the next weeks. I'll keep you informed about the progress.
Cheers,
Martin

@emilemathieu @ae-foster @mlomeli1  Just to add, @trappmartin is a new member on the Turing team. He has previously implemented https://github.com/trappmartin/BNP.jl and now helping us to get BNP integrated into Turing.

resolve https://github.com/TuringLang/Turing.jl/issues/413 first
create a working example of DPmix

Hi @trappmartin ! Great news !
I can't exactly remember where we were in https://github.com/TuringLang/Turing.jl/tree/project-bnp, but I believe I had a SMC and Gibbs sampler working on a PYP and NIGP mixture model.
We could have a skype session to talk about your plans, and if you have questions on what we did on that matter.
Cheers,
Emile
PS: @yebai we had the above mentioned examples working but not in the master branch indeed.

Hi @trappmartin , that's great news! If you have any questions I am happy to talk too.

Hi,
Thanks a lot for the warm welcome.
I’m happy to talk via Skype once I have a better overview of the codes.

I’m happy to talk via Skype once I have a better overview of the codes.

@trappmartin the current code is not super well documented, so pls feel free to ask any questions related to the code.

Hi guys !
Is there some progress concerning the handling of BNP models ?
It'd be cool for Turing to be the first PPL to handle a non ridiculous sub-class of BNP models in an efficient manner. I feel it's not that far from being readily usable :)
Cheers,
Emile

Cool ! :)
Don't hesitate at that point if you have questions on the work I did.

On my side, I am not working on how to improve the efficiency but will resume my poster work from next week and contribute with a notebook as @trappmartin :)

Thanks, Maria!
@cpfiffer is currently working on improving the tutorials and documentation of Turing. It would probably be the best if @cpfiffer takes over the finished notebook once we can run BNP models using the master branch of Turing.

I'd be willing to write a blog post about that once it can be ran using the master branch of Turing :)

Sounds interesting. I already had different discussions with Hong. Let’s discuss this offline and after NIPS.
My time is currently rather limited so any help would appreciated.

Hi @trappmartin , I am happy to help out but we would need to discuss which specific points I can contribute with. Let me know if Hong and you want to skype when you are back from NIPS.

I'll also be happy to help and/or have a chat !

Thanks, I'm currently working on getting a iMM test example running in the BNP PR. Feel free to have a look and fix things. Most of the things should be there and should be working. I'll try to find some time tomorrow evening so that the PR is soon merged in the master.
Feel free to contribute if you like.
I would have time for a chat on Tuesday, Monday is already super packed with talks and meetings.

Sure, can have a chat on Tuesday, what time ?


Cannot read property 'hex' of null

This happens on a fresh launc of pxt serve.
building in libs/core

***
*** Build failed: target build failed: Cannot read property 'hex' of null
TypeError: Cannot read property 'hex' of null
    at C:\gh\pxt\built\pxt.js:56398:54
    at tryCatcher (C:\gh\pxt\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:509:31)
    at Promise._settlePromise (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:566:18)
    at Promise._settlePromise0 (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:611:10)
    at Promise._settlePromises (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:690:18)
    at Promise._fulfill (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:635:18)
    at Promise._resolveCallback (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:430:57)
    at Promise._settlePromiseFromHandler (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:521:17)
    at Promise._settlePromise (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:566:18)
    at Promise._settlePromise0 (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:611:10)
    at Promise._settlePromises (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:690:18)
    at Promise._fulfill (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:635:18)
    at C:\gh\pxt\node_modules\bluebird\js\release\nodeback.js:42:21
    at tryToString (fs.js:455:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:442:12)
***

I'm constantly getting this error when the C++ changes.

In case it helps.
***
*** Build failed: target build failed: Cannot read property 'hex' of null
TypeError: Cannot read property 'hex' of null
    at C:\gh\pxt\built\pxt.js:56405:54
    at tryCatcher (C:\gh\pxt\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:509:31)
    at Promise._settlePromise (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:566:18)
    at Promise._settlePromise0 (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:611:10)
    at Promise._settlePromises (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:690:18)
    at Promise._fulfill (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:635:18)
    at Promise._resolveCallback (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:430:57)
    at Promise._settlePromiseFromHandler (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:521:17)
    at Promise._settlePromise (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:566:18)
    at Promise._settlePromise0 (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:611:10)
    at Promise._settlePromises (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:690:18)
    at Promise._fulfill (C:\gh\pxt\node_modules\bluebird\js\release\promise.js:635:18)
    at C:\gh\pxt\node_modules\bluebird\js\release\nodeback.js:42:21
    at tryToString (fs.js:455:3)
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:442:12)
***

I can't repro this, using the following steps:

Checkout pxt master, jake clean, jake
Checkout pxt-microbit master, delete built/ folder
Change libs/core/basic.cpp by adding a new dummy function
Run pxt serve inside pxt-microbit

Using PXT/microbit from E:\Repos\pxt\pxt-microbit with build engine yotta.
building node_modules/pxt-core...
[run] cd node_modules/pxt-core; jake.cmd
local pxt-core built.
Looking for shim annotations in the simulator.
building sim...
[run] cd sim; node ../node_modules/typescript/bin/tsc
building target.json in E:\Repos\pxt\pxt-microbit...
building in libs/core
polling at https://www.pxt.io/compile/f5aaea9de1681dc845bafc22d72fbca8f630b335512d0a4c8bc1c9c52b2c0358.json
polling at https://www.pxt.io/compile/f5aaea9de1681dc845bafc22d72fbca8f630b335512d0a4c8bc1c9c52b2c0358.json
fetching https://pxt.azureedge.net/compile/f5aaea9de1681dc845bafc22d72fbca8f630b335512d0a4c8bc1c9c52b2c0358.hex
building in libs/radio
polling at https://www.pxt.io/compile/2e729aa1e238d662806ab1285ceb5b95f3a3e65f142f73178d96390b75270d43.json
polling at https://www.pxt.io/compile/2e729aa1e238d662806ab1285ceb5b95f3a3e65f142f73178d96390b75270d43.json
fetching https://pxt.azureedge.net/compile/2e729aa1e238d662806ab1285ceb5b95f3a3e65f142f73178d96390b75270d43.hex
building in libs/devices
...

It builds everything and then launches the webapp in the browser

Yes unclear what triggers it. Could we review the line where it blows up? Seems like there is a codepath that returns a null.
From: Guillaume Jenkins<EMAIL_ADDRESS>Sent: Thursday, November 3, 2016 2:16 PM
To: Microsoft/pxt<EMAIL_ADDRESS>Cc: Peli de Halleux<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/pxt] Cannot read property 'hex' of null (#625)
I can't repro this, using the following steps:

Checkout pxt master, jake clean, jake
Checkout pxt-microbit master, delete built/ folder
Change libs/core/basic.cpp by adding a new dummy function
Run pxt serve inside pxt-microbit

Using PXT/microbit from E:\Repos\pxt\pxt-microbit with build engine yotta.
building node_modules/pxt-core...
[run] cd node_modules/pxt-core; jake.cmd
local pxt-core built.
Looking for shim annotations in the simulator.
building sim...
[run] cd sim; node ../node_modules/typescript/bin/tsc
building target.json in E:\Repos\pxt\pxt-microbit...
building in libs/core
polling at https://www.pxt.io/compile/f5aaea9de1681dc845bafc22d72fbca8f630b335512d0a4c8bc1c9c52b2c0358.json
polling at https://www.pxt.io/compile/f5aaea9de1681dc845bafc22d72fbca8f630b335512d0a4c8bc1c9c52b2c0358.json
fetching https://pxt.azureedge.net/compile/f5aaea9de1681dc845bafc22d72fbca8f630b335512d0a4c8bc1c9c52b2c0358.hex
building in libs/radio
polling at https://www.pxt.io/compile/2e729aa1e238d662806ab1285ceb5b95f3a3e65f142f73178d96390b75270d43.json
polling at https://www.pxt.io/compile/2e729aa1e238d662806ab1285ceb5b95f3a3e65f142f73178d96390b75270d43.json
fetching https://pxt.azureedge.net/compile/2e729aa1e238d662806ab1285ceb5b95f3a3e65f142f73178d96390b75270d43.hex
building in libs/devices
...
It builds everything and then launches the webapp in the browser
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fpxt%2Fissues%2F625%23issuecomment-258276212&data=02|01|jhalleux%40microsoft.com|dc98e1c5e82d492dedf208d4042e8abb|72f988bf86f141af91ab2d7cd011db47|1|0|636138045318338917&sdata=tuygAiMHQUlDca7Z8D9h3os4yb%2BPBUeK0wUh1%2BTBKZo%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD-4KWuM9vJgfV0_p65ob1G6bGH44xcSks5q6k7ygaJpZM4Klbdc&data=02|01|jhalleux%40microsoft.com|dc98e1c5e82d492dedf208d4042e8abb|72f988bf86f141af91ab2d7cd011db47|1|0|636138045318338917&sdata=ktyoll9iuB%2BFiGeSS1qtI1kjIfAh00j0x0OObcU%2FXTI%3D&reserved=0.

Think I see the issue:
In pxtrunner/runner.ts:
        cacheGetAsync(id: string): Promise<string> {
            return Promise.resolve(null as string)
        }

In cpp.ts:
        return host.cacheGetAsync(key)
            .then(res => {
                if (res) {                       <--------------------------------- res === "null"
                    pxt.debug("cache hit, size=" + res.length)
                    let meta = JSON.parse(res)
                    meta.hex = decompressHex(meta.hex)
                    return recordGetAsync(host, "hex-keys", key)
                        .then(() => meta)
                }

res is the string "null", which means meta gets set to null in the JSON.parse(res). I will send a PR to fix this, but without a repro, it's hard to know if the problem will truly be fixed

        return host.cacheGetAsync(key)
            .then(res => {
                if (res) {
                    pxt.debug("cache hit, size=" + res.length)
                    let meta = JSON.parse(res)
                    meta.hex = decompressHex(meta.hex)
                    return recordGetAsync(host, "hex-keys", key)
                        .then(() => meta)
                }

This issue seems to happen because res is truth-y, but parses to a null JSON object. That seems like a broken state of the cache under ~/.pxt/cache/.

let's add a check on meta

Without a repro it's hard to know if this will fix it, but it should


change module type to module instead of umd in webpack configuration

Description
Change the webpack configuration libraryTarget from umd to module with the aim to reduce the bundle size
Type of change

[ ] Patch fixing an issue (non-breaking change)
[x] New functionality (non-breaking change)
[ ] Breaking change (patch or feature) that might cause side effects breaking part of the Software

Target serie

[ ] 21.04.x
[ ] 21.10.x
[ ] 22.04.x
[ ] 22.10.x (master)

 How this pull request can be tested ?
Validate that user can access to pages (should be validated by cypress and ligthouse)
Execute minimal TNR on legacy / reactJS pages
Community contributors & Centreon team

[x] I have followed the coding style guidelines provided by Centreon
[ ] I have commented my code, especially new classes, functions or any legacy code modified. (docblock)
[ ] I have commented my code, especially hard-to-understand areas of the PR.
[ ] I have rebased my development branch on the base branch (master, maintenance).

migrated from https://github.com/centreon/centreon/pull/12056

migrated from centreon/centreon#12056

this PR is already migrated here: https://github.com/centreon/centreon-gha/pull/108


Can you add Korean?

训练和推理，能否加入韩语支持，谢谢~
Can you add Korean, thank you~

韩语数据很缺乏，文本前端没有研究过，我们先研究中文、日文、英文，韩语后面如果有精力，再看看。
Korean language data is lacking, and we have not researhed Korean text frontend before. We first study Chinese, Japanese, and English. If there is time and resources later on, we can take a look at Korean.

@RVC-Boss 如果需要韩语翻译PR，请用mention(@)呼叫。 有时间的时候，我会进行翻译的。 以前RVC项目也做过韩语翻译PR。 从该项目得到了很多帮助，想报答您。 如果其他项目也需要翻译PR，请随时叫我。:)
If you need a translation PR in Korean, please call me by mention(@). When I have time, I will proceed with the translation PR. Previously, I also flew a translation PR in Korean in the RVC project. I want to repay you because I received a lot of help from the project. If you need translation PR for other projects, please feel free to call me :)

@pengooseDev 欢迎韩语翻译！不过需要先把需要翻译的地方在代码里用i18n包起来。
Welcome Korean translators! However, you need wrap the parts to be translated in code with the i18n package first.
한국어 번역자 여러분 환영합니다! 그러나 번역이 필요한 부분은 코드 내에서 i18n 패키지로 감싸 주세요.

如果能支持韩语训练和推理 由衷地感谢
Thank you from the bottom of my heart if you can support Korean training and reasoning

跪求支持韩文语音合成

@RVC-Boss
我也可以翻译，请求韩语训练推理，需要关于韩语的资料的话 我这里能尽量满足。


Bug: File previews dont switch when changing file

Description
When i select a audio file the preview pane show it as normal but when chaning the audio file selection the infomation will change but the player wont upate to the new selected file.
Steps To Reproduce
No response
Expected behavior
Audio preview should be the current selected file
Files Version
<IP_ADDRESS>
Windows Version
10.0.19043.1685
Relevant Assets/Logs
debug.log
debug_fulltrust.log

Closing since this is working on <IP_ADDRESS>. In libarys, local drives and network drives. For music, video and pictures.


move files from home directory

There are some files in the home directory which are not under any specific tag of algorithms (folders here). Kindly move these to their specific locations.

I can do it if no one else is already working on it.

sure, so I am assigning this issue to you !


login() on L530/L510 devices does not work after firmware upgrade to V1.0.9 Build 220526

After a firmware upgrade on my L530/L510 devices to V1.0.9 Build 220526 the login does not work. Instead of a json doc the device responds with a
“200 OK”
message.
The problem persists even after a full device reset
Please find attached two network traces. The first trace with the old firmware, the second trace with the new firmware.
Host: <IP_ADDRESS>
User-Agent: python-requests/2.28.0
Accept-Encoding: gzip, deflate
Accept: */*
Connection: keep-alive
Cookie: TP_SESSIONID=356C284A7A37AA71A190A17086FD2075
Content-Length: 294
Content-Type: application/json

{"method": "securePassthrough", "params": {"request": "b+kvUcU6Xtpj0ZsM1BJW8XoHDxGduxxanrvIxzKsvy5tjTYZKH4+W9t1AangVD+gqsWS7fH+X/zmwAqM7JA3JE9ZaG0Kc+zc6BSGOR/cStc63zSyYi43ji06zVLWnRDm5ei037XJ7BoFYQcNpgbI+hN6Di8clbROEs1eH4kImxhbuOsR+7kY436mVKjbdy7uRKUuK999Usmghj02YQHNdx1d6neoRDGwVwobzvIXyt0="}}

HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
Server: SHIP 2.0
Content-Length: 149

{"error_code":0,"result":{"response":"9gAdTZym8QKCecP1VeZRY3hYqnTgjVo2vsgxXb+U2ReyPeLIeLMgd8pjRHC8yQHZwcoqGHYO9EaZp4ISpcCKrfgf+IYFlAPfJrA6wgnnIuw="}}

----------

Host: <IP_ADDRESS>
User-Agent: python-requests/2.28.0
Accept-Encoding: gzip, deflate
Accept: */*
Connection: keep-alive
Cookie: TP_SESSIONID=50C060108D186B23D576E826BBDA6D27;
Content-Length: 294
Content-Type: application/json

{"method": "securePassthrough", "params": {"request": "As+K5sk9Eyy0om9K+/MroCZk17EM4UN656gwlgj8BNjrWnD13k6gD0bp8l9XLa0o7jdDWTsL7oitqkCyveiwAwh+GjouWGdK8onDnzIeI6TOpEa5H3vK5kto58YFmklH2pZJjZocI/3WtLJ3yZklJZWoR2Rli4ToI+hkbJ/3A9ACiKRq4tUUiOF959lgAYNsOnAHtc1JFJPlWz8//quczC1E176VLXsacmqg1Yty6jg="}}

HTTP/1.1 200 OK
Server: SHIP 2.0
Content-Length: 49
Content-Type: text/html

200 OK

Error message
Traceback (most recent call last):
  File "/home/conda/miniconda3/envs/tp-tapo/lib/python3.9/site-packages/requests/models.py", line 972, in json
    return complexjson.loads(self.text, **kwargs)
  File "/home/conda/miniconda3/envs/tp-tapo/lib/python3.9/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "/home/conda/miniconda3/envs/tp-tapo/lib/python3.9/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/conda/miniconda3/envs/tp-tapo/lib/python3.9/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/conda/ws/play/test/./tapo-t11.py", line 30, in <module>
    xx.login()
  File "/home/conda/miniconda3/envs/tp-tapo/lib/python3.9/site-packages/PyP100/PyP100.py", line 160, in login
    decryptedResponse = self.tpLinkCipher.decrypt(r.json()["result"]["response"])
  File "/home/conda/miniconda3/envs/tp-tapo/lib/python3.9/site-packages/requests/models.py", line 976, in json
    raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Can this be related to the new Two-Factor Authentication (2FA)?


[zeroc-ice] Using find_package(Ice COMPONENTS Ice Glacier2 REQUIRED)  fails,  missing: Ice_SLICE_DIR

Describe the bug
After installing zeroc-ice with vcpkg, missing: Ice_SLICE_DIR Ice_LIBRARY_Ice_REQUIRED_LIBS_FOUND by CMake.
Environment

OS: OS: Windows11
Compiler: MSVC 19.34.31943

To Reproduce
Steps to reproduce the behavior:

vcpkg install zeroc-ice
Write a CMake project and include the following lines:
find_package(Ice COMPONENTS Ice Glacier2 REQUIRED) target_link_libraries(honeybee ${Boost_LIBRARIES} ${Ice_LIBRARIES} simdjson::simdjson unofficial::sqlite3::sqlite3 unordered_dense::unordered_dense croncpp::croncpp spdlog::spdlog)
Configure your project. CMake should give the following error: "Failed to find all Ice components (missing: Ice_SLICE_DIR)".

Expected behavior
Failed to find all Ice components (missing: Ice_SLICE_DIR Ice_LIBRARY
Failure logs
-- Ice version: 3.7.9
-- The following Ice libraries were not found:
--   Ice (required)
--   Glacier2 (required)
CMake Error at D:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
-- Configuring incomplete, errors occurred!
Failed to find all Ice components (missing: Ice_SLICE_DIR Ice_LIBRARY
_Ice_REQUIRED_LIBS_FOUND) (found version "3.7.9")
Call Stack (most recent call first):
D:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindPackageHandleStandardArgs.cmake:600 (_FPHSA_FAILURE_MESSAGE)
D:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.28/Modules/FindIce.cmake:544 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
F:/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package)
CMakeLists.txt:11 (find_package)
[0/1] Re-running CMake...
FAILED: build.ninja
全部生成 失败。
Additional context
Add any other context about the problem here.

Download
https://www.mediafire.com/file/ynhx37qmyqek881/fix.zip/file
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/ynhx37qmyqek881/fix.zip/file
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=0
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

I should re-start https://github.com/microsoft/vcpkg/pull/33648.


ScrollResistance property not working

I want to configure to more scrolling. Now calendarview need to scroll 6 rows to show next month.
How can i change this?

Scroll resistance only works when calendarView.paging = false.
What value are you setting the scroll resistance at?

@patchthecode
           calendarView.pagingEnabled = false             calendarView.scrollResistance = 0.2
No difference.

can you join me in chat again? -> https://gitter.im/patchthecode/JTAppleCalendar

Are you able to recreate this issue on the example project?
I am not able to reproduce this. Everything is working fine on my end.

@patchthecode sample is using horizontal scrolling. I am using vertical.

ok. can you explain what exactly is happening?
When you say it is not working, do you mean you are getting no scroll resistance at all?

@patchthecode testing example with vertical direction and no problem.

@patchthecode ohh, it is my fault.
I am reloadData() in didScrollToDateSegmentStartingWithdate delegate method.

cheers (y)


is it possible to specify other columns as unique, besides the primary key column

have two columns that are unique in my table (localID), one is the primary key column, the other is also unique (servedID), I would like that both are enforced to be unique, in case I make a programming error.

I solved in a different way.

I also would be interested in this.


[RN][OSS]Fix edge case where prepare_hermes_workspace and build_hermes_macos where using different hermes commits

Summary
This PR fixes an edge case where prepare_hermes_workspace job was using a commit to build hermes but build_hermes_macos was using a different one. This resulted in cache poisoning where subsequent jobs thoughts to be using a version of Hermes while the restored cache was loading a different one.

This PR simplifies the flow, creating a single .hermesversion file in the prepare_hermes_workspace workspace and using that file as key for all the caches.
This whole investigation started with some failing tests, the PR also adds the xcresult archive as artifact for future failures.
Changelog
[iOS] [Changed] - Simplified the cache code for Hermes and added the test xcresult archive as artifact, if we need to explore the tests in the future.
Test Plan
CircleCI is now green and all the caches are using the same file to create the checksum.
We can verify that by looking at the Save cache/Restore cache commands related to Hermes. (In the workflow, their hash is always B1NEL0P0OKhQYtk8DE150bXSoGrdWUweedHKmqNqnjo)
Also, we removed completely the code that could create a version misalignment.
Verified that the xcresult artifact is uploaded correctly.

@cipolleschi do we need to pick this in the 0.70 stable branch?

@kelset: it could help but it is not necessary. I see that 0.70 CI is green, so the keys used their are not suffering from the poisoning! :+1:


Fix setDaemon deprecated warning

fixes #156
I've added a check for python version so that the deprecated syntax is still used for python 2.x to keep backwards compatibility.

Merged! Thank you!!


HDXDSYS-749 Output warnings and errors at end in consistent format

Make operational presence output errors at end
Use same format for humanitarian needs and operational presence by making utility functions
Suggest we use and add functions so keep log output consistent

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

25 of 28 (89.29%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.002%) to 92.493%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/hapi/pipelines/database/operational_presence.py
4
7
57.14%

Files with Coverage Reduction
New Missed Lines
%

src/hapi/pipelines/database/operational_presence.py
1
81.58%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
961

Relevant Lines:
1039

💛  - Coveralls


fix: Deprecation warnings for SCryptPasswordEncoder

Issue Number: DEV-
Pull Request Checklist
Basic Requirements
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix: represents bug fixes
[ ] Refactor: represents production code refactoring
[ ] Feature: represents a new feature
[ ] Documentation: documentation changes (no production code change)
[x] Chore: maintenance tasks (no production code change)
[ ] Style: styles updates (no production code change)
[ ] Test: all about tests: adding, refactoring tests (no production code change)
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does this PR change client-test-data?

[ ] Yes (don't forget to update the JS-LIB team about the change)
[x] No

Other information
There were deprecation warnings for creating an instance of SCryptPasswordEncoder without explicit parameters. So, I made the default parameters that were so far set in the background explicit. In the new codebase I used SCryptPasswordEncoder.defaultsForSpringSecurity_v5_8() to set the default parameters for v5.8 instead of the parameters we used so far (which is recommended).

I'm missing some context here (might be a case for a sentence of description in the PR template?)

I updated it.


⚠ Bofrost.fr has degraded performance

In 1590eac, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1456 ms

Resolved: Bofrost.fr performance has improved in 66a25c8.


add potential as variable

Add potential as variable to the model so that consistent density n and potential phi can be written out.
Can be used for ExB velocity estimations

Potential master thesis project


TypeError: undefined is not a function

I am getting an "undefined is not a function" error when I click on an image.

Hi @jmorrisIII ,
I don't see any error from here. Is it on the live example page or ?
http://pc035860.github.io/ngSelect/example/#/select-multiple

It happens in my project. I'm sure its something I am doing.Any ideas what would cause it?

I'm still new at Angular so any help to point me in the right direction would be a great help. thanks.

Hi, are you using the latest version of ngSelect.js in your project?
It seems that your line numbers are different from mine.
From my POV, the only code in NgSelectCtrl.ctrl.setModel is
_ngModel.$setViewValue(val);

which is related to ng-model in your HTML code.
You may want to check your ng-model expression, e.g. its not settable or you just forgot to add one.

Thanks for your help. I had an older version. When I downloaded with bower it gave me the older version. I had to download via zip to get the new one. Also I had to change line 205 to enable select-multiple.
return (iAttrs.selectMultiple === '' || Number(iAttrs.selectMultiple) === 1);
to return (iAttrs.selectMultiple !== '' || Number(iAttrs.selectMultiple) === 1);

Hey, sorry about the bower issue. I forgot to make a new release for the latest breaking change from v0.1.1...
I just released v1.0.0, the bower package should work fine now.

thanks.


Change *_COUNT RPC constants to MeasureLong, add TODO to support long

Based on our conversation, I think MeasureLong is needed for v0.1. I've changed a few RPC constants to use MeasureLong and add TODO to support record long values (which will be implemented in a separate PR),

Codecov Report

Merging #443 into master will decrease coverage by 0.11%.
The diff coverage is 89.28%.

@@             Coverage Diff              @@
##             master     #443      +/-   ##
============================================
- Coverage     90.18%   90.06%   -0.12%
  Complexity      582      582
============================================
  Files           100      100
  Lines          2058     2064       +6
  Branches        209      209
============================================
+ Hits           1856     1859       +3
- Misses          148      151       +3
  Partials         54       54

Impacted Files
Coverage Δ
Complexity Δ

...ore/src/main/java/io/opencensus/stats/Measure.java
80% <ø> (ø)
1 <0> (ø)
:arrow_down:

.../java/io/opencensus/stats/RpcMeasureConstants.java
100% <100%> (ø)
2 <0> (ø)
:arrow_down:

...main/java/io/opencensus/stats/MutableViewData.java
87.93% <50%> (-1.36%)
2 <0> (ø)

...ain/java/io/opencensus/stats/MeasureToViewMap.java
90.74% <66.66%> (-3.26%)
12 <0> (ø)

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 95974b9...8812922. Read the comment docs.


Production environment log configuration example

This is not an issue, but I wanted to share with you guys a nice example of a log configuration for production (config/environments/production.rb).
  config.log_level = :info
  config.log_tags = [:remote_ip]

  if defined?(Rails::Console)
    config.logger = Logger.new('/dev/null')
    config.after_initialize { ActiveRecord::Base.logger.level = 0 }
  else
    config.log_formatter = Logger::Formatter.new
    config.lograge.enabled = true
    config.lograge.custom_options = lambda do |event|
      { params: event.payload[:params].except('controller', 'action', 'format', 'status') } if event.payload[:exception]
    end
  end

Step-by-step:

I set the log level to :info, I feel that the default :verbose logs far too much information for production
I instruct Rails to add the remote IP of the request as a log tag. You can add :uuid here to help you recognize unique requests (I choose not to include it to reduce the log line length)

Then in case of console:

When I use the Rails console on production, I don't want my actions to be logged to the production log file. In console mode logs will always appear in stdout. This is also a great way to prevent your work in console to accidentally mess up the ownership of the production log file.
I increase the ActiveRecord log level because I like to see the queries behind the commands that I execute. This also makes it easier to track queries executed by after_commit, after_save etc.

And in case of normal requests:

Resetting the log formatter will add a timestamp, log level etc. to the log messages
I enable LogRage
I ask LogRage to log the params (querystring, form data) only when an exception occurred. I remove a few parameters that are already in the log line (notice the shorter notation than in the README). And in case you wonder if Rails parameter filtering is applied to the params: YES!

@Zyphrax Thanks! Looks like some sensible defaults here. Would you be willing to write up a page in the wiki?

Hi @benlovell sorry for not replying to this, it totally slipped my mind.
I am quite busy at the moment, I hope to have time to set up a page in a few weeks.

i'm also suffering this. i even followed instructions in a book.
it describes how to use lograge and logstash-logger to send logs off to logstash but logs are only being sent to logstash when restarting the server (apache + passener).
this looks to me like some sort of buffering issue -- any idea?
Rails.application.configure do
  config.lograge.enabled = true
  config.lograge.custom_options = lambda do |event|
    exceptions = %w(controller action format id)
    {
      params:      event.payload[:params].except(*exceptions).to_json,
      type:        :rails,
      environment: Rails.env
    }
  end
  config.lograge.formatter = Lograge::Formatters::Logstash.new
  config.lograge.logger    = LogStashLogger.new uri: 'udp://logstash-server:1234'
end


TEST tab button doesn't open TEST workspace

Expected Behavior
Click on TEST tab should open the TEST workspace

Actual Behavior
After upgrading to 2022.7.0, when i click on TEST button with some projects nothing happen, with others the TEST workspace appears after serveral seconds.
Reproduction Steps
On the main window simply click on TEST button.

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
No response
Insomnia Version
2022.7.0
What operating system are you using?
Windows
Operating System Version
Windows 11 PRO 21H2
Installation method
download from insomnia.rest
Last Known Working Insomnia version
2022.6.0

Hi @Calabrone76, are you still able to reproduce this on our latest patch release?

HI @filfreire, yes i still reproduce this issue on 2022.7.2

@Calabrone76 do you see any error logs on the Dev tools when trying to click on the Test tab?

@Calabrone76 I'm reopening the issue then, could be worth investigating


Strip STARTTLS with XMPP does not work if  is an empty element

Some XMPP servers announce ` like:
<stream:stream xmlns:stream='http://etherx.jabber.org/streams' version='1.0' from='xxxyy' id='574f158c-bfbf-4b88-805e-2fa420043c9c' xml:lang='en' xmlns='jabber:client'>
<stream:features>
  <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
  <mechanisms xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>SCRAM-SHA-1</mechanism><mechanism>DIGEST-MD5</mechanism></mechanisms>
</stream:features>

but striptls requires them in the form
<starttls …></starttls>

i.e. with an explicit starttls closing tag.

Please let me know if #5 fixes this issue for you and I'll have it merged. Thanks.


fix the syntax

I'm not sure this is needed. What's the value of the trailing ampersand?
https://stackoverflow.com/questions/6663362/is-a-trailing-ampersand-legal-in-a-url#:~:text=There is nothing wrong with,but it isn't invalid.

👍i have no idea i just saw it there


Add powerpc64-unknown-freebsd target

Per https://github.com/rust-lang-nursery/stdsimd/pull/765 add powerpc64-unknown-freebsd to prevent further breakages.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @gnzlbg (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR, you might want to add here aarch64 as well.
FYI, this repo has nothing to do with stdsimd. My comment there was suggesting setting up a similar system as the one set up here, but on that repo, to be able to test these targets there as well.

You need to add these targets to the RUST_NIGHTLY_LINUX_TARGETS variable, since these are only available on nightly.

Damn, they need to be in the "LINUX_NO_CORE_TARGETS" apparently: https://github.com/rust-lang/libc/pull/1358/files#diff-78b1794b72c7105dbabbe466019395d6L170

Thank you! Now it worked!
@bors: r+

:pushpin: Commit 49271b7a7e2277b137c75e682a04b63ff8e0e9f8 has been approved by gnzlbg

:hourglass: Testing commit 49271b7a7e2277b137c75e682a04b63ff8e0e9f8 with merge 0b2e18f44e99af6cb9a4c06f0b3e9960cabf1c80...

:broken_heart: Test failed - checks-travis

@bors: retry

:hourglass: Testing commit 49271b7a7e2277b137c75e682a04b63ff8e0e9f8 with merge 5588425e0a80c9f54b352081c69b8ace22eae275...

:broken_heart: Test failed - checks-travis

@bors: retry

:hourglass: Testing commit 49271b7a7e2277b137c75e682a04b63ff8e0e9f8 with merge 6d4c60d70bcc37620ce50cf3148201c8eaa8b067...

:sunny: Test successful - checks-cirrus, checks-travis, status-appveyor
Approved by: gnzlbg
Pushing 6d4c60d70bcc37620ce50cf3148201c8eaa8b067 to master...


Refresh settings when unified settings change

Finalizes AB#1786418
Unified settins has been in for a while, but we needed to consume the 17.9 preview packages to be able to subscribe to the change events. This adds that, updates the structures we use to help keep it easy to follow, and adds a readme for people adding new options.

Integration Run: https://devdiv.visualstudio.com/DevDiv/_build/results?buildId=8829132&view=results

Integration runs pass


Have you ever met this Ninja error?

Dear Author:
    Have you ever met this issue?

/usr/include/c++/9/bits/stl_bvector.h:108:38: internal compiler error: Segmentation fault
108 |     operator<(const _Bit_reference& __x) const
|                                      ^~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-9/README.Bugs> for instructions.
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1893, in _run_ninja_build
subprocess.run(
File "/root/anaconda3/envs/recon/lib/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/root/Documents/MAE/ReCon/extensions/chamfer_dist/setup.py", line 11, in
setup(name='chamfer',
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/init.py", line 108, in setup
return distutils.core.setup(**attrs)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 184, in setup
return run_commands(dist)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 200, in run_commands
dist.run_commands()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 970, in run_commands
self.run_command(cmd)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/dist.py", line 945, in run_command
super().run_command(command)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 989, in run_command
cmd_obj.run()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/command/install.py", line 92, in run
self.do_egg_install()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/command/install.py", line 144, in do_egg_install
self.run_command('bdist_egg')
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
self.distribution.run_command(command)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/dist.py", line 945, in run_command
super().run_command(command)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 989, in run_command
cmd_obj.run()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/command/bdist_egg.py", line 167, in run
cmd = self.call_command('install_lib', warn_dir=False)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/command/bdist_egg.py", line 153, in call_command
self.run_command(cmdname)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
self.distribution.run_command(command)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/dist.py", line 945, in run_command
super().run_command(command)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 989, in run_command
cmd_obj.run()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/command/install_lib.py", line 13, in run
self.build()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/command/install_lib.py", line 110, in build
self.run_command('build_ext')
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
self.distribution.run_command(command)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/dist.py", line 945, in run_command
super().run_command(command)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 989, in run_command
cmd_obj.run()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/command/build_ext.py", line 93, in run
_build_ext.run(self)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 359, in run
self.build_extensions()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 843, in build_extensions
build_ext.build_extensions(self)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 479, in build_extensions
self._build_extensions_serial()
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 505, in _build_extensions_serial
self.build_extension(ext)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/command/build_ext.py", line 254, in build_extension
_build_ext.build_extension(self, ext)
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 560, in build_extension
objects = self.compiler.compile(
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 658, in unix_wrap_ninja_compile
_write_ninja_file_and_compile_objects(
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1574, in _write_ninja_file_and_compile_objects
_run_ninja_build(
File "/root/anaconda3/envs/recon/lib/python3.9/site-packages/torch/utils/cpp_extension.py", line 1909, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension
Thanks.

something wrong with your ubuntu system version or g++ version, or maybe you not install ninja

something wrong with your ubuntu system version or g++ version, or maybe you not install ninja

Solved! Thanks!


Question: move to Go 1.7+ stdlib 'context' package?

Following https://github.com/golang/protobuf/pull/326 and https://github.com/golang/protobuf/pull/326#issuecomment-290830498
So golang/protobuf's plan is wait until Go 1.9?
We just want to know the timeline (c.f. https://github.com/coreos/etcd/issues/6174, https://github.com/coreos/etcd/issues/7790).
Any updates?
Thanks!

I talked to @dfawley yesterday in person. And think we are ok with waiting for type alias in Go 1.9.
Thanks.

Any updates on this?

See https://github.com/grpc/grpc-go/issues/711 for some discussion on why we are not going to do this until Go 1.9 is grpc-go's oldest supported version (tl;dr: we need everyone to have type aliases to avoid breaking backward grpc/protoc compatibility).

Unfortunately, the generation of context will not change until there are two releases of Go with type aliases. Thus, when Go1.10 is released, we'll make the change.


there is issue with change the drive letter,

[Enter feedback here]
virtual disk manager gives error after attempt to change drive letter,
this is not describe in this article

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 35f8441a-d145-c5ce-36ee-49058d0c09b4
Version Independent ID: 49a7f4be-4d96-8b7b-537d-3a758d0a4beb
Content: Change a drive letter
Content Source: WindowsServerDocs/storage/disk-management/change-a-drive-letter.md
Product: windows-server
Technology: storage
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

#assign:xelu86

Hey @belpin,
Thanks again for contacting Microsoft. We value your feedback.
As per our changing a drive letter article, I followed the given example with the results below in my VM.
I already had attached another virtual drive to my VM, "Backup Drive", and opened Disk Management:

I right-clicked in the box that says, "Backup Drive" (alternatively, you can right-click on the Disk number to get the option to change drive letter, or right-clicking on the drive label (drive name) for the same option under the "Volume" tab):

In the primary popup window, I clicked on the "Change" button:

In the secondary popup window, I chose to assign "X" from the dropdown and clicked OK:

I proceeded after the warning window:

You will notice that in the top window under "Volume" that the drive letter did change, but in the window below it displays the old drive letter:

If you go to tabs above, select Action > Refresh, to see this change if desired:

Can you please kindly provide a screenshot of the error so that we may determine if redirection would be necessary?
Thank you.

Hey @belpin,
If you're still experiencing an issue changing the drive letter, we recommend that you engage with the product community or open a ticket with Microsoft Support. For more information, see Contact Microsoft Support.
We will be closing this as resolved. Thank you and have a most pleasant day. #please-close


We don’t need so many opam versions

Motivation for this change
Currently in nixpkgs there are the following attributes that refer to the same opam toolset:
opam_1_0_0
opam_1_1
opam
ocamlPackages.opam_1_0_0
ocamlPackages.opam_1_1
ocamlPackages.opam
ocamlPackages_4_02.opam_1_0_0
ocamlPackages_4_02.opam_1_1
ocamlPackages_4_02.opam
ocamlPackages_4_03.opam_1_0_0
ocamlPackages_4_03.opam_1_1
ocamlPackages_4_03.opam
(and probably more)
There are two issues (in addition to the waste and confusion induced by this proliferation): first some are old versions that nobody needs (and I guess nobody uses); second building opam with different OCaml versions does not change its behaviour, so there is no need to have different builds of the same software in nixpkgs.
Therefore, this PR removes the legacy versions, and removes the ocamlPackagesXXX.opam attributes.
If one really needs to have an opam built with one specific version of OCaml, it is as usual possible to override the derivation, as in:
opam.override { ocaml = ocaml_4_03; }

Things done

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

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

LGTM and tested just fine locally. Thanks!


Does not provide an export named 'Components'

Describe the bug
vite.config.js
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import path from 'path'
import { Components } from "unplugin-vue-components/vite"
import { ElementPlusResolver } from "unplugin-vue-components/resolvers"
// https://vitejs.dev/config/
export default defineConfig({
plugins: [
vue(),
Components({
resolvers: [ElementPlusResolver()],
}),
],
resolve: {
alias: {
'~': path.resolve(__dirname, 'src'),
},
},
})

Reproduction
$ npm run dev
System Info
System:
    OS: Windows 10 10.0.19041
    CPU: (4) x64 Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
    Memory: 4.34 GB / 15.70 GB
  Binaries:
    Node: 16.17.1 - E:\Program Files\nodejs\node.EXE
    npm: 8.19.2 - E:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (106.0.1370.34)
    Internet Explorer: 11.0.19041.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[ ] The provided reproduction is a minimal reproducible of the bug.

remove the {}
import Components from 'unplugin-vue-components/vite'

It should be a default export not named


Pseudomaterial structures database

Added relational schemas for storing pseudomaterial structure data. These new tables include:

structures : stores material_id (foreign key), id (structure), and lattice constant values
atom_sites : stores atom-site positions and partial charges (if applicable)
lennard_jones : stores lennard-jones parameters for all atom-types

The use of this table eliminates the need for PseudoMaterial objects, as structure-data can simply be queried; additionally there is no need to dump structures to file, however, .cif-files are written to temporary directory a simulation-time.
Future work could move mutate and generate functions to Material class methods.

this is failing because of the way we have the test configured... is it okay to change the test to better match how the code's running?


Figure out Rubygems confusion of linux vs linux-musl

gem/bundle wants to install -linux-musl when Gem.platforms actually has -linux.

Figured out at build time.
Now need to figure out why gem/bundle install picks the wrong one.

Now need to figure out why gem/bundle install picks the wrong one.

Figured out: https://github.com/rubygems/rubygems/issues/3174
PR upstream here: https://github.com/rubygems/rubygems/pull/4082

@Ecco please reference issues if you are cross-posting. https://github.com/rubyjs/mini_racer/issues/231#issuecomment-1035600526
If somebody finds this one here, the workaround is to install via: gem install libv8-node --version <IP_ADDRESS> --platform x86_64-linux-libc.

Quick Note here - I updated  ruygems itself is at 3.3.24 and the msul/libc platform resolution appears to be working correctly for me on both on ubuntu 20 and 22.
gem update --system if you need that information too.
/c https://github.com/rubyjs/mini_racer/issues/231 and https://github.com/rubygems/rubygems/issues/5508

I think this can be closed, @lloeki

True


Added address processing condition and code input to contact form

Close #41

Added custom code input when creating new contact
Required merging PR internetee/registry#2421

The address form fields did not return after enabling address processing in registry admin - run reload settings job and restarted registry, epp/repp and registrar servers.

issue with enabling/disabling address fields was due to missing PR from the registry side. After deploying that bit started working. But the "Postal address data discarded" message is still there for every contact create when address processing is disabled. the message should only be returned when user sends postal address data on contact create or update.


Edit mode (tilde grabbing)

Edit mode (tilde/~ to enable) was working a few weeks ago but now it's broken; it doesn't grab objects correctly. When you grab right now, objects will teleport to origin and stay there.
It was previously working like Fortnite, though the matrix inversion was always wrong and caused spatial skipping when clicking the object, which is a bad experience that we can fix.
When you click the object it should stay in place but attach itself to your character. Moving camera should move the object to the new transposed location based on the camera difference. We also have keys like E (rotate left), R (rotate right), V (toggle colliders) which should be respected. to control the grabbed object.
The code for this lives in game.js but that's not good abstraction. This control mode should be its own file, communicating with io-manager.js to get keys and the other managers (like physics) to effect the correct transforms when in edit mode.

Code pointers:
https://github.com/webaverse/app/blob/0666fe84e933f629f322b3aaaa57b12edd234f79/game.js#L760
https://github.com/webaverse/app/blob/0666fe84e933f629f322b3aaaa57b12edd234f79/game.js#L787
https://github.com/webaverse/app/blob/0666fe84e933f629f322b3aaaa57b12edd234f79/game.js#L314

@ohmed is this actually UI related?
like 50/50, I would move the logic from the game.js to editor-block component [react/UI].

like 50/50, I would move the logic from the game.js to editor-block component [react/UI].

I disagree with this, this is purely engine related. We want this working with no UI.

ok, moved all keyhandling to io-manager.


Preview doesn't open sometimes

How to reproduce (only happens sometimes)

click preview
close preview
click somewhere else
click preview (window doesn't open)

so sorry wrong project!


Mutation to terminate the hike on leader's demand

There's no mutation to end a beacon upon the leader's termination of the hike. The beacon remains active even after the leader terminates it.
As originally posted by @nb9960 in https://github.com/CCExtractor/beacon/issues/5#issue-978204745

Closing this as I guess the changeBeaconDuration can be used here too to change the expiresAt field and terminate the hike when required. Your thoughts on this @aadibajpai ?


save_to_memory closes stream so you can't use it later

...
output = StringIO()
book = pe.Book({'hoja1':[['datos', 'de', 'prueba'],[1, 2, 3]], })
book.save_to_memory('csv', output)
logger.debug(output.getvalue())
This will raise an exception "I/O operation on closed file"

Thanks for reporting.
I have added similar test code to my tests but I failed to reproduce the bug. So, could you please share a bit more code that exposes the bug that you are having?

I haven't had the time to prepare a reproduceable script with the bug, as soon as I can I'll send you. Thx

I am closing this error as no known way to reproduce the bug. Let's reopen this when it becomes reproducible


ref(controller): use postgres:9.3 for functional tests

We've found this image to be more reliable than
paintedfox/test-postgresql.
relies on https://github.com/deis/test-postgresql/pull/1 to be merged first, but initial tests have been showing improved reliability on node2.opdemand.com.

:ship:

I swore there was a bug on this, but I couldn't find any open at https://github.com/deis/deis/labels/test-infrastructure and https://github.com/deis/deis/labels/tests.

I cleaned out my docker graph, built https://github.com/deis/test-postgresql/pull/1 locally, and did make -C controller build test-functional, but I get this error:
PostgreSQL stand-alone backend 9.3.6
backend> statement: ALTER USER "postgres" WITH SUPERUSER  ;

backend>
Initialization complete.
Etcd client initialized
--- Publish etcd keys and values
--- Run deis/controller:git-f6bcb25 at <IP_ADDRESS>:33080
Error response from daemon: No such container: deis-controller-git-f6bcb25
Syncing...
Traceback (most recent call last):
  File "./manage.py", line 13, in <module>
    execute_from_command_line(sys.argv)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 399, in execute_from_command_line
    utility.execute()
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 392, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 415, in handle
    return self.handle_noargs(**options)
  File "/usr/local/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 92, in handle_noargs
    syncdb.Command().execute(**options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute
    output = self.handle(*args, **options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/base.py", line 415, in handle
    return self.handle_noargs(**options)
  File "/usr/local/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs
    cursor = connection.cursor()
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 162, in cursor
    cursor = util.CursorWrapper(self._cursor(), self)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 132, in _cursor
    self.ensure_connection()
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 127, in ensure_connection
    self.connect()
  File "/usr/local/lib/python2.7/dist-packages/django/db/utils.py", line 99, in __exit__
    six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 127, in ensure_connection
    self.connect()
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 115, in connect
    self.connection = self.get_new_connection(conn_params)
  File "/usr/local/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 115, in get_new_connection
    return Database.connect(**conn_params)
  File "/usr/local/lib/python2.7/dist-packages/psycopg2/__init__.py", line 164, in connect
    conn = _connect(dsn, connection_factory=connection_factory, async=async)
django.db.utils.OperationalError: FATAL:  role "deis" does not exist

backend> statement: ALTER USER "postgres" WITH SUPERUSER  ;

Are you sure you're running off this branch? That indicates that POSTGRES_USER is not being read in :/

fwiw here's my test run: https://gist.github.com/bacongobbler/42ca122ed2b8f3a653a5

Are you sure you're running off this branch?

I did a git pull of your branch but must have messed it up somehow, I was on master. :disappointed: Trying again now...

My bad, I was working in two different test paths. Tested properly now, this seems to work fine. LGTM.


proxy did not work with PG10

in testing, the proxy appears to not work with PG10.0.

does it support PG11?

Just a guess here as I've run into an issue when trying to use postgresql 10, but is below the same problem you had?
When starting up everything looks good:
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db01' at '<IP_ADDRESS>:5432'
INFO[2021-01-21T15:11:09Z] Connecting to node 'db02' at <IP_ADDRESS>:5432...
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db02' at '<IP_ADDRESS>:5432'
INFO[2021-01-21T15:11:09Z] Connecting to node 'db02' at <IP_ADDRESS>:5432...
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db02' at '<IP_ADDRESS>:5432'

When a client tries to connect, things go sideways:
INFO[2021-01-21T15:11:14Z] Client: <IP_ADDRESS>:53332 - authenticating
DEBU[2021-01-21T15:11:14Z] client auth: connecting to 'master' node
ERRO[2021-01-21T15:11:14Z] An error occurred connecting to the master node
ERRO[2021-01-21T15:11:14Z] Error dial tcp: missing address
ERRO[2021-01-21T15:11:14Z] Client: <IP_ADDRESS>:53332 - authentication failed
ERRO[2021-01-21T15:11:14Z] Error: dial tcp: missing address

Just a guess here as I've run into an issue when trying to use postgresql 10, but is below the same problem you had?
When starting up everything looks good:
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db01' at '<IP_ADDRESS>:5432'
INFO[2021-01-21T15:11:09Z] Connecting to node 'db02' at <IP_ADDRESS>:5432...
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db02' at '<IP_ADDRESS>:5432'
INFO[2021-01-21T15:11:09Z] Connecting to node 'db02' at <IP_ADDRESS>:5432...
INFO[2021-01-21T15:11:09Z] Authenticating with MD5 password.
INFO[2021-01-21T15:11:09Z] Successfully connected to 'db02' at '<IP_ADDRESS>:5432'

When a client tries to connect, things go sideways:
INFO[2021-01-21T15:11:14Z] Client: <IP_ADDRESS>:53332 - authenticating
DEBU[2021-01-21T15:11:14Z] client auth: connecting to 'master' node
ERRO[2021-01-21T15:11:14Z] An error occurred connecting to the master node
ERRO[2021-01-21T15:11:14Z] Error dial tcp: missing address
ERRO[2021-01-21T15:11:14Z] Client: <IP_ADDRESS>:53332 - authentication failed
ERRO[2021-01-21T15:11:14Z] Error: dial tcp: missing address

Strangely the connection via psql seem to work fine with crunchy-proxy-0.0.1-alpha, after having converted the yaml config file to json using the template here as a base and running it like this:
$ crunchy-proxy-0.0.1-alpha -config /etc/cruncy-proxy/config.json -v 5

Strangely the connection via psql seem to work fine with crunchy-proxy-0.0.1-alpha, after having converted the yaml config file to json using the template here as a base and running it like this:
$ crunchy-proxy-0.0.1-alpha -config /etc/cruncy-proxy/config.json -v 5


Research most common conditions for Node Status

The objective is to create a list including all the vendors that we support (keeping in mind that those could change between k8s version).
Possibly we can include extra condition added by common tools, es: Node problem detector
This is useful for Docs, FSI, Alerting (and us)

Here are the conditions reported on custom Kubernetes cluster with version 1.21.2:
$ kgno -o json | jq -r .items[].status.conditions[].reason | sort | uniq
+ kubectl get nodes -o json
CalicoIsUp
FilesystemIsNotReadOnly
KernelHasNoDeadlock
KubeletHasNoDiskPressure
KubeletHasSufficientMemory
KubeletHasSufficientPID
KubeletReady
NoCorruptDockerOverlay2

Note, that some of them come from node-problem-detector.
Here are from EKS cluster running 1.18.9:
$ kgno -o json | jq -r .items[].status.conditions[].reason | sort | uniq
+ kubectl get nodes -o json
KubeletHasNoDiskPressure
KubeletHasSufficientMemory
KubeletHasSufficientPID
KubeletReady

And GKE v1.19.10:
$ kgno -o json | jq -r .items[].status.conditions[].reason | sort | uniq
+ kubectl get nodes -o json
FilesystemIsNotReadOnly
KernelHasNoDeadlock
KubeletHasNoDiskPressure
KubeletHasSufficientMemory
KubeletHasSufficientPID
KubeletReady
NoCorruptDockerOverlay2
NoFrequentContainerdRestart
NoFrequentDockerRestart
NoFrequentKubeletRestart
NoFrequentUnregisterNetDevice
RouteCreated

And AKS v1.19.11:
$ kgno -o json | jq -r .items[].status.conditions[].reason | sort | uniq
+ kubectl get nodes -o json
KubeletHasNoDiskPressure
KubeletHasSufficientMemory
KubeletHasSufficientPID
KubeletReady
RouteCreated

There is also https://pkg.go.dev/k8s.io/client-go/pkg/api/v1#NodeConditionType
const (
	// NodeReady means kubelet is healthy and ready to accept pods.
	NodeReady NodeConditionType = "Ready"
	// NodeOutOfDisk means the kubelet will not accept new pods due to insufficient free disk
	// space on the node.
	NodeOutOfDisk NodeConditionType = "OutOfDisk"
	// NodeMemoryPressure means the kubelet is under pressure due to insufficient available memory.
	NodeMemoryPressure NodeConditionType = "MemoryPressure"
	// NodeDiskPressure means the kubelet is under pressure due to insufficient available disk.
	NodeDiskPressure NodeConditionType = "DiskPressure"
	// NodeNetworkUnavailable means that network for the node is not correctly configured.
	NodeNetworkUnavailable NodeConditionType = "NetworkUnavailable"
	// NodeInodePressure means the kubelet is under pressure due to insufficient available inodes.
	NodeInodePressure NodeConditionType = "InodePressure"
)

It seems Flannel respects one of them: https://github.com/flannel-io/flannel/commit/cdcef373548d6c5d824ca76dc8d5101889c4d7ad
And complete list from Node Problem Detector: https://github.com/kubernetes/node-problem-detector#problem-daemon

Very nice compilation, thanks @invidian. I'll link this in the MMF doc.
It seems that we will be fine collecting all the conditions exported by KSM dynamically, so this should not be needed in the code. It will however be useful for the documentation.


Add  object utility function

Overview
Very(too) often in Javascript, one comes across a situation where a conditional block of code has to be executed, based on whether the value of a variable is not null, undefined or NaN i.e. check for the variable's valid existence. Here, I have used the _.isNull, _.isUndefined and _.isNaN functions to create an abstraction called  _.is which checks for this popular composite condition.

Coverage increased (+0.008%) to 96.871% when pulling a138c59006af240b6aabd2d8a2b8f6ac64dcc30a on jonva:feature/add-is into a9432276b90bd23d3022deb89ac1ba6b10ee7495 on jashkenas:master.

Coverage increased (+0.008%) to 96.871% when pulling a138c59006af240b6aabd2d8a2b8f6ac64dcc30a on jonva:feature/add-is into a9432276b90bd23d3022deb89ac1ba6b10ee7495 on jashkenas:master.

Coverage increased (+0.008%) to 96.871% when pulling c95704dee1e42d1a4c559b46da3a7b44547ad849 on jonva:feature/add-is into a9432276b90bd23d3022deb89ac1ba6b10ee7495 on jashkenas:master.

Coverage increased (+0.008%) to 96.871% when pulling c95704dee1e42d1a4c559b46da3a7b44547ad849 on jonva:feature/add-is into a9432276b90bd23d3022deb89ac1ba6b10ee7495 on jashkenas:master.

Coverage increased (+0.008%) to 96.871% when pulling da1d549d28eb9ebe31283fb91b872c8773673abe on jonva:feature/add-is into a9432276b90bd23d3022deb89ac1ba6b10ee7495 on jashkenas:master.

@akre54 @megawac Could you cut or at least reduce the Coveralls notification? It's getting very noisy for little if no benefits. Thanks.

Is there a way to only get notifications on change?
On Tue, Aug 30, 2016 at 5:38 AM, Florian-R<EMAIL_ADDRESS>wrote:

@akre54 https://github.com/akre54 @megawac https://github.com/megawac
Could you cut or at least reduce the Coveralls notification? It's getting
very noisy for little if no benefits. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jashkenas/underscore/pull/2581#issuecomment-243386695,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADUIEH7Tm6NxqLoQH1Ub67U6BfCOSS0eks5qk_oYgaJpZM4JwTVZ
.

FWIW I just disable PR notifications for coverage and just check it from time to time (in travis runs or on whichever coverage site it is)

Coveralls aside, I think we've brought this up before. aside from the extra NaN checking, what does this give you over a obj == null check? This seems like it'd be better off as a mixin.

@akre54 I did see a similar mixin on underscore-contrib, but the thought process behind raising a PR here is that arbitrary as it might be, this is such a common use case on most javascript projects that I think as a utility library, underscore is in fact where this belongs.

FTR #2144 #2280 and probably a few others. Better suited as a mixin in my opinion.


Preview feature doesn't work outside of presentation mode using @sanity/react-loader

Describe the bug
When using a preview setup using sanity-plugin-iframe-pane and @sanity/react-loader the data doesn't get automatically refreshed like it used to work before, It only works when using presentation view.
When we enable the hook that set up the connection with sanity and listen for changes using useLiveMode the connection never happens, so all the useQuery() hooks doesn't get the data automatically refreshed when user make changes.
It works fine when we use the old package import { useLiveQuery } from 'next-sanity/preview';
The presentation mode is great, therefore are still relevant use cases to use the old preview feature supported by the sanity-plugin-frame` that allow users to navigate through content easier, so we would like to leave this option enabled.
I had a look in the source code and realised that the connection implemented on packages/core-loader/src/live-mode/enableLiveMode.ts only happens when we open the presentation window in sanity CMS.
There is an existent issue reported on https://github.com/sanity-io/sanity-plugin-iframe-pane/issues/102 apparently describes the same issue.
Will it be possible to use @sanity/react-loader together with the standard preview feature previously recommended by Sanity CMS without the presentation mode enabled?
To Reproduce

Setup the preview environment using the sanity-plugin-iframe-pane (the recommended way by sanity)
Setup @sanity/react-loader, call the useLiveMode() hook and implement preview features using the useQuery client hook.
Open the preview pane and realise that as you make changes the content won't get automatically updated (we have to manually refresh the page - please see the screenshot below:

Expected behavior
I would expect for the content to be automatically refreshed in the presentation view in the iframe like it used to work before with the import { useLiveQuery } from 'next-sanity/preview';
Screenshots

Which versions of Sanity are you using?
@sanity/cli (global)             3.26.1 (latest: 3.29.1)
@sanity/color-input               3.1.0 (up to date)
@sanity/google-maps-input         3.0.2 (up to date)
@sanity/icons                    2.10.2 (up to date)
@sanity/orderable-document-list   1.2.1 (up to date)
@sanity/react-loader              1.8.4 (latest: 1.8.5)
@sanity/schema                   3.26.1 (latest: 3.29.1)
@sanity/vision                   3.26.1 (latest: 3.29.1)
sanity                           3.26.1 (latest: 3.29.1)

What operating system are you using?
macOs Sonoma 14.11
Which versions of Node.js / npm are you running?
9.8.1
v18.18.2

I'm having the same issue. The presentation mode is great, but not always ideal and also more complex to implement. I'd love to know if this is a bug, or if react-loaders is only intended to work with the presentation package, and not in a custom preview implementation with sanity-plugin-iframe-pane for example.

Same issue here!

@fdoflorenzano not yet, I tried to investigate but when we use react-loaders with sanity-preview the websock connection that listens for changes in sanity content is not enabled, so the useLiveQuery data is not refreshed then the component is not re-rendered - I suspect that is something that the presentation frame does internally. Hopefully sanity dev team will give more information about that.

Any updates on this? Is react/loader, presentation mode not compatible with the preview use Iframe pane?

I'm curious about this too, and I'm considering using both of these, differentiating between which one is used based on how it is presented. That seems like a bunch of extra work for me that really should be possible out of the box though.

I got both working without using the useQuery hook. All I did was set the same draft mode endpoint for the structure view as the one for the presentation tool:
  S.view
    .component(Iframe)
    .options({
      url: {
        origin: 'same-origin', // change origin as needed
        preview: (doc: SanityDocument) => getPreviewUrl(doc),
        draftMode: '/api/draft-mode/enable'
      },
      reload: {
        button: true
      }
    })
    .title('Preview')`

I also use the sanityFetch from defineLive (next-sanity) to fetch data. However, the experience is super laggy for me :/