[BUG] javaScriptConsoleMessage: message=HybridUI:pluginHostDesktop: 454ms sourceId=qrc:///HybridUI/PluginUtil.js lineNumber=159

https://github.com/jkew/airtable.tableau
And the following was in the log. This is Tableau 2019.3
{"ts":"2019-09-13T22:44:53.265","pid":0,"tid":"0","sev":"info","req":"-","sess":"-","site":"-","user":"-","k":"begin-commands-controller.invoke-command","l":{},"a":{"depth":0,"id":"HJAejJGjUx5KHERT3OtDbs","name":"commands-controller.invoke-command","req-desc":"-","type":"begin"},"v":{"args":"tabui:create-connection-ui suppress-switch-tab=\"false\" value-class-attr=\"airtable_jdbc\"","name":"tabui:create-connection-ui"},"ctx":{}} {"ts":"2019-09-13T22:44:53.356","pid":31314,"tid":"14ff48","sev":"warn","req":"-","sess":"-","site":"-","user":"-","k":"msg","e":{"log-code":"00000000","log-source":"needs-classification"},"v":"Property 'props'' of object 'PluginInteropObject' has no notify signal and is not constant, value updates in HTML will be broken!"} {"ts":"2019-09-13T22:44:53.795","pid":31314,"tid":"14ff48","sev":"info","req":"-","sess":"-","site":"-","user":"-","k":"msg","e":{"log-code":"b0ef223f","log-source":"needs-classification"},"v":"WebPage javaScriptConsoleMessage: message=HybridUI:pluginHostDesktop: 454ms sourceId=qrc:///HybridUI/PluginUtil.js lineNumber=159"}

This is my dialog file:
`

<db-name-prompt value="Airtable Database: " />
<has-pre-connect-database value="true" />

`

We will investigate this issue in our next sprint.

@jkew Based on my investigation, that line is logged from line 163 and line 170 at http://opengrok.prod.tableautools.com/source/xref/dev_tableau-2019-4-dev/modules/web/plugin-host-desktop/PluginUtil.js#163
it is just a hint message while loading hybird dialog, it happens to all connectors using hybird connection dialog. not only hybird connection dialog, it also happens to other hybird dialog, like error detail dialog.
So I think it is not a bug, just a hint message logged while hybird dialog loading process.

Here the link for writing no-auth correctly.
https://tableau.github.io/connector-plugin-sdk/docs/auth-modes


Add Topic: 'this' in functions and objects

Some developers struggle to understand the use case of "this" in function and object scopes. I want to add an article to that addresses it.

/assign


Add tutorial 1032 - Fast Bit Calculations (en)

@RaiyaN-98 Excellent work Raiyan! The quality of this editorial is amazing! Very much descriptive and illustrative. No how or why has been left uncalled for. Please just add some headers and add the images internally, then we are pretty much good to merge. Beautiful work. Well done dear 💯  👑

Thank you vai. Some header files and images are now added. I think now it is good to merge.

@RaiyaN-98 Thank you dear contributor ❤ Well done! 💯


Fix "residual" invalid dynamic behaviour of optional-dependencies

Summary of changes
This is reminiscent of https://github.com/pypa/setuptools/pull/3306.
It is another situation where PEP 621 does not allow mixing dynamic and static configurations.
Without explicitly listing optional-dependencies in dynamic users cannot rely on setup.py to specify extras_require -- in turn, when optional-dependencies is present in dynamic, then it cannot be listed as an static configuration.
Therefore, the only valid situation according to PEP 621, is that static optional-dependencies are honoured exactly as provided, without modifications (this means ignoring any extras_require previously set)..

Closes https://github.com/pypa/setuptools/issues/3300
Pull Request Checklist

[x] Changes have tests
[x] News fragment added in newsfragments/.
(See documentation for details)

This cannot be done directly this way...
It needs to consider https://github.com/pypa/setuptools/issues/3204.

This cannot be done directly this way... It needs to consider #3204.

OK, so this should no longer be a problem since https://github.com/pypa/setuptools/pull/3903.
This is because converting requirements with env markers to extras no longer is done in _finalize_requires but rather when writing core metadata and does not modify the distribution attribute.


»pocok« was renamed to »proco«

Travis CI build #1547 [1] failed:

Issues :-(

Links

[L324] 301 https://github.com/shiwaforce/pocok → https://github.com/shiwaforce/proco

[1] https://travis-ci.org/veggiemonk/awesome-docker/builds/382141031

@agebhar1 awesome! Thanks 👍


Unknown error while making a remote service call: Remote host closed connection during handshake

Please provide more details, error logs, a minimal repro, etc., on the issue you are facing so we can help you better. Please use StackOverflow for usage questions. Thanks!

@lahirumaramba I have encountered the same issue when I tried virtual threads in ThreadManager in firebase-app. I have shared a post in stackoverflow. I think this errors are related to rate limit of FCM but in that case I expect the errors regarding to rate limit such as 429 http status code but I could not see these in exception.
The error "Remote host closed connection during handshake" comes from java itself not from FCM.


cannot build version 1.7 on ubuntu 20.04

I think there may be an issue with compiler flags:
[ 91%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/main.cpp.o
In file included from /home/opt/PotreeConverter-1.7/PotreeConverter/include/BINPointReader.hpp:11,
                 from /home/opt/PotreeConverter-1.7/PotreeConverter/src/BINPointReader.cpp:8:
/home/opt/PotreeConverter-1.7/PotreeConverter/include/PointReader.h:11:21: error: ‘filesystem’ is not a namespace-name
   11 | namespace fs = std::filesystem;
      |                     ^~~~~~~~~~

I tried with gcc-9 and gcc-10
From what I understand the flag -lstdc++fs may be missing ?
It seems that this part is commented in CMakeLists.txt :
#if(UNIX)
#    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -std=c++17 -pthread -lstdc++ -lstdc++fs -lm")
#    SET(CMAKE_EXE_LINKER_FLAGS  "${CMAKE_EXE_LINKER_FLAGS} -lstdc++fs" )
#endif()

but if I uncomment it, there is a mix up of c++14 and c++17 in the flags
build/PotreeConverter/CMakeFiles/PotreeConverter.dir/flags.make:CXX_FLAGS =  -Wall -std=c++17 -pthread -lstdc++ -lstdc++fs -lm -Wall -std=c++14 -pthread -lstdc++ -lm -O3 -DNDEBUG

https://github.com/potree/PotreeConverter/pull/405/files

Thanks !
@m-schuetz any chance to include this in a fix release 1.7.1 ?


What's the intended way of resuming training on a SLURM cluster?

📚 Documentation
Hi, I'm not sure if this is the intended type of issue for this category, but I thought trying doesn't hurt:
I'm trying to use lightning to train my model on a SLURM cluster due to the high memory requirements. For fairness, it only allows to train 48 hours at once, so I looked up the documentation on how to properly use checkpointing to resume where I left off as described here.
The documentation states this:

Resume training state
If you don’t just want to load weights, but instead restore the full training, do the following:
model = LitModel()
trainer = Trainer()

# automatically restores model, epoch, step, LR schedulers, etc...
trainer.fit(model, ckpt_path="some/path/to/my_checkpoint.ckpt")

So I only let it run for the maximum amount of epochs possible before the wall time would kick in. Lightning then automatically saves a checkpoint in the lightning_logs/version_21716264/checkpoints/ directory, where 21716264 is the id of the SLURM job that was used to run training. Then when I manually re-queue the job I pass the checkpoint created by the last run via CLI where it is passed to trainer.fit. So this seems to work at first glance, but there's something I noticed that seemed odd. When I do this the following warning is issued:
Restoring states from the checkpoint path at lightning_logs/version_21716264/checkpoints/epoch=13-step=188874.ckpt
/path/to/venv/lib64/python3.9/site-packages/pytorch_lightning/callbacks/model_checkpoint.py:346: UserWarning: The dirpath has changed from '/path/to/lightning_logs/version_21716264/checkpoints' to '/path/to/lightning_logs/version_21719253/checkpoints', therefore `best_model_score`, `kth_best_model_path`, `kth_value`, `last_model_path` and `best_k_models` won't be reloaded. Only `best_model_path` will be reloaded.
  warnings.warn(

This seems to suggest that using my approach it "reverts back" to the best model for further training instead of using the last model, which makes training rather ineffective at later stages when validation loss does not always decrease in a couple of epochs.
I tried searching the documentation for a solution to this problem, however it doesn't seem to clearly explain what's the intended way to achieve this. The fact that it uses the SLURM batch id for the version folder seems to suggest, that by default lightning is SLURM aware, so I searched for the lightning documentation on SLURM. I stumbled upon #13773 where I realized a "hpc" keyword exists for the checkpoint, which is supposed to restore the latest "hpc" state. I tried using it, but I just get
ValueError: `.fit(ckpt_path="hpc")` is set but no HPC checkpoint was found. Please pass an exact checkpoint path to `.{fn}(ckpt_path=...)`

So apparently there is some required prequisite for this? The "hpc" keyword is not mentioned on the cluster (advanced) page, and the trainer page only mentions this as part of the class API. Nowhere to be seen in samples, but the documentation states it "just works", when it clearly doesn't. Disclaimer at this point, I'm currently using version 1.8.1, but the changelog doesn't seem to suggest a bugfix in this direction, so I assume it still applies.
So at this point I'm confused. Do I need to store the checkpoint differently? Can't I use the automatic checkpoints for this? Or do I need to override the lightning log directory so it all happens in the same directory so the warning doesn't appear? If so, how? The trainer and SLURM doc pages don't mention anything in this direction. Do I need to define a custom ModelCheckpoint callback, or should I define a custom logger, just to use a fixed directory depending on the model? Is there a bug in lightning? I honestly have no idea what I'm supposed to do. The SLURM documentation also mentions auto-requeuing, but I assume that because of my setup bash doesn't pass the signal properly to python. I really hope that's not a precondition for this to work, because again the documentation does not mention anything like this.
Anyways, I feel like there is a straightforward solution to all of my problems the documentation is not telling me. I'm using very limited lightning functionality, so I'm naively assuming it'd just work out of the box:
dm = MyDataModule()
model = MyModel(learning_rate)
trainer = Trainer(
  accelerator='gpu' if gpu_count > 0 else None,
  devices=gpu_count or None,
  max_epochs=max_epochs,
  strategy=None if gpu_count <= 1 else DDPStrategy(find_unused_parameters=False, static_graph=True)
)
trainer.fit(model, dm, ckpt_path=checkpoint)

I'd be happy if you could point me in the right direction and add your suggestions to the official documentation so that future people won't have the same struggle as I did.
cc @borda @awaelchli

Bump

I have essentially the same problem. It would be nice if someone could chime in who uses auto-resubmission in Slurm.
Does it actually work?

I think my problem is actually a different one, or perhaps just a further source of confusion, but I'll note here in case related:
The slurm job id is used by the default logger. If the logger is defined explicitly, then by default it will number the versions consecutively, and dirpath will change when the job is requeued, so all that stuff mentioned in the error above won't be reloaded.
I worked around this by adding something like:
    # Set version number to Slurm job number
    array_job_id = os.getenv("SLURM_ARRAY_JOB_ID")
    if array_job_id is not None:
        array_task_id = os.environ["SLURM_ARRAY_TASK_ID"]
        job_id = f"{array_job_id}_{array_task_id}"
    else:
        job_id = os.environ["SLURM_JOB_ID"]

    if job_id is not None:
        job_id = int(job_id)

    trainer = pl.Trainer(
        logger=pl.loggers.TensorBoardLogger(
            "runs",
            name=RUN_NAME,
            version=job_id,
        ),
    ...
    )

Some kind of hint of this in the documentation would be useful.

It would generally be useful to expand the documentation of expected behavior for restoring automatic checkpoints.

Bump


Fix full on/off in pca9685.

It's currently not possible to toggle between full off and full on, as
switching to full on leaves the full off control bit set. The full off
control bit takes precedence according to the datasheet, which means the
signal remains off. (See datasheet page 21 for register definitions and
page 24 for information about precedence).
The 'normal' branch does correctly clear full off/full on, as it writes
0s to the LEDn_ON registers unconditionally and writes 0 to the control
bit in LEDn_OFF.

Thank you!


Feature request: Trigger pre recorded response

Could you please add the option to trigger the voice reply.
I can in example trigger the default sentence "Please leave it at the door" from the app and would like to be able to do this from code. Basically like the current quick response but with the custom recorded messages.

@swavans Are the current methods not enough?

get the VoiceIDs with the method getVoices of the class HTTPApi, the self-recorded ones should also be included.
pass the self-recorded ID to the quickResponses method of the Station class

Didn't know about the getVoices, thnx for that.


Issue with 'you' in human agent reflection

Issue
When asking a question of a human-representing agent, 'you' is getting confused in gpt
Solution
convert all you phrasing to first name when question is indicated
consider whether to use extremely cheap model to categorize or reframe

use intermediary engine

which category for quote: "${ _question }"
categories: greet, query, sharing, other

as work begins, first order is to move chat -> agent before further release


Transform event content for API endpoint calls

Passes query string parameters to the Lambda fn instead of the whole event in the case that an HTTP request with query string params comes through. If it's an API request with no query string parameters, that JSON element is null, and so the Lambda fn gets an empty list() (just like direct invocation with no args).
I've left a note in there with instructions on changing it if the user would prefer to pass the request body in to the Lambda function arguments instead of the query string parameters. It works the same way in principle, though, if the body is JSON.
Note that query string parameters are always interpreted as strings, so the Lambda fn needs to explicitly convert them to the intended type.
This still doesn't quite cut it for API Gateway: although good Lambda calls POST 200 OK, the API Gateway receives it and sends on "502: Malformed Lambda proxy response". See:

https://aws.amazon.com/premiumsupport/knowledge-center/malformed-502-api-gateway
https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html#api-gateway-simple-proxy-for-lambda-output-format

I'm not sure how to alter the POST response yet, though!

Okay, I have this working with API Gateway now!

I'm continuing to work on this in #2, and it's not quite done yet, so I might close this!


Helmet

https://github.com/fastify/fastify-helmet

fastify-helmet is a wrapper around helmet, which has these features:

helmet.contentSecurityPolicy(options)
helmet.expectCt(options)
helmet.referrerPolicy(options)
helmet.hsts(options)
helmet.noSniff()
helmet.originAgentCluster()
helmet.dnsPrefetchControl(options)
helmet.ieNoOpen()
helmet.frameguard(options)
helmet.permittedCrossDomainPolicies(options)
helmet.hidePoweredBy()
helmet.xssFilter()

Which are relevant for dunder?

@sesam Sorry, I don't know right now. I guess this needs more research actually.
My rationale for creating this issue was that maybe some fortifying lib could/should be used instead of just using raw Fastify.
helmet.hsts(options) is no-brainer at least I think.


Temporary workaround to timeout fetching elements from GQ

Fixes #9670
Status
tested
Description
Limit the number of elements pulled from global workqueue to 50k, such that we avoid the request timeout hitting us in production. Which, by the way, is also affecting the relval agent (even though the relval agent retrieves only a few kB of data...).
TODO: still to investigate whether priorities are enforced.
TODO2: I guess we will have to patch the agents in production until the situation is under control
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
none
External dependencies / deployment changes
none

 Fix #9671 - Temporary workaround to timeout fetching elements from GQ

All the 1.3.3 agents have been patched (including the relval one); and I see that work is flowing again.

Given that we don't see much job pressure in the system (either in running cores and pending jobs), I had a look at a couple of agents (FNAL and CERN) to make sure that this workaround wa being effective.
Indeed it's working fine and the agents always manage to pull some work down. The reason for the low pressure seems to actually be the large amount of workqueue elements, where each spawns just a few jobs. Summing that with a large'ish cycle of JobCreator (~500 secs at FNAL; ~1200secs at CERN), it looks to me the agent never manages to pile too much work.
One possible solution here would to actually allow WorkQueueManager to acquire more than 100 documents per cycle. I believe doubling it wouldn't have a negative side effect...

This patch has been removed from all the agents and it's no longer relevant. Closing


Long URLs overflow the chat window and create a transparent yet present horizontal scrollbar

Look at that guy, for example:

Hmm, I think #523 might be fixing it, I don't see that on my instance:

On #chat .msg:

word-break: break-word seems to work exactly like we want but is only for Webkit :-/
overflow-wrap: break-word... does nothing on Chrome
word-wrap: break-word seems to do nothing on Chrome either

Checking this on Firefox, bug does not appear there, so maybe word-break: break-word is the answer?

Hmm, I think #523 might be fixing it, I don't see that on my instance:

Possibly, but reading code and comments, removing table layout might/will lead to a whole new set of bugs, so I'll need to review and test this carefully...


[New game]: Want to add new game Tether! #4894

PR Description 📜
Please include summary related to the issue you have fixed and describe your PR in brief over here by specifying the issue number on which you were working below
Fixes #4894
Added Tether Game

Mark the task you have completed ✅

[X ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[X ] I have performed a self-review of my own code or work.
[X ] I have commented my code, particularly in hard-to-understand areas.
[X ] My changes generates no new warnings.
[X ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[X ] I have added screenshot for website preview in assets/images
[X ] I have added entries for my game in main README.md
[ X] I have added README.md in my folder
[ X] I have added working video of the game in README.md (optional)
[ X] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @nishant0708 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

hey @ishita-43 @kunjgit can you review this pr

/assign

Thank you  @nishant0708 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Fix cover size

The current layout would leave the blank cover image just right on the screen. I think we can place the blog description on the cover image like capser does would look better.

Great idea, I merged it in. Thank you for the contribution


CustomCentroidBondForce represented under NonbondedForce in energycomponent

The added CustomCentroidBondForce (system.addForce) gets represented under NonbondedForce in energycomponent output file.

Ok, this is happening because opensmog has a force dictionary that is used by the reporters.  Since you are adding a force to the model without adding it to the dictionary, the last force (i.e. the centroid force) gets listed under the index of the first force (nonbonded).  I'll write a wrapper that allows for any force to be added in a way that is consistent with the rest of opensmog.

I added a new routine called addForce.  This ensures that the name is also added to the dictionary, which is needed to properly report the energy.  See commit a5d26a3 for details.


Convert to using SharedPreferences?

I was looking in the code, and currently you are using an ObjectOutputStream to save your data. This is unintuitive; it requires parsing the entire file and that is inefficient. It also isn't very forwards-compatible, seen as you have blank in.readInt(); inside the Init().
I was thinking that we could do a SharedPreferences implementation.
SharedPreferences are much easier.

They are stored in a key-value XML file, just like a strings.xml file.
It is useful for debugging because it is a readable XML file (when it is accessed either with root access or a backup).
They can be accessed independently using:

public static SharedPreferences prefs;
public static SharedPreferences.Editor editor;

public static void doStuff(Context ctx) {
    prefs = PreferenceManager.getDefaultSharedPreferences(ctx);

    // Get a value
    String str = prefs.getString("key1", "def_value");
    boolean bool = prefs.getBoolean("key2", true);

    // Set a value
    editor = prefs.edit();
    // put as many or as little as you want, just keep the same editor instance
    editor.putString("key1", "new_value");
    // it can be chained
    editor.putBoolean("key2", false)
          .putInt("key3", 314)
          .putString("key4", "new_value");
    // when you are done
    editor.apply();
}

If we were to soon migrate to a PreferenceFragment implementation, it is very easy to do.
Setting default values is easy.

The only thing that would be a slight issue is the custom patterns. But we can store it as a string of 1's and 0's.
Converting over the prefs should be rather easy:
public void importOldPrefs(Context ctx) {
    try {
        ObjectInputStream in = /* you know what I mean */ ...;
        SharedPreferences prefs = PreferenceManager.getDefaultSharedPreferences(ctx);
        SharedPreferences.Editor editor = prefs.edit();
        editor.putInt("pattern", in.getInt());
        .....
        editor.apply();
        // We don't need this anymore
        File dir = getFilesDir();
        File file = new File(dir, SettingsFileName);
        boolean deleted = file.delete();
    catch (AnyExceptionsNeeded e) {
        e.printStackTrace();
    }
}

I could help on this.

@pelya any thoughts on this?

There were too few preferences, so I did not bother implementing it
properly. If you'll send me a merge request, I'll merge it.
On Thu, May 5, 2016 at 12:17 AM, easyaspi314 (Devin) <
<EMAIL_ADDRESS>wrote:

@pelya https://github.com/pelya any thoughts on this?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/pelya/screen-dimmer-pixel-filter/issues/8#issuecomment-217005449

I was planning to work on quite a few changes.

SharedPreferences
4.1 support
AppCompat
Disabling the overlay for SuperSU

Is that okay with you?

Yes it's okay. It would be nice to also disable the overlay when Play Store
app is launched, but I don't think you can get foreground app without root.
On Thu, May 5, 2016 at 12:25 AM, easyaspi314 (Devin) <
<EMAIL_ADDRESS>wrote:

I was planning to work on quite a few changes.

SharedPreferences
4.1 support
AppCompat
Disabling the overlay for SuperSU

Is that okay with you?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/pelya/screen-dimmer-pixel-filter/issues/8#issuecomment-217007988

You can too! :smile:
4.x and 5+ have different methods, though.
I know Lux Lite could detect the foreground app and disable it if it was running.


Not getting any stream URLs

Looks like they have changed something about the response from
https://playbox.ais.co.th/AISWeb/ServiceCheckAssetEntitlementByUserId.aspx
It now returns an empty response (200) on that URL.

Ignore that, looks like the user id's changed, updated and working again.

Ouf! good to know. Thanks!
I didn't have much time to take a look at it these past days.


API support for multiple AuthenticationSessions with the same scopes.

Currently VS Code provides an API (vscode.authentication.getSession()) that allows extensions to get an AuthenticationSession for a given set of scopes.  Depending on the options passed it, if there are no existing sessions, VS Code may prompt the user to sign in.  If there are more than one session with those scopes, VS Code may prompt the user to select which one to use.  At the end of the day, however, the extension is returned at most one AuthenticationSession that corresponds to a single account.
In some cases extensions may want to know about all the AuthenticationSession instances associated with a specific set of scopes, in order to provide multi-account experiences or to have its own UX for choosing which account is used in a specific setting (where VS Code's current selection UX might not be appropriate).  For example, a tree view that shows assets associated with multiple accounts rather than requiring the user to constantly switch between accounts.
What I propose is a new function, getSessions() with similar semantics as that same method on the AuthenticationProvider.  If matching sessions exist, all will be returned. If none exist, an empty array is returned.  Calling the function will not result in any user prompts (to select between accounts or to sign in) aside, perhaps, from the initial "do you allow this extension to access these accounts" prompt.
declare module 'vscode' {
    export namespace authentication {
        export function getSessions(providerId: string, scopes: readonly string[]): Thenable<readonly AuthenticationSession[]>;
    }
}

I'm merging https://github.com/microsoft/vscode/issues/177263 into this... In the end, here's what we'll do:

Update vscode.d.ts here to define this { detail: string } as:

export interface AuthenticationForceNewSessionOptions {
	detail: string;
}

Add to the getSessions proposed API file... to make it:

	/**
	 * Options used in {@link authentication.getSession} to be used when forcing the recreation of an {@link AuthenticationSession}.
	 */
	export interface AuthenticationForceNewSessionOptions {
		readonly session?: AuthenticationSession;
	}

	export namespace authentication {
		/**
		 * Get all authentication sessions matching the desired scopes that this extension has access to. In order to request access,
		 * use {@link getSession}. To request an additional account, specify {@link AuthenticationGetSessionOptions.clearSessionPreference}
		 * and {@link AuthenticationGetSessionOptions.createIfNone} together.
		 *
		 * Currently, there are only two authentication providers that are contributed from built in extensions
		 * to the editor that implement GitHub and Microsoft authentication: their providerId's are 'github' and 'microsoft'.
		 *
		 * @param providerId The id of the provider to use
		 * @param scopes A list of scopes representing the permissions requested. These are dependent on the authentication provider
		 * @returns A thenable that resolves to a readonly array of authentication sessions.
		 */
		export function getSessions(providerId: string, scopes: readonly string[]): Thenable<readonly AuthenticationSession[]>;
	}

One thing left to be talked about is how the AuthProvider receives the session that needs to be recreated. There are a couple options:

AuthenticationProvider needs to explicitly implement a recreateSession(...)
AuthenticationProvider#createSession(...) takes in a 2nd parameter:

createSession(scopes: readonly string[], options?: { session: AuthenticationSession }): Thenable<AuthenticationSession>;

API Sync likes the 2nd bullet, and I agree that maybe existingSession is a more descriptive parameter.

Got some other ideas... this would help manipulate the session preference so that forcing a new session would "just work".
export interface AuthenticationGetSessionOptions {
  clearSessionPreference?: boolean | AuthenticationSession;
}

or
export interface AuthenticationGetSessionOptions {
  clearSessionPreference?: boolean | { newSessionPreference: AuthenticationSession };
}

There's also this, but I'm not the biggest fan.
export interface AuthenticationGetSessionOptions {
  silent?: boolean | AuthenticationSession;
}

Also, it has come to my attention that even today, the AuthProvider is not informed as to which session is the preferred session... in other words, which one to re-create... so we still need:
createSession(scopes: readonly string[], options?: { session: AuthenticationSession }): Thenable<AuthenticationSession>;

Not fully. If no session is passed in to clearSessionPreference, then the preferred session still needs to be passed in to the auth provider's createSession call so the auth provider knows what session needs to be recreated

Moving this over to next iteration for finalization... though I think it'll probably be finalized in July since I still wanna see more adoption.

Hmm there's still more to talk about here... One of the things this is missing is some way to add an account without clearing the preference. Otherwise, this wrong behavior happens:

I have open the vscode repo in RemoteHub (preference is set to personal GH)
I "Open Remote Repository" and choose an option in the quick pick like "Add an account" because I now wanna switch to a repo with my work account
RemoteHub has to call clearSessionPreference which shows the option to "Sign in to another account"
Once that's picked then the user goes through the login flow for their work account

At this point, that account becomes the preference for this workspace. That's bad because the current workspace is the vscode repo... I haven't gone over to the other workspace yet.
So that's bad... and additionally it's annoying that the user would click something in RemoteHub's picker that says "Add an account" and then would have to pick "Sign in to another account"... an extra quick pick for no reason.

Revisiting this... I have a new proposal. I have not liked how getSessions coupled accounts and scopes so closely together. This has exposed issues like https://github.com/microsoft/vscode/issues/213947
Instead, it would be better to separate accounts and the scopes... so that means the following proposal:
/**
 * Get all accounts that the user is logged in to for the specified provider.
 * Use this paired with {@link getSession} in order to get an authentication session for a specific account.
 *
 * Currently, there are only two authentication providers that are contributed from built in extensions
 * to the editor that implement GitHub and Microsoft authentication: their providerId's are 'github' and 'microsoft'.
 *
 * Note: Getting accounts does not imply that your extension has access to that account or its authentication sessions. You can verify access to the account by calling {@link getSession}.
 *
 * @param providerId The id of the provider to use
 * @returns A thenable that resolves to a readonly array of authentication accounts.
 */
export function getAccounts(providerId: string): Thenable<readonly AuthenticationSessionAccountInformation[]>;

declare module 'vscode' {
	// FOR THE CONSUMER

	export interface AuthenticationGetSessionOptions {
		/**
	 	* The account that you would like to get a session for. This is passed down to the Authentication Provider to be used for creating the correct session.
	 	*/
		account?: AuthenticationSessionAccountInformation;
	}

	// FOR THE AUTH PROVIDER

	export interface AuthenticationProviderSessionOptions {
		/**
		 * The account that is being asked about. If this is passed in, the provider should
		 * attempt to return the sessions that are only related to this account.
		 */
		account?: AuthenticationSessionAccountInformation;
	}

	export interface AuthenticationProvider {
		/**
		 * Get a list of sessions.
		 * @param scopes An optional list of scopes. If provided, the sessions returned should match
		 * these permissions, otherwise all sessions should be returned.
		 * @param options Additional options for getting sessions.
		 * @returns A promise that resolves to an array of authentication sessions.
		 */
		getSessions(scopes: readonly string[], options: AuthenticationProviderSessionOptions): Thenable<AuthenticationSession>;
		/**
		 * Prompts a user to login.
		 *
		 * If login is successful, the onDidChangeSessions event should be fired.
		 *
		 * If login fails, a rejected promise should be returned.
		 *
		 * If the provider has specified that it does not support multiple accounts,
		 * then this should never be called if there is already an existing session matching these
		 * scopes.
		 * @param scopes A list of scopes, permissions, that the new session should be created with.
		 * @param options Additional options for creating a session.
		 * @returns A promise that resolves to an authentication session.
		 */
		createSession(scopes: readonly string[], options: AuthenticationProviderSessionOptions): Thenable<AuthenticationSession>;
	}
}

This actually follows a pretty established model that MSALjs uses where you get an account and then you pass that account in to get a token for that account.

Moving to July for potential finalization


replace ansi_term with yansi

Fixes #101
Technically a breaking change because ansi_term::Style is publicly-exported (due to the way the macros are constructed), but I would be very surprised if anyone was relying on it.

Fixes #101

Thank you very much for taking this on and fixing it!

Technically a breaking change because ansi_term::Style is publicly-exported (due to the way the macros are constructed), but I would be very surprised if anyone was relying on it.

Agree that this is unlikely to break anything, I'm happy to include it in a minor patch version and cover it with a note in the changelog. I also think having a re-exported member is not required here, so I suggest we remove it altogether rather than have this problem again in the future.

I've pushed several commits to the branch, if you could take a look and give me your opinion on them:

Fix clippy lints
Remove the public export (as above)
You updated some of the printer internals to make style an Option<Style> - I don't think this is required and contains some subtle bugs. I've reverted it to Style

If you're happy with this review points, I'm happy to squash into a new release.

It also appears that yansi does not have a documented MSRV - I'll file an issue over there to ask what their support policy is likely to be.

Opened https://github.com/SergioBenitez/yansi/pull/38, - yansi MSRV appears to be 1.54.0, which I'm happy to bump to as it's more than a year old at this point.

Your additions look fine to me

Your additions look fine to me

Thanks for taking a look. This is currently blocked on needing some more repo permissions - I have reached out to the owner to resolve this.

@colin-kiegel maybe giving others merge rights for the future?

Released in 1.3.0


the list blocks should have the number of transactions

the blocks and single block now have a property transactionCount


⚠ ClamAV has degraded performance

In 596662d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 66 ms

Resolved: ClamAV performance has improved in db5efe1.


If I use G102 ,I Can use it

If I can use it, Where should I fix it?

G102 does not have "PROGRAMMABLE BUTTONS"  feature .
At least G302, or more advanced models


Missing link to docs

This one is trivial: when I went to the main page for higlass, I clicked on the word "docs" in this sentence and got a "page not found" error:
Take a look at some examples or head over to the docs to learn how HiGlass can be used and configured.
(Lemme know if there is some other place I should report something like this.)

The URL that is not working is https://higlass.io/docs

It took me quite a bit of clicking around, but I eventually figured out that the correct URL is supposed to be https://docs.higlass.io/
This needs to be fixed in multiple places, including the one mentioned above as well as the "Docs" link at the bottom of the main page.

Apologies and thanks for the heads-up! We actually had fixed that but never updated the public deployment at higlass.io.
I just redeployed and it looks like it works now. And this is a perfect place to report things like this. Thank you for taking the time!


DSL validator tests

@MathieuAA Please review.
If this basic structure is acceptable I can add many more test cases here.

Hi @MathieuAA
I tried to apply the naming convention you recommended.
If there is just a tiny fix or two required just edit it directly on github please and we will speed things up :)

Why is the yarn.lock file different?

Why is the yarn.lock file different?

I think because I fixed to fixed range for fs-extra using github web editor so the yarn.lock was not synced to the package.json from the previous commit

I hope I fixed the eslint errors now.

Reminder to squash this to avoid polluting the history 😄

Hi @MathieuAA
Do you want to remove yarn.lock from this? is it worth the hassle or should this just be merged?

I dont understand how I closed this 😢

Just do an empty commit and it should work I think

I forced push a commit that reverted everything, I will sort it out 😢

Can't you just reopen one? (PR)

Fixed now, I started messing with the git reflog and it caused problems...
I just started from a blank slate and that fixed it
https://github.com/jhipster/jhipster-core/pull/238


🎨 Make a banner/logo for Representation Learning

💭 Description:
Need someone to design a logo/banner for the repository.
🏟 Discord:
Join Discord

@divyanshugit can you please assign me this issue, would love to come up with some designs.
you can check out my Behance link

@saroshfarhan Sure, but before raising the PR. Please share some designs of the logo over here. Once, we fix the design you can add it to assets/banner.png

@divyanshugit on it 🚀


Linkify not working if initialized with commonmark and overriding

After creating an instance with commonmark, it seems that we are unable to override the linkify option effectively.
const md = window.markdownit('commonmark')
md.set({ html: false, linkify: true }) // either via set

// or via the presetname and options combo
const md = window.markdownit('commonmark', { html: false, linkify: true })

With the configuration above, rendering the markdown content will not linkify the URLs. Strangely enough, the override for html works.
Tested with markdown-it v10.0.0 from jsDelivr.
Sample: https://jsfiddle.net/2tbuxs3j/
Question: Is this the intended behavior? It feels odd that we could override the html option, but not the linkify option.

That's intended, because only commonmark-related rules are enabled explicit in that preset. If you need additional features, you should enable missed rules back first.

@vast https://github.com/markdown-it/markdown-it/blob/master/lib/parser_core.js#L17

@vast in case it was not clear, the idea is to enable the linkify feature. This is what I've done to make it work.
// initialize markdown-it
const md = new MarkdownIt('commonmark', { html: false, linkify: true });

// enable linkify feature
md.enable(['linkify']);

https://jsfiddle.net/w8gejrdb/
Hope this helps.


add jscs+eslint info

@markelog

How does it looks like on the site?

You probably can remove Try JSCS Online (Coming back soon!) too :)

Coverage remained the same at 96.784% when pulling cb7b653245ce7dad29db1b31d5b254ab1b93adb9 on jscs-eslint into 3c3c33f91607066ceeec7192454cbc09fc10a672 on master.

👍


Composer prevents install

While having some fun with with https://github.com/JasonElkin/Hangfire-Umbraco-Example I noticed that the composer throws an exception when there's no connection string.
A site that hasn't run the installer yet won't have a connection string. If you install Cultiv.Hangfire on a brand spanking new, never before run, Umbraco repo, you won't be able to start the site.
Previously composers had a RuntimeLevel attribute to prevent this, but that's gone in v9+ and I'm not yet sure what the answer is.

@JasonElkin I had a look and the only thing I can think of right now is if the connection string is not found, we just skip the whole Hangfire setup. That means that Umbraco's install will run, but you'd need to stop/start the site for the Hangfire install to happen next. I think it's an acceptable trade-off for now. It's released in v2.0.1 now (compatible with v10, not v9).


golang reader support

Hi:
Do you have plan to support golang reader for MMDB?

I'd suggest looking at https://github.com/oschwald/geoip2-golang and https://github.com/oschwald/maxminddb-golang. We use them internally and they work well.

I tried this yesterday, but there are some errors. I think the golang reader does not support the whole data format of the MMDB.
The error log is :
parse ip country error maxminddb: cannot unmarshal map into type []struct { GeoNameID uint "maxminddb:"geoname_id""; IsoCode string "maxminddb:"iso_code""; Names map[string]string "maxminddb:"names"" }
I see the source code of golang reader, the format of  City struct does not match the MMDB that I am using

Please open an issue on that repo with the code you are using. The reader does support the full MMDB specification.


Can't set default workspace by name.

Feel free to close if this is user error but I'm trying to set the default workspace on my monitor using the
workspace=DP-1,name:my_workspace command and this results in a line parsing error while loading the config.
Is there an intended way to set the default workspace by name?

only numbers in workspace= directives

Is there any plans to implement named workspace support and/or possible workarounds?

yes and no

fixed in 84d6e640ff6e48c8161e1922349c7bce6b0b335f


Feature Request: Notify on completion or failure

It'd be great to have the script notify on successful/failed conversion to various services (Slack, pushover, pushbullet, etc).
This would add an extra layer of certainty that the file has been processed properly.

Hi,
I'm doing this differently. I have the conversion run in the background and trigger SickRage and CouchPotato as soon as a conversion is finished. SR and CP then have Pushbullet turned on as soon as they "downloaded" the file. (ie import the converted file in to their library).
If your setup works differently it's an easy thing to create a Pushbullet post_process plugin that utilizes the PB-API using simple JSON calls.
Granted having an autonomous PB interface to notify on fatal conversion errors that result in the output to be invalid would be a good thing, because that's the only time when SR/CP wouldn't notify as they don't see any files to import.

Most of the media managers have this notification feature built in to them so reproducing it just for an extension script isn't too high on the priority list
Not sure where the various media managers are about reporting processing errors but this would be an ideal feature to implement in them since they handle more aspects that could be prone for failure


Exception: Cannot set property message of [object Object] which has only a getter

When attempting to run a function, which crashed on startup (for an unrelated reason), I got the following error:
[2023-12-12T12:41:34.171Z] Worker failed to load function: 'func-name' with functionId: '…'.
[2023-12-12T12:41:34.171Z] Result: Failure
[2023-12-12T12:41:34.171Z] Exception: Cannot set property message of [object Object] which has only a getter
[2023-12-12T12:41:34.171Z] Stack: TypeError: Cannot set property message of [object Object] which has only a getter
[2023-12-12T12:41:34.171Z]     at h.<anonymous> (/opt/homebrew/Cellar/azure-functions-core-tools@4/4.0.5455/workers/node/dist/src/worker-bundle.js:2:33509)
[2023-12-12T12:41:34.171Z]     at Generator.throw (<anonymous>)
[2023-12-12T12:41:34.171Z]     at a (/opt/homebrew/Cellar/azure-functions-core-tools@4/4.0.5455/workers/node/dist/src/worker-bundle.js:2:32342).

instead of the actual error message that got thrown by my function.
worker-bundle.js:2:33509 corresponds to this line:
t.message=`Worker was unable to load function ${r.name}: '${t.message}'`

so there's something wrong with the way errors are handled.

Hi @wojtekmaj can you share your version of core tools and the "@azure/functions" npm package? If you have sample repro code, that would also be very helpful

@ejizba @azure/functions was at 3.5.1 in the project I could reproduce that in. I don't think that's relevant though. What was thrown from my function was not Error but ZodError from zod schema validation library. I believe ensureErrorType helper does not account for this.

Okay I think I understand what's happening here. The ZodError type apparently makes the "message" property read-only and doesn't let us change the message. We'll look into this. If you need a workaround in the meantime, you could probably catch the error yourself and either log it or convert it to a more normal error type that we can handle

I have just merged two PRs that should resolve this issue: https://github.com/Azure/azure-functions-nodejs-worker/pull/732 and https://github.com/Azure/azure-functions-nodejs-library/pull/220.
When these changes are deployed, I will close out this issue.

@castrodd Is the fix available on Azure yet? We are experiencing a similar problem and I'm not able to find any information on the currently deployed function-host versions.

@sladkoff It actually just started rolling out and should finish in the next couple weeks. At least for Node.js, you could check our github releases here. Of course, commenting on a specific issue is also probably one of the best ways to get this info 🙂 Btw, if you're on Windows consumption and want to test it out today, I believe the East Asia and West Central US regions already have the fix.

We're seeing a TypeError in this updated code that causes an unhandled promise rejection. Details in the PR: https://github.com/Azure/azure-functions-nodejs-worker/pull/732#discussion_r1604141371.

This PR should have fixed this issue: https://github.com/Azure/azure-functions-nodejs-worker/pull/750

Facing the exact same thing, which took me quite some time to figure out what actually was wrong.
We´re using zod to parse/validate configuration, which sometimes happens in global context.
Azure Functions Core Tools
Core Tools Version:       4.0.5907 Commit hash: N/A +807e89766a92b14fd07b9f0bc2bea1d8777ab209 (64-bit)
Function Runtime Version: 4.834.3.22875
@azure/functions: 3.5.1
Is there any ETA, when this gets shipped? Currently working around by wrapping the causing logic in a try/catch and throwing a new Error (combined with a console.error, as the logic currently is out of a context).
I have prepared a simple repro here:
https://github.com/earloc/repros-azure-functions-nodejs-library


Fix board detection for install command

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (21857aa) to head (ba42e83).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #36   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            9         9
  Lines          501       501
=========================================
  Hits           501       501

Flag
Coverage Δ

macos-latest-py-3.10
?

macos-latest-py-3.11
?

macos-latest-py-3.12
?

macos-latest-py-3.8
?

macos-latest-py-3.9
?

ubuntu-latest-py-3.10
?

ubuntu-latest-py-3.11
100.00% <100.00%> (ø)

ubuntu-latest-py-3.12
?

ubuntu-latest-py-3.8
100.00% <100.00%> (ø)

ubuntu-latest-py-3.9
100.00% <100.00%> (ø)

windows-latest-py-3.10
?

windows-latest-py-3.11
?

windows-latest-py-3.12
?

windows-latest-py-3.8
?

windows-latest-py-3.9
?

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

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


Biases observed in loopback interfaces.

With the acquire_iq.jl script, @zsoerenm noticed that there are subtle biases in the data. They are both static and dynamic. This appears in the first baseband loopback as well. This appears to have not been as observed when performing loopback from the XTRX in the carrier. While using loopback from an XTRX in the XYNC, this issue is more pronounced. Example:

The offset can be more clearly seen when there is no signal (in this case, failure to acquire at 800MHz):

This is closed in https://github.com/JuliaComputing/xtrx_julia/pull/132
There is other spurious noise and calibrations we need to test for as well, but this bias should be eliminated.


A0-1190 Escrow smart contract

Example of Escrow SC with a simple mechanism of returning funds to the buyer, when given a number of blocks passes from contract instantiation.
Testing done:

UTs pass,
Testing via UI on local node

I'd like to propose the following changes: a) constructor is payable and incorporates the deposit method b) there are two "actionable" methods: confirm and refund, callable, respectively, by buyer and seller and they BOTH end up in transfering the full deposit and terminating the contract instance (deleting it from the chain)
That simplifies the logic a bit:
* keeping the state is not needed, as there is only one "awaiting_action" state

* the buyer is automatically known since he is the person calling the constuctor

* the current logic allows any user to create an escrow for any other two users. I find it a bit strange - what does Charlie have to do with a transaction between Alice and Bob? In my opinion the role of the third party in this case should be completely handled by the blockchain and the contract, without even a possibility for a human user to take that role

very good point, logic is now simplified a lot


feat(ci): run tests daily

Need to confirm this runs at scheduled time before merging

So unfortunately this won't run until it's on the default branch so going to merge now and then check to ensure it worked tomorrow.


README.md - version removed from installation and import

from installation and import parts of the readme file "/v10" was removed (go get did not work with it)

Coverage remained the same at 76.07% when pulling 26c70372e88109f15a0a13114078b3c6e0757297 on Serj1c:updatedReadme into f6584a41c8acc5dfc0b62f7962811f5231c11530 on go-playground:master.

For me,  go get github.com/go-playground/validator/v10 is correct. If I use go get github.com/go-playground/validator, it takes v9.31.0...
Which command is right?


Back-Button is buggy

Hey,
The back button in issues is not working correctly.
For example:
In the gitpoint app open issue #55. There is a reference to #2 click on it. Than go back.
#55 should be displayed and "#55" is Standing on top of the page but #2 is displayed.
Hopefully everbody understands what i mean....
Thank you

Sorry duplicate to #3 overseen that one :laughing:

Thanks for reporting this @FlorianTaut, I'm closing this since it seems like a dupe of #3
Let me know if I'm wrong so I can re open it.


[1.16.5] Ticking block crash. Soul Campfire on hopper.

Placing a Soul Campfire on a hopper made my solo game crash, and wouldn't let me back in.
I have 52 mods installed but the crash report indicated a problem with this mod specifically. (see report below)
The game crashed as soon as I place the campfire, and the coordinates in the report confirm it to be the cause of the ticking block.
Fortunately, deleting the mod altogether resolved the ticking block.
No harm done: I only had about 9 vertical slabs that got deleted with it (I didn't combine any slabs because it seemed to cause texture problems once I had a shader installed...)
---- Minecraft Crash Report ----
// You're mean.
Time: 4/19/21 7:58 PM
Description: Ticking block entity
java.lang.IllegalArgumentException: Cannot get property BooleanProperty{name=lit, clazz=class java.lang.Boolean, values=[true, false]} as it does not exist in Block{doubleslabs:vertical_slab}
at net.minecraft.state.StateHolder.func_177229_b(SourceFile:95) ~[?:?] {re:mixin,re:classloading}
at net.minecraft.tileentity.CampfireTileEntity.func_73660_a(SourceFile:42) ~[?:?] {re:classloading}
at cjminecraft.doubleslabs.common.tileentity.SlabTileEntity.func_73660_a(SlabTileEntity.java:189) ~[?:3.5.0rc1] {re:mixin,re:classloading}
at net.minecraft.world.World.func_217391_K(World.java:491) ~[?:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B}
at net.minecraft.world.server.ServerWorld.func_72835_b(ServerWorld.java:371) ~[?:?] {re:mixin,re:classloading,pl:mixin:APP:charm.mixins.json:ServerWorldMixin,pl:mixin:APP:charm.mixins.json:accessor.ServerWorldAccessor,pl:mixin:A}
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:851) ~[?:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:charm.mixins.json:accessor.MinecraftServerAccessor,pl:mixin:A}
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:787) ~[?:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:charm.mixins.json:accessor.MinecraftServerAccessor,pl:mixin:A}
at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:118) ~[?:?] {re:classloading,xf:OptiFine:default}
at net.minecraft.server.MinecraftServer.func_240802_v_(MinecraftServer.java:642) [?:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:charm.mixins.json:accessor.MinecraftServerAccessor,pl:mixin:A}
at net.minecraft.server.MinecraftServer.func_240783_a_(MinecraftServer.java:232) [?:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:charm.mixins.json:accessor.MinecraftServerAccessor,pl:mixin:A}
at net.minecraft.server.MinecraftServer$$Lambda$6826/295621064.run(Unknown Source) [?:?] {}
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_51] {}
A detailed walkthrough of the error, its code path and all known details is as follows:
-- Head --
Thread: Server thread
Stacktrace:
at net.minecraft.state.StateHolder.func_177229_b(SourceFile:95) ~[?:?] {re:mixin,re:classloading}
at net.minecraft.tileentity.CampfireTileEntity.func_73660_a(SourceFile:42) ~[?:?] {re:classloading}
at cjminecraft.doubleslabs.common.tileentity.SlabTileEntity.func_73660_a(SlabTileEntity.java:189) ~[?:3.5.0rc1] {re:mixin,re:classloading}
-- Block entity being ticked --
Details:
Name: doubleslabs:dynamic_slab // cjminecraft.doubleslabs.common.tileentity.SlabTileEntity
Block: Block{doubleslabs:vertical_slab}[double=false,facing=north,waterlogged=false]
Block location: World: (-138,30,-297), Chunk: (at 6,1,7 in -9,-19; contains blocks -144,0,-304 to -129,255,-289), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Block: Block{doubleslabs:vertical_slab}[double=false,facing=north,waterlogged=false]
Block location: World: (-138,30,-297), Chunk: (at 6,1,7 in -9,-19; contains blocks -144,0,-304 to -129,255,-289), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Stacktrace:
at net.minecraft.world.World.func_217391_K(World.java:491) ~[?:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B}
at net.minecraft.world.server.ServerWorld.func_72835_b(ServerWorld.java:371) ~[?:?] {re:mixin,re:classloading,pl:mixin:APP:charm.mixins.json:ServerWorldMixin,pl:mixin:APP:charm.mixins.json:accessor.ServerWorldAccessor,pl:mixin:A}
-- Affected level --
Details:
All players: 1 total; [ServerPlayerEntity['helloua'/229, l='ServerLevel[2021]', x=-136.96, y=30.00, z=-293.56]]
Chunk stats: ServerChunkCache: 7569
Level dimension: minecraft:overworld
Level spawn location: World: (-144,72,-256), Chunk: (at 0,4,0 in -9,-16; contains blocks -144,0,-256 to -129,255,-241), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1)
Level time: 2830359 game time, 3831759 day time
Level name: 2021
Level game mode: Game mode: survival (ID 0). Hardcore: false.  I am aware of this but fixing this may take longer than I expected. The version you are currently using is an experimental pre release version which aims to improve the performance of the mod. To improve so, I had to change how the mod interacts with tile entities and unfortunately this issue has arose because of that change. I recommend switching back to the previous version where everything is working while I try to fix this; however since it is a change of the internal workings, it may take a while (especially as I am quite busy in real life at the moment). I apologise for the inconvenience that this will cause.

Thanks for the quick reply.
Very understandable, no worries.
I've installed the previous version (DoubleSlabs-1.16-3.4.10 I believe) and it's seems to be working splendidly.
Thanks again.


SchemaFilterContext add ModelMetadata

This pull request enhances SchemaFilterContext to include ModelMetadata, it makes the SystemType Parameter obsolete.
Adds DisplayNameAttribute and DescriptionAttribute to schema.
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/765

Sorry I didn't mean to close this PR, it was the result of a major F-up on my part - I was working on another project, accidentally added Swashbuckle as the remote and force pushed. As a result, GitHub closed all open PR's because there was no history in common. I was able to get the commits back up from my local branch but am unable to re-open PR's.


default use  "browser-sync"  and "proxy-middleware" ,

no used,I dont know why
,but I can do it that "browser-sync"  and "proxy-middleware" ,
I hope default that use  "browser-sync"  and "proxy-middleware" ,

Hello! While we appreciate you opening an issue with us i am going to close this issue and ask that you open a new one that has the issue template filled out please. Thanks for using Ionic!


Parsing formatted issues from Translator Feedback repo

For the moment, does not take into account multiple templates in 1 issue, in case of multiplicity, the syntax needs to be worked out first

Thank you @RichardBruskiewich ! Here are my responses to your questions:
[1,2] the logic I had by choosing that was that the template is built originally through sending a feedback form in the UI:

The idea of using this methodology is to limit mistakes in building a template by hand while maximizing the compatibility with the current existing feedback form.
The issues with a non strict matching of template tags is that we may end up with wrong test assets and I preferred staying of the safe side for the moment. I am open to make it less contrained if that is preferable though.
[5] I will confirm this with the UI team but so far the pattern has been invariant. My take on this is that testers inside Translator (that are the ones who submit issues in the feedback repo without the URLs), now know that the URL is one of the requirements for fixing bugs. All other users will pass through the form that automatically report it so it should be fine. Testers submitting in the GitHub repo should become aware of any new templated format and either submit a form throu UI or report following the same pattern is they want their answer to be included in the test assets (note that currently the structure only allows QA pairs that represent a tiny proportion of submitted GitHub issues. The form/template will need to be flexible enough to accomodate other possible bug reports.
The reason for parsing the URL is to minimize the amount of work/time testers need to do. Finding those same and associated CURIE takes time for no reason while "outputID" or "outputName" (which should perhaps be generalized to "area of focus for the bug" are required because the bug could potentially evolve to become intermediary nodes or paths in a result (if we take the generalization route).
What I envision (very) long term, that the submit form would be relative to the result so that a test asset could be linked directly to the components of the result (aux graph, specific IDs used for the "inferrence"...etc.): this is in line with idea for the need to refer to a result/set of results rather than to a query itself (https://github.com/NCATSTranslator/Feedback/issues/403). This won't happen soon but it could help to parse the information directly from the ARS message.


Portuguese character accentuation

In the Portuguese version, there is a problem with character accentuation. Always they are placed in the previous letter.
Linux mint 18.2

Still no answer? The new company I'm working for is using Bitrix.
Dev, if u could please tell us where are the files that select the input I would try to fix that.

Still no answer?

This project is inactive.
Find new Maintainer
There is a beta version of the official desktop application. https://www.1c-bitrix.ru/download/files/bitrix24_desktop_6_0_45_40.tgz
https://www.bitrix24.ru/features/desktop.php


add dashboard panel for roles

https://github.com/howtohireme/give-me-poc/issues/471
Description
add dashboard panel for roles
Testing steps
Explain how to test your PR manually

Step 1
Step 2
Step 3

Features PR URL
PR #ID
Checklist
Make sure that all steps a checked before the merge

[x] RSpec tests are passing on CI
[x] Cucumber features are passing localy
[x] bin/cop -a does not return any warnings
[x] Tested manually

Screenshots
if user has all roles:
https://monosnap.com/file/1VyUpkGLDlSuqLF10A0Jzqh33RbuMs

@reabiliti rebase please


Maximum call stack size exceeded when creating objects

Hello @whastings,
please take a look at the following simplified example code:
"use strict";

var Protomatter = require("protomatter");

var Model = Protomatter.create({
    private: {
        _properties: null
    },

    init: function init(properties) {
        this._properties = properties;
    }
});

var File = Model.extend({
    init: function init(path) {
        this.callSuper("init", {
            path: path
        });
    }
});

var JSONFile = File.extend({});

As soon as I try to create a new JSONFile object, it will throw the following error:
$ node example.js
$
$ (null):0
$ (null)
$
$ RangeError: Maximum call stack size exceeded

Is this a bug with protomatter or am I misusing it?

Hi Steffen,
Thank you for bringing this issue to my attention. It's an interesting case that I didn't account for. Basically, when you create a JSONFile, the init() method in File runs because JSONFile doesn't have its own init() method. But it does have its own callSuper() method. So when creating a JSONFile, the callSuper() call in File's init() just calls File's init() again, and that causes the infinite recursion. I should have a fix for this ready in a few days. Thanks again for filing the issue!
As for usage, keep in mind that the private section of the prototype definition is only for private methods. Any property assigned to this in your init() will be private automatically. You don't have to do anything special to make it private. You can still name it with an underscore prefix if you want, but it won't be accessible from outside the object's own methods.

Okay, I just pushed version 0.2.1 with a fix for this issue. Feel free to reopen this issue if you're still having trouble, or another issue if you find anything else.

I am sorry for the late response. Everything’s working as expected now. And thank you for the note on the usage of the private property, very appreciated!


Rotational effect

Description
Adds rotational effect as mentioned in #336.
It is based on the infinite effects branch (#329), so that should be merged first.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:
If something is unclear, please submit the PR anyways and ask about what you thought was unclear.

[ ] This branch is based on develop
[x] This PR is targeted to merge into develop (not master)
[x] I have formatted my code with flutter format
[x] I have made corresponding changes to the documentation
[x] I have added examples for new features in doc/examples
[x] The continuous integration (CI) is passing

Is this PR based on your branch adding the alternating and infinite effects?

Is this PR based on your branch adding the alternating and infinite effects?

It is, like it says in the PR description. ;)

Is this PR based on your branch adding the alternating and infinite effects?

It is, like it says in the PR description.

Now this is rebased on develop since the infinite-effects branch is in.

The example has to be updated after #349 is merged.

The example has to be updated after #349 is merged.

@spydon #349 has been merged, wanna update the example and land this?

Will fix tomorrow :)

Now the example is updated according the new BaseGame structure.


🐞[Bug]: Letters not arranged properly on navbar

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Patient portal is not properly aligned with other options
Expected behavior
p is small in patient portal. so Making P capital as all other options initials are also capital.
Add ScreenShots

What browsers are you seeing the problem on?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@varshith257  can you add the level tag in this

Will add based on your PR work


Avoid a-priori "in future" check in Chain DB

The goal of the proof discussed as part of #1933 to show whether or not we can use a ledger state at point X to derive timing conclusions (SlotNo to UTCTime conversion) for some point Y
------ A ----------X
       \
        \
         -------Y

or
------ A ----------X
       \
        \
         ---------------Y

The conclusion was that we can do this as long as Y is within the forecast range at the intersection point A. This makes sense, intuitively: if Y is outside of that range, a hard fork could have been confirmed somewhere between A and Y, which could have taken effect before Y, thereby effecting the timing conversion for Y.
The chain sync client knows what that intersection point A is (as of https://github.com/input-output-hk/ouroboros-network/pull/1942 it maintains it as part of its local state), and so it can pass that to timingForecastAt (as well as ledgerViewForecastAt). This then allows it to back off (block) when we have reached the end of the forecast range, and wait for the block fetch logic to catch up, or disconnect (if we end up switching to a fork).
However, when we pass the block to to the chain DB (using addBlock), we no longer know what that intersection point is. This means that the chain DB can no longer determine if it is able to to time conversion of the block's slot number given its own current ledger state (much less decide what to do it it can't). If it conservatively put that intersection at 2k slots back, we may not be able to validate any headers past our own tip (in low density chain conditions); if it optimistically put the intersection at our own tip, we might reach the wrong conclusions, applying changes that happened on our branch to a block from a different branch.
So I propose that we don't check ahead of time at all if a block is in the  future, and instead simply discover during chain selection if it or not, and if it is, don't include it in the chain selection yet. This has the nice added bonus that it will simplify the chain DB, and remove two places where we use time (addBlock and the scheduled chain selection runner).
We should consider what the ramifications of this change are. The most important use case of the chain sync client. It has already done a "in the future" check, but will allow for some clock skew. If it only very occasionally happens that we get a block from the future, the additional wasted chain selection is not problematic. Suppose however that our system clock is behind (maybe the user is not running NTP), and every block that comes in is (according to our clock) from the future. When the first block comes in, we will run chain selection, discover the block is from the future, and not change anything. Now the second block comes in; we again run chain selection, disregard the second block but now discovering the first, and so this chain selection is useful and we adopt the first block. From this point forward, each block that comes in will trigger a chain selection that discovers the previous, and no chain selection is wasted.

Marked as high priority as this is blocking the hard fork combinator.

WIP PR at https://github.com/input-output-hk/ouroboros-network/pull/1989 . This introduces a CheckInFuture abstraction and threads that through the Chain DB, making the chain DB independent from the BlockchainTime. Still needs to be done:

Actually use this abstraction during chain selection as a second validation step, excluding blocks in the future from chain selection, repeating the chain selection process just like for any other invalid block, but only marking them as invalid if they exceed the clock skew.
Re-enable the block-in-future tests of the Chain DB
Add functionality to the Chain DB to consider the previously-set-aside blocks during addBlock.

Handing this over to @mrBliss while I will continue on the hard fork stuff.

Already done in #2003 (which includes #1989).


Start of the path incorrect

Describe the bug
When setting the "Ideal start position" or a "rotation at waypoint"  at the start of the path, the robot always start at zero degrees
Expected behavior
"Ideal start position" should make the robot start at that rotation  and not make the robot rotate as fast as possible to start the path
Screenshots

After #821 is merged, I will replace the builds on the beta 1 release with the fixed version instead of doing a whole new release. You'll have to redownload the build from there.


Set up pre-commit hooks

I tried to make .clang-format suit the current coding style as much as possible, but feel free to suggest tweaks anyway.
See https://pre-commit.com for more information.

@hpvb Done. I rebased this PR against the main branch as well.

Thanks!

I found it easier to just integrate clang-format with eclipse and deal with the differences. I ended up merging your exact .clang-format into the refactor2 branch which should become main soon.


Build broken due to update of "colors" package

The release #384 containing a security fix (https://github.com/googleapis/google-p12-pem/pull/382) appears to be blocked by CI due to the sabotaged colors package having updated (https://github.com/Marak/colors.js/issues/285)
I notice that this repository doesn't have a package-lock.json or yarn.lock file in it - should one be added to help avoid this kind of unexpected breakage in future?

There are trade offs for checking in the package-lock.json.   Paging @bcoe for an explanation.

the bad release of colors was rolled back on the weekend by npm/GitHub, which unblocked #384. Security patch should be out in the wild.


Bug 2175990: Improve Default InstanceType field in Edit modal

📝 Description
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2175990
Improve Default InstanceType field/dropdown in Edit volume metadata modal, accessible in Bootable volumes list, according to the design update: add descriptive text to each one, omit "highperformance" and "server" options from the dropdown.
Improve also related 'Size' dropdown to display items with more info about number of CPUs and Memory size, sorted according to the size and not alpabetically, as expected.
See more for Default InstanceType and Size drop downs design here:
https://docs.google.com/document/d/1HTF6_H2WDXwlVy7RnrHH28dzFlhNIa15Hhpeoyg2R0Q/edit
🎥 Screenshots
Before:
Not much info about options for Default InstanceType, also the selected option not marked as selected in the dropdown:

Sizes sorted alphabetically:

After:

@avivtur @metalice @pcbailey @upalatucci @vojtechszocs please review

/hold

/hold cancel

@avivtur @metalice @pcbailey @upalatucci @vojtechszocs please review

/lgtm

/hold
I have a few comments, but haven't finished my review.


Apply Baseline plugin to iceberg-spark

This PR applies Baseline to iceberg-spark and resolves #161.
Open Questions
I’ve picked the default Scala formatting from Baseline. Here are a few points I want to bring attention to:

Baseline applies FileLengthChecker with 800 as maxFileLength. Is it ok for us?
Baseline applies CyclomaticComplexityChecker with 10 as the max value. Shall we make it 12 as in Java?
Baseline applies MethodLengthChecker with 50 as maxLength. Shall we make it 150 as in Java?
Baseline applies ReturnChecker. Is it ok for us?

The description of rules can be found here.

I’ve changed UTF8 to Utf8 because Baseline required this.

Can we disable this rule? I don't think it is valuable and it requires a lot of code changes that result in awkward names, like Utf8Reader.

I tried to add UTF8 to the list of allowed abbreviations but it didn't work for me (it worked for SQL, though). I will disable this rule in the next pass. Let me know what you think about the other open questions.

cc @rdsr @mccheah

I had some minor comments, but I don't see any bugs introduced by this. Thanks @aokolnychyi!
I think the choices you made sound good.

I've removed AbbreviationAsWordInName and reverted changes required by that rule.
Also, the PR description contains a few points I want to bring attention on Scala formatting in Baseline. Let me know if we want to change defaults there.

Here are some responses to the questions in the description. The rest of them sound fine to me.

Baseline applies ReturnChecker. Is it ok for us?

Yes? What does it do?

Baseline doesn't apply ImportOrderChecker by default. Shall we add it?

Yes, I think so.

Baseline doesn't apply DisallowSpaceBeforeTokenChecker by default. Shall we add it?

I think so. This is consistent with the Java formatting, right?

Baseline doesn't apply NonASCIICharacterChecker by default. Shall we add it?

Is this intended to catch fancy quotes? I think we probably don't need it. Plus, we have some areas with multi-byte characters in strings (@rdsr's recent Avro fix, for example).

Enabled ImportOrderChecker and grouped all imports together as we do in Java.
Enabled DisallowSpaceBeforeTokenChecker.
Let's ignore NonASCIICharacterChecker.

@rdblue ReturnChecker ensures that we don't have explicit return statements.

ReturnChecker doesn't sound like a good idea to me. Sometimes it's easier to use an explicit return and I see no reason to disallow it.

+1, that's the reason why I brought up this topic. Anything else to change?

Some of those are probably worth adding to Baseline proper - it seems bad to not have ImportOrderChecker for example. I'll file against Baseline in a bit.


Ligand with Charge

I would like to know what I should do if my ligand is charged in my protein-ligand complex. For example, the ligand has a -COOH group in it, and it is deprotonated in my ligand and becomes -COO⁻. If I run Uni-GBSA normally, it will give the following error:

Running: /home/username/anaconda3/envs/gbsa/bin/atomtype -i ANTECHAMBER_AC.AC0 -o ANTECHAMBER_AC.AC -p gaff
Info: Total number of electrons: 71; net charge: 0
Info: The number of electrons is odd (71).
Please check the total charge (-nc flag) and spin multiplicity (-m flag).

which means that it assumes that the molecule is neutral and the molecule is a radical (-COO·). In this case, how can I specify the negative charge in Uni-GBSA?
Any help would be appreciated.

You can try the command unigbsa-validate to fix this problem. But please double check the output file.


bpf: CT drops final FIN+ACK

The BPF conntrack code seems to remove the conntrack entry prematurely which leads to the final FIN+ACK being dropped due to lack of conntrack entry:
xx drop (CT: Can't create entry from packet) to endpoint 0, identity 0->0: <IP_ADDRESS>:46368 -> <IP_ADDRESS>:8080 tcp ACK, FIN

How reproducible is this issue? (Rare occurrences or almost each time in test env?)
Latest master or older cilium version?
Is L7 proxy involved?
Connection is local on a single node (container <-> container) or spans accross multiple nodes (container <--wire--> container)?
Is global or local CT table used?
CT table is LRU or hash table with timeout (probably unlikely we hit the tmo first, though)?
Did we hit RST in the packet flow earlier (probably not, but would immediately close the entry)?
Small sample client/server tcpdump packet flow, or pcap would be good for inspection.

How reproducible is this issue? (Rare occurrences or almost each time in test env?)
Every TCP connection

Latest master or older cilium version?

Latest master

Is L7 proxy involved?

It definitely occurs with proxy involved. Likely also with proxy not involved. I suspect it's a general CT handling issue.

Connection is local on a single node (container <-> container) or spans accross multiple nodes (container <--wire--> container)?

Container to container for both, local node and multi node.

Is global or local CT table used?

Global CT. Unverified with local table.

CT table is LRU or hash table with timeout (probably unlikely we hit the tmo first, though)?

Doesn't matter. The failure occurs because we delete the CT entry before the final FIN is processed.

Did we hit RST in the packet flow earlier (probably not, but would immediately close the entry)?
Small sample client/server tcpdump packet flow, or pcap would be good for inspection.

No RST. The issue occurs in every TCP connection when FIN is being processed.

Via #1186


test_reorged_deposit_status is flaky

It seems to not detect the reorg sometimes. Could be nothing, but it should be fixed
revault_network = <test_framework.revault_network.RevaultNetwork object at 0x7f9251c9bca0>
bitcoind = <test_framework.bitcoind.BitcoinD object at 0x7f9251c9bf70>

    @pytest.mark.skipif(not POSTGRES_IS_SETUP, reason="Needs Postgres for servers db")
    def test_reorged_deposit_status(revault_network, bitcoind):
        # A csv of 2 because bitcoind would discard updating the mempool if the reorg is >10
        # blocks long.
        revault_network.deploy(4, 2, csv=2)
        vault = revault_network.fund(0.14)
        revault_network.secure_vault(vault)
        deposit = f"{vault['txid']}:{vault['vout']}"

        # Reorg the deposit. This should not affect us as the transaction did not
        # shift
        bitcoind.simple_reorg(vault["blockheight"])
        for w in revault_network.participants():
            w.wait_for_logs(
                [
                    "Detected reorg",
                    # 7 because simple_reorg() adds a block
                    f"Vault deposit '{deposit}' still has '7' confirmations",
                ]
            )

        # Now actually shift it (7 + 1 - 3 == 5)
        bitcoind.simple_reorg(vault["blockheight"], shift=3)
        for w in revault_network.participants():
            w.wait_for_logs(
                [
                    "Detected reorg",
                    f"Vault deposit '{deposit}' ended up with '5' confirmations",
                    "Rescan of all vaults in db done.",
                ]
            )
            wait_for(lambda: len(w.rpc.listvaults(["unconfirmed"], [deposit])) == 1)

        # All presigned transactions must have been removed from the db,
        # if we get it confirmed again, it will re-create the pre-signed
        # transactions. But they are the very same than previously to the
        # signatures on the coordinator are still valid therefore the signature
        # fetcher thread will add them all and the vault will be back to 'secured'
        # again
        bitcoind.generate_block(1)
        for w in revault_network.participants():
            w.wait_for_secured_vaults([deposit])

        # TODO: eventually try with tx malleation

        # Now do the same dance with the 'active' status
        revault_network.activate_vault(vault)
        bitcoind.simple_reorg(vault["blockheight"] + 3)
        for w in revault_network.participants():
            w.wait_for_logs(
                [
                    "Detected reorg",
                    # 7 because simple_reorg() adds a block
                    f"Vault deposit '{deposit}' still has '7' confirmations",
                ]
            )
        bitcoind.simple_reorg(vault["blockheight"] + 3, shift=3)
        for w in revault_network.participants():
            w.wait_for_logs(
                [
                    "Detected reorg",
                    f"Vault deposit '{deposit}' ended up with '5' confirmations",
                    "Rescan of all vaults in db done.",
                ]
            )
            wait_for(lambda: len(w.rpc.listvaults(["unconfirmed"], [deposit])) > 0)
        bitcoind.generate_block(1)
        for w in revault_network.participants():
            w.wait_for_active_vaults([deposit])

        # If we are stopped during the reorg, we recover in the same way at startup
        revault_network.stop_wallets()
        bitcoind.simple_reorg(vault["blockheight"] + 3 + 3)
        revault_network.start_wallets()
        for w in revault_network.participants():
            w.wait_for_logs(
                [
                    "Detected reorg",
                    # 7 because simple_reorg() adds a block
                    f"Vault deposit '{deposit}' still has '7' confirmations",
                ]
            )

        revault_network.stop_wallets()
        bitcoind.simple_reorg(vault["blockheight"] + 3 + 3, shift=3)
        revault_network.start_wallets()
        for w in revault_network.participants():
            w.wait_for_logs(
                [
                    "Detected reorg",
                    f"Vault deposit '{deposit}' ended up with '5' confirmations",
                    "Rescan of all vaults in db done.",
                ]
            )
            wait_for(lambda: len(w.rpc.listvaults(["unconfirmed"], [deposit])) > 0)
        revault_network.stop_wallets()
        bitcoind.generate_block(1)
        revault_network.start_wallets()
        for w in revault_network.participants():
            w.wait_for_active_vaults([deposit])

        # Now do the same dance with a spent vault

        # Keep track of the deposit transaction for later use as we'll reorg deeply enough that
        # bitcoind won't add the transactions back to mempool.
        deposit_tx = revault_network.stk(0).rpc.listonchaintransactions([deposit])[
            "onchain_transactions"
        ][0]["deposit"]["hex"]

        # If the deposit is not unconfirmed, it's fine
        revault_network.spend_vaults_anyhow([vault])
        for w in revault_network.mans():
            assert len(w.rpc.listspendtxs()["spend_txs"]) == 1
        bitcoind.simple_reorg(vault["blockheight"] + 3 + 3 + 3)
        for w in revault_network.participants():
            w.wait_for_logs(
                [
                    "Detected reorg",
                    f"Vault deposit '{deposit}' still has .* confirmations",
                    "Rescan of all vaults in db done.",
                ]
            )

        # If it is then we'll mark it back as unvaulting
        bitcoind.simple_reorg(vault["blockheight"] + 3 + 3 + 3, shift=-1)
        for w in revault_network.participants():
>           w.wait_for_logs(
                [
                    "Detected reorg",
                    f"Vault deposit '{deposit}' ended up without confirmation",
                    "Rescan of all vaults in db done.",
                ]
            )

tests/test_misc.py:871:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <test_framework.revaultd.StakeholderRevaultd object at 0x7f9250163fa0>
regexs = ['Detected reorg', "Vault deposit 'eab8103e0f39e79de16caafc3b220acde5f83231d32397d2056f4159c9812148:1' ended up without confirmation", 'Rescan of all vaults in db done.']
timeout = 90

    def wait_for_logs(self, regexs, timeout=TIMEOUT):
        """Look for `regexs` in the logs.

        We tail the stdout of the process and look for each regex in `regexs`,
        starting from last of the previous waited-for log entries (if any).  We
        fail if the timeout is exceeded or if the underlying process
        exits before all the `regexs` were found.

        If timeout is None, no time-out is applied.
        """
        logging.debug("Waiting for {} in the logs".format(regexs))

        exs = [re.compile(r) for r in regexs]
        start_time = time.time()
        pos = self.logsearch_start

        while True:
            if timeout is not None and time.time() > start_time + timeout:
                print("Time-out: can't find {} in logs".format(exs))
                for r in exs:
                    if self.is_in_log(r):
                        print("({} was previously in logs!)".format(r))
>               raise TimeoutError('Unable to find "{}" in logs.'.format(exs))
E               TimeoutError: Unable to find "[re.compile('Detected reorg'), re.compile("Vault deposit 'eab8103e0f39e79de16caafc3b220acde5f83231d32397d2056f4159c9812148:1' ended up without confirmation"), re.compile('Rescan of all vaults in db done.')]" in logs.

tests/test_framework/utils.py:456: TimeoutError

It's not anymore since https://github.com/revault/revaultd/pull/243


Contact

Hello! Would love to talk to you about an AI project. Could you email me at<EMAIL_ADDRESS>:D

I'm busy/not interested. Sorry, closing as offtopic.


instrumentation tests are executed with BUCK

Added ability to run instrumentation tests with BUCK.
This change uses BUCK to build and run instrumentation tests facebook style.
The gains are that we can execute the same tests internally at FB and in OSS.
Also running tests not via graddle:connect command is 1.5 minutes faster.
I'll keep keep an eye on stability Gradle and BUCK builds for a while.

Currently I get these results:
$ buck test ReactAndroid/src/androidTest/buck-runner:react-oss-tests
[-] PROCESSING BUCK FILES...FINISHED 0.2s [100%]
[-] DOWNLOADING... (0.00 B/S AVG, TOTAL: 0.00 B, 0 Artifacts)
[-] BUILDING...FINISHED 3.7s [100%] (174/324 JOBS, 5 UPDATED, 1.5% CACHE MISS)
[-] TESTING...FINISHED 1.7s
RESULTS FOR //ReactAndroid/src/androidTest/buck-runner:react-oss-tests
NOTESTS <100ms  0 Passed   0 Skipped   0 Failed   com.facebook.react.tests (<IP_ADDRESS>:5555)
TESTS PASSED

To execute locally:
./gradlew :ReactAndroid:packageReactNdkLibsForBuck
node local-cli/cli.js bundle --platform android --dev true --entry-file ReactAndroid/src/androidTest/assets/TestBundle.js --bundle-output ReactAndroid/src/androidTest/assets/AndroidTestBundle.js
buck test ReactAndroid/src/androidTest/java/com/facebook/react/tests

Really cool!
@facebook-github-bot shipit

@bestander Failed to land with:
BUILD FAILED: 'Libraries/FBReactKit/js/react-native-github/ReactAndroid/src/androidTest/assets/ScrollViewTestModule.js'
in '//Libraries/FBReactKit:GroupsJS' crosses a buck package boundary.
This file is owned by
'Libraries/FBReactKit/js/react-native-github/ReactAndroid/src/androidTest/assets'.
Find the owning rule that references
'Libraries/FBReactKit/js/react-native-github/ReactAndroid/src/androidTest/assets/ScrollViewTestModule.js',
and use a reference to that rule instead of referencing the desired file directly.

Check out Sandastle.

yep, working on it


Expose setting the location of MESA_DIR/data

Exposes the ability to change where MESA read/writes data files from/to.
Works on #872

Dont merge yet i forget to update the test suite

Can be merged now

Looks fine, merging.


[KBFS-1641] Try to fix hang in TestKeyManagerRekeyAddDeviceWithPromptViaFolderAccess

Also use ErrGroup.
Also plumb context through Shutdown functions.

PTAL, although I'll be likely fixing dokan test errors as you do so.

Looking at this latest test failure, so hold off on reviewing...

Moved the ctx plumbing to https://github.com/keybase/kbfs/pull/610 .


Permission error in ownership of datadir

Hi,
there is a problem in your docker file.
The container will restart continuously.
$ docker logs bitcoin:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE
boost::filesystem::create_directory: Permission denied: "/opt/graphsense/data/blocks"
bitcoin in AppInit()

To fix it is sufficient to add the -R flag in the chown command in the Docker file (line 7):
chown -R dockeruser /opt/graphsense
I'll submit a pull request for this issue

same thing in graphsense/bch-client...

Permissions are set in docker/start.sh


Feature: version info into binary

Add the version info (hash of commit, tag) into binary.

What is the project status? It looks stale

@ccoVeille
Now, I am solving problems IRL :(
I return to linter after 22nd of July.

Take care of yourself


Weird behavior of type checking while object deconstructing

Bug Report
🔎 Search Terms
object deconstructing, type checking
🕗 Version & Regression Information

Version 4.x.x

⏯ Playground Link
Playground link with relevant code
💻 Code
The error messages:
[오후 5:55:30] File change detected. Starting incremental compilation...

src/submissions/submissions.service.ts:97:49 - error TS2345: Argument of type '{ id: number; problem: Problem; problemId: number; user: User; userId: number; time: number; memory: number; language: string; code: string; status: SubmissionStatus; createdAt: Date; } | { ...; }' is not assignable to parameter of type '_QueryDeepPartialEntity<Submission>'.
  Type '{ id: number; problem: Problem; problemId: number; user: User; userId: number; time: number; memory: number; language: string; code: string; status: SubmissionStatus; createdAt: Date; }' is not assignable to type '_QueryDeepPartialEntity<Submission>'.
    Types of property 'problem' are incompatible.
      Type 'Problem' is not assignable to type '(() => string) | _QueryDeepPartialEntity<Problem> | undefined'.
        Type 'Problem' is not assignable to type '_QueryDeepPartialEntity<Problem>'.
          Types of property 'author' are incompatible.
            Type 'User | undefined' is not assignable to type '(() => string) | _QueryDeepPartialEntity<User | undefined>'.
              Type 'User' is not assignable to type '(() => string) | _QueryDeepPartialEntity<User | undefined>'.
                Type 'User' is not assignable to type '_QueryDeepPartialEntity<User>'.
                  Types of property 'submissions' are incompatible.
                    Type 'Submission[]' is not assignable to type '(() => string) | _QueryDeepPartialEntity<Submission>[] | undefined'.
                      Type 'Submission[]' is not assignable to type '_QueryDeepPartialEntity<Submission>[]'.
                        Type 'Submission' is not assignable to type '_QueryDeepPartialEntity<Submission>'.
                          Types of property 'user' are incompatible.
                            Type 'User' is not assignable to type '(() => string) | _QueryDeepPartialEntity<User> | undefined'.
                              Type 'User' is not assignable to type '_QueryDeepPartialEntity<User>'.
                                Types of property 'permissions' are incompatible.
                                  Type 'SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<AnyObject>>[] | undefined' is not assignable to type '(() => string) | _QueryDeepPartialEntity<SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<...>>[] | undefined>'.
                                    Type 'SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<AnyObject>>[]' is not assignable to type '(() => string) | _QueryDeepPartialEntity<SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<...>>[] | undefined>'.
                                      Type 'SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<AnyObject>>[]' is not assignable to type '((() => string) | _QueryDeepPartialEntity<SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<...>>> | undefined)[]'.
                                        Type 'SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<AnyObject>>' is not assignable to type '(() => string) | _QueryDeepPartialEntity<SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<...>>> | undefined'.
                                          Type 'SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<AnyObject>>' is not assignable to type '_QueryDeepPartialEntity<SubjectRawRule<Actions, ExtractSubjectType<"Submission" | "User" | "Problem" | "Workbook" | "Contest" | "Board" | "Article" | "Comment" | "all">, MongoQuery<AnyObject>>>'.
                                            Types of property 'conditions' are incompatible.
                                              Type 'MongoQuery<AnyObject> | undefined' is not assignable to type '(() => string) | _QueryDeepPartialEntity<MongoQuery<AnyObject> | undefined>'.
                                                Type 'MongoQuery<AnyObject>' is not assignable to type '(() => string) | _QueryDeepPartialEntity<MongoQuery<AnyObject> | undefined>'.
                                                  Type 'MongoQuery<AnyObject>' is not assignable to type '_QueryDeepPartialEntity<MongoQuery<AnyObject>>'.
                                                    Types of property '[ɵvalue]' are incompatible.
                                                      Type 'MongoQueryFactory | undefined' is not assignable to type '(() => string) | _QueryDeepPartialEntity<MongoQueryFactory | undefined>'.
                                                        Type 'MongoQueryFactory' is not assignable to type '(() => string) | _QueryDeepPartialEntity<MongoQueryFactory | undefined>'.
                                                          Type 'MongoQueryFactory' is not assignable to type '_QueryDeepPartialEntity<MongoQueryFactory>'.
                                                            Types of property 'produce' are incompatible.
                                                              Type 'MongoQuery<unknown>' is not assignable to type '(() => string) | _QueryDeepPartialEntity<MongoQuery<unknown>> | undefined'.

 97     await this.submissionsRepository.update(id, {
                                                    ~
 98       ...submissionParams,
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
 99       // ...({} as any),
    ~~~~~~~~~~~~~~~~~~~~~~~~
100     });
    ~~~~~

[오후 5:55:30] Found 1 error. Watching for file changes.

🙁 Actual behavior

🙂 Expected behavior
Why those two codes result different?
If the property with unknown type is the problem, both should be invalid code. But it doesn't.
By adding ...(something as any) I could solve the error but I can't understand.
Is this valid operation? or a bug?

When spreading any the resulting expression will be any as well, meaning any type check is disabled. This works as intended.

Sorry, it was object spreading. That means I should find the other things to fix the error. Thank you!


Oracle-11 eventstore and saga code contains possible resource leaks

Oracle11Utils, Oracle11EventTableFactory, and Oracle11SagaSqlSchema don't close all statements that create tables/triggers/sequences.

FYI: this issue relates to #852.


Getting files C++ compilable

Getting files C++ compilable - Adding pointer conversions, changing variable and type names.

Jenkins: test this please

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

BTW, what are the strange commits at the top of this PR? There seem to be commits from Mark and others that are unrelated.  Looks to me like your branch base is questionable; can you rebase this to master?

I was trying out git rebase -i. So it intermingled some of the merges. Fixed it.

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

Known issues : #11737, (also the fixed INT_MAX issue in flow_control.c)

_t names are reserved for the language and system libraries afaik... Can we change this to use something else?

Can change it to explicitly use _type or _enum or something else. What do you suggest?

_type or _enum would be fine: my expectation is that we'll rename these
again once we start c++-ifying the codebase, but until then we should stay
within spec and the existing style guide.
On Wed, Sep 13, 2017 at 8:44 AM Yash Tibrewal<EMAIL_ADDRESS>wrote:

Can change it to explicitly use _type or _enum or something else. What do
you suggest?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/12499#issuecomment-329209572, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJpudcX8fz_qqvXt-oO0q9cPdftgT2xVks5sh_hMgaJpZM4PT8Wd
.