DatePicker: Not disabling dates out of range after a selection is made

Detailed description

Describe in detail the issue you're having.

No dates selected / set in the date picker:

You can see which dates are allowed to be selected as expected and user can select them

The moment a single selection is made the disabled date options look enabled even though the component doesn't let you select them. This is very confusing for a user who no longer knows what the valid range for selection is anymore.

Is this a feature request (new component, new icon), a bug, or a general issue?

Bug

Is this issue related to a specific component?

Date Picker

What did you expect to happen? What happened instead? What would you like to see changed?

Expect the disabled dates to remain disabled when the user is making a selection, has made a selection or is attempting to change their selection.

What browser are you working in?

Chrome

What version of the Carbon Design System are you using?

Latest. See Reproduction

What offering/product do you work on? Any pressing ship or release dates we should be aware of?

CS360 + others. We are opting to not use this component for the time being but would've liked to.

Steps to reproduce the issue

https://github.com/virkt25/carbon-ng-demo

Also for the date range picker I feel like the behaviour needs to be modified to be more intuitive for users.
If a user is trying to make a new selection they should be forced to select both options again. A good example of this can be seen in this demo (which is also using flatpickr). https://mattlewis92.github.io/angularx-flatpickr/

There may be some changes in the carbon flatpickr plugins that we haven't picked up yet ... It would be ideal if those were exposed as a package 🤔

Anything preventing the update to the latest version of flatpickr / associated plugins?

Unsure ... That's something we definitely should look into though. The Carbon plugins aren't exposed as a package yet (IIRC), so I may take a stab at that first and try integrating them here.

I think this may been resolved in the latest version, does the error still come up on v4.10.1 @virkt25?

Per Doni's comment, it looks like it's been resolved in one of the later versions. Feel free to reopen with more info if needed.

Per Doni's comment, it looks like it's been resolved in one of the later versions. Feel free to reopen with more info if needed.


How does the engine construct table schemas based on the data?

When you write data from your dataflow to the Azure SQL enhanced compute engine, presumably it's creating the schema based on data samples?
Can you write a little more about how the system creates the schema? What if a text column in your first 1,000 rows only has 5 character strings, but later columns have 7 character strings? Can we explicitly set the schema of the tables?

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

ID: 71265a0f-32b6-7cf3-7daa-3b523aa556a5
Version Independent ID: da1e7392-ea68-65c7-916e-89e0d9974dc5
Content: Premium features of dataflows - Power BI
Content Source: powerbi-docs/transform-model/dataflows/dataflows-premium-features.md
Service: powerbi
Sub-service: pbi-dataflows
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Hi, @kthejoker  -- thanks for your question! Assigning to the author for consideration.

Hi, @kthejoker  -- thanks for your question! Assigning to the author for consideration.


Performance testing

We want the following performance data to be available for each release:

Single threaded transactions per second.
With and without JITter.
With and without signature verification (since verification will be done in parallel in the future this gives us an idea of what will be achievable then)
Above measurements made in single node (no network) and multi-node (two nodes with network) configuration.

ATC:
A report similar to what was produced last time we ran these tests containing the test data and commentary. [We should link to the previous report.]

macbook, clang6, -O3, single node, no signature checking
WAVM: 8000 txn/sec
binaryen: 2700 txn/sec
Linux, Ryzen 1600X, clang6, -O3, two-nodes on same box with full signature checking, binaryen --- 1200txn/sec

Here is a link to the instructions for how to repeat the performance tests such as these: https://gist.github.com/spoonincode/fca5658326837b76fd744d39b2a25b4e


Authentication Problem: "alexa.amazon.es" doesn't work

Hi,
I cannot do the authentication because the web "alexa.amazon.es" redirect to the application...
Could you please help me?
Thank you,
Best Regards.

Anyone have recently logged into Alexa account with Node Red?
I’m facing the issue that login site always asking for scan QR with the App, and when you scan that QR it redirects you to the same “scan QR site” in an infinite loop.
I have tried it sacan QR with the iOS and Android app, both have the same behavior, this happens using the Proxy and Cookie auth method of node-red-contrib-alexa-remote2-applestrudel.
URL https://pitangui.amazon.com/ or https://alexa.amazon.com.mx/ always redirect to the same screen in an infinite loop, even from Proxy Auth URL that Node Palette gives me.
Seems that node red and Alexa Web interface are no longer available for new users


Show help for nested subcommands

https://picocli.info/#_nested_sub_subcommands
By default, the usage help message only shows the subcommands of the specified command, and not the nested sub-subcommands. This can be customized by specifying your own IHelpSectionRenderer for the command list section. The picocli-examples module has an example that shows how to accomplish this.

Done


CDC supoprt for MI using Debezium connector

Problem
Currently the MI doesn't have Change Data Capture (CDC) support. The requirement is to implement a solution for that.
These are the subtasks :

[x] Check for the feasibility to have a CDC in MI, considering its stateless nature
[x] Design and finalise an architecture for CDC in MI
[ ] Implement the CDC support for MI

Affected Component
MI
Version
No response
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Studied on Change data capture and related technologies and about the databases used in MI

Work Log

Checked the following scenario to verify whether Kafka keeps the offset internally :

Configured a Kafka inbound endpoint to MI. Sent messages via a Kafka producer and logged the received message in MI console, along with the offset. The messages were correctly logged in MI terminal in the sent order (last offset was 65)
Stopped the MI instance and sent 2 messages via kafka producer.
When restarted the MI instance, it started from offset 66 and logged the messages for offsets 66 and 67
Another message was produced and it was logged with offset = 68

With the above observations it seems that the offset can be handled within the scope of Kafka, without having an external storage mechanism

Work Log
When analysing the scenario further, it was identified that in the previous Kafka example, offset we identified is the one not coming from Debezium, it's coming from Kafka side which it uses to manage offset in each listener group.
Based on several discussions regarding this,  it was identified that since Debezium is a library rather a server, the offset should be available even in MI restart scenario as well
Meanwhile created a sample Java application connecting Debezium and MySQL

Work Log
Connected the java application which was to listen database events using Debezium, with Kafka,  in a way that it polls the events fired by debezium and mediate them.
Configured WSO2 MI with the kafka inbound endpoint and logged the received events in MI side

Email thread was created with the subject "CDC support to WSO2 Micro Integrator"

Work Log
Completed the design doc with the inbound endpoint parameters
Was blocked in the implementation due to a dependency issue.  Found it was an OSGI related one and could solve it by creating an orbit bundle for debezium with required changes

Update [2023-06-19 to 21] (new rotation)
Since there are continuous set of startup and deployment errors, started working from scratch from a new branch containing recent updates of the master branch
could resolve the initial startup errors. But still there are issues with cdc inbound endpoint deployment.
These are related to debezium and related dependencies.
Since there's no direct way of identifying all dependencies, have to  resolve one by one, based on the error log.
Currently working on it

Update [2023-06-22]
Implemented the logic to handle the events captured by the debezium
This requires further tests

Update [2023-06-23]
Implemented the optional and required parameters to be taken from the inbound endpoint xml file.
Extended the support for listening only to the specified table names and operation names (if provided) and to listen the entire db with insert, update and delete operations as the default behaviour
With this, the PoC is complete

Update [2023-06-26]
Modified the payload and properties to output via the sequence
Following are the sample  json payloads for insert, update and delete operations for the database table ‘marks’ which was created for testing purposes.
Insert
 {
  "before": null,
  "after": {
     "maths": 80,
     "english": 70,
     "id": "s005"
     }
 }

Update
{
    "before": {
       "maths": 80,
       "english": 70,
       "id": "s005"
    },
    "after": {
       "maths": 80,
       "english": 75,
       "id": "s005"
     }
  }

Delete
{
"before": {
   "maths": 80,
   "english": 75,
   "id": "s005"
},
"after": null
}

Apart from the above payload, the database, table, operations, the time at which the connector processed the event will be exposed to the outside as properties via a sequence

Update [2023-06-27]
tested for server shutdown scenarios.
Fixed the issue related to the file name in resuming the event fired when server was down, at a restart.
Added operation into the payload as well
tested for clustered setups. Further testing needs to be done

Update [2023-06-28, 29]
When deploying multiple cdc inbound endpoints or 1 cdc inbound endpoint with set of other inbound endpoints, the deployment stops, when cdc inbound EP is deployed.
Tested listening 2 different tables in two different databases to ensure that the above doesn't occurs due to the default isolation level (Repeatable reads).
Debugged the code to identify the exact place where concurrency get disturbed.

Update [2023-06-30]
Extended the concurrency support for deploying multiple cdc inbound endpoints which listen to

different tables in the same database
different tables in different databases

Update [2023-07-04]
Completed the implementation for securevault support

Update [2023-07-05]
Checked the clustered behaviour for other inbound endpoint types.
In Polling inbound endpoints it's handled by a parameter named "coordination".
In Listening inbound endpoints (tested with an http) it seems that there's no explicit way to handle this other than using a  load balancer.
Hence it requires to decide whether it needs to handle this and a way to handle this

Update [2023-07-06]
Started working on testing the inbound endpoint for postgres.
Identified that there are several parameters that need to be added, which are specific to the DBMS.
Had a discussion regarding the clustered behaviour. It was discussed that although the entire process seems as a listening process, it's more towards a polling. Since it was advised to go ahead as a polling inbound endpoint rather a listening.

Update [2023-07-10]
Completed the implementation for polling mode
Working on testing for clustered scenarios

Update [2023-07-11]
Fixed the issues found while testing clustered scenarios.
Now when one node stops the execution, the other continues from where prev node stopped.
But there are scenarios where the immediate prev event is getting dupplicated by the new coordinator node.
Debezium documentation explains that as follows :
When the Debezium’s systems crash, they are not always able to record their last position/offset. When they are restarted, they recover by starting where were last known to have been, and thus the consuming application will always see every event but may likely see at least some messages duplicated during recovery.

Additionally, network failures may cause the Debezium connectors to not receive confirmation of writes, resulting in the same event being recorded one or more times (until confirmation is received).

https://debezium.io/documentation/faq/#:~:text=position and offset.-,Why must consuming applications expect duplicate events%3F,-When all systems

Update [2023-07-12]
Worked on testing for Kafka storage. the following error occures at the connector startup
 ERROR io.debezium.embedded.EmbeddedEngine - Error while trying to run connector class 'io.debezium.connector.mysql.MySqlConnector'
org.apache.kafka.connect.errors.ConnectException: An exception occurred in the change event producer. This connector will be stopped.
	at io.debezium.pipeline.ErrorHandler.setProducerThrowable(ErrorHandler.java:53)
	at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:116)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: io.debezium.DebeziumException: io.debezium.relational.history.SchemaHistoryException: java.util.concurrent.ExecutionException: org.apache.kafka.common.InvalidRecordException: Compacted topic cannot accept message without key in topic partition h2-0

But seems the above error is unavoidable because there there events from debezium size which comes with a null key and  those are stored by debezium which is not in our control.
Currently looking if a solution can be applied for this

Update [2023-07-13,14,18]
Even though the initial change event is detected, the changes are not detected thereafter in postgres connector setup.
Still trying to resolve it.
Meantime started testing on MSSQL server.

Update [2023-07-19]
completed testing for MSSQL database.

Update [2023-07-20, 21]
Tested for postgress database including

multiple cdc inbound endpoints in same standalone instance
clustered setup

Update [2023-07-26]
Code review was held on Tuesday 25th
Currently working on the modifications suggested

Update [2023-08-07]
Testing for oracle DB is remaining since had issues in all attempts in containerized approaches. Finally tried using the Vagrant-box as well. According to this thread https://github.com/hashicorp/vagrant/issues/13098#issuecomment-1550533339, it is also not supported for M1 machines.
With that it was suggested to handover the Oracle testing to the MI team (need to be done using an Ubuntu machine).
Started working on the documentation

Update [2023-08-08]
Had a discussion today regarding the dependency packing issue. There, was suggested to build the debezium on JDK 11 and if there are no errors, go ahead with creating the OSGI bundle. Further test the scenarios with the new pack.
Orbit PR : https://github.com/wso2/orbit/pull/995
Created the Documentation https://docs.google.com/document/d/1v4OCIFsNpoeyx7gM1Ysggl021WGvCY4KnRljDdtPtwk/edit?usp=sharing

Update [2023-08-09]
Resolved the error of DebeziumEngine Notfound , by adding the METAINF classes of DebeziumEmbedded jar to the orbit bundle.
Tested the clustering/ File storage/Kafka Storage scenarios after replacing the dependencies with an orbit bundle

Update [2023-08-10]
Addressed all review comments in PRs
Tested the final versions of the artifacts using MySQL database.

We need to test this with Oracle.


Add vendor.yml to exclude some folders from Github statistics

Fix the wrong contribution statistics, which makes me scary :)

This doesn't seem to work as I misunderstood this file. I was reading too quickly...


Added key signing for strong-naming the assembly.

Hi @florinszilagyi, thank you for your PR! Unfortunately nuget packages cannot be switched from non-SN to SN.
If you really need strong naming, or a specific use case, this library is only two .cs files - just drop them into your project :smiley:

Oh, damn.
I already did that, thought that maybe it would be helpful to someone else :)
Thanks.


Specify batch Size and Batch Interval for Batch Delete

How can we specify both parameters for the Delete command. I have something like:
_dbContext.Set<T>().Where(predicate).Delete(x => x.BatchSize = 10000);
How can I add BatchDelayInterval as well?
_dbContext.Set<T>().Where(predicate).Delete(x => x.BatchSize = 10000, x => x. BatchDelayInterval = 1000);
doesn't seem to work

Hello @saad749 ,
You must use a statement block
_dbContext.Set<T>().Where(predicate).Delete(x => {
	x.BatchSize = 10000;
	x.BatchDelayInterval = 1000;
});

Let me know if that worked.

Thanks, I will try it tomorrow.

It works perfectly fine. Thank you :)


trust the new initial kubelet client CA

kubelets have clients signed by this short lived cert

/retest

ha proxy flake.


Replace wrench with shelljs

In this pull request for issue #2237 wrench is swapped out for fs-extra due to the deprecation of wrench. Luckily wrench was only used in two places making this a relatively minor pull request.
There has been no change in functionality with regards to delete and copy within files.cljs as a result.
If desired, we can expand the scope of this PR to update all places we use fs to use fs-extra instead. fs-extra contains fs within it...

Please verify everything is hunky dory with regards to npm. After updating package.json, the commands used were:
npm install<EMAIL_ADDRESS>npm uninstall wrench
And the results committed

@sbauer322 Thanks for this PR! Sorry for taking so long to get around to reviewing it.
But do we even need fs-extra? I don't think we do. The shell npm package rm method seems to handle recursive deletes just fine. The existing upgrade code has been using it for three years. Would you mind testing whether we can simply use the shell package methods instead?

Will do! I had chosen fs-extra simply because that is what wrench
suggested.
On Aug 14, 2016 12:33, "kenny-evitt"<EMAIL_ADDRESS>wrote:
@sbauer322 https://github.com/sbauer322 Thanks for this PR! Sorry for
taking so long to get around to reviewing it.
But do we even need fs-extra? I don't think we do. The shell npm
package rm method seems to handle recursive deletes just fine. The existing
upgrade code has been using it for three years. Would you mind testing
whether we can simply use the shell package methods instead?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LightTable/LightTable/pull/2238#issuecomment-239682869,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACzxaojQ-RXDq8iTdaI-Bb51udZ3m2zvks5qf0NFgaJpZM4Jjmdg
.

If we can remove npm dependencies I'm all for that. Funnily I happen to use wrench from a couple of my plugins, but that's obviously of no concern to LT. But it should come as a warning in the release notes. Hopefully there aren't many other plugins that use it.

@sbauer322 Thanks!
@rundis You and other plugin authors can pull in wrench (or any other Node.js package) independently of LT tho – right? Is the potential issue just that removing it from LT core might break plugins that are using it without including it in their own projects themselves?

The latter.
I haven't found anything in the dev docs stating that you shouldn't use the node modules shipping with LT. Maybe it should mention that if you do it's at your own peril, because it's not part of the official "api" for plugins ?

@rundis We should mention that those packages aren't part of the 'official API' – now I'm trying to figure out where best to do that! Any ideas?

@kenny-evitt my preference would be stating this somewhere within for-committers.md, the wiki, and package.json itself as a comment. It is possible to miss if it is only within a single supporting document.

I was able to switch files.cljs to use shelljs instead of wrench. Do note, there is a different library(?) named shell already being used within files.cljs.
Sorry for the list, @kenny-evitt, but there are a couple questions now:

Should we rename what is currently known as shell to something such as electron-shell across the project? It can be easily confused with shelljs if you are not aware of both of them... I know I wasn't! :smile:
Do you want wrench removed as a dependency within LT or leave it? Alternatively, we could deprecate it for future releases and aim to remove it entirely for 0.9 or 1.0?

Tx for your contributions @sbauer322. Much appreciated.
I'd say we go for the following.

remove wrench completely
either rename use of shell to electron-shell as you suggested, or  rename var usagee of shelljs to be named shell-js. Prefer the former.

Should be all set now @rundis, @kenny-evitt!
Wrench has been removed, shell has been renamed to electron-shell and shelljs is now shell

@sbauer322 Please rebase the upstream master onto this branch.

@sbauer322 @rundis I just tested all of the UI features that use any of the affected vars and everything looks good (or as good as it was before these changes). The only issue I noticed was #2129 but Scott already commented that it's still an issue even with the other related changes.
@sbauer322 I'll merge this after you've rebased the upstream master on top of this branch.

@kenny-evitt: I believe I have done what you asked, but full disclosure - I've never used rebase before.
The commands used were:
git checkout replace-wrench-with-fs-extra
git rebase LightTable/master

Could you confirm I did not do something undesired prior? If all is well then merge away!

@sbauer322 I'm not sure what happened. GitHub doesn't show any changes for the 'merge' commit. I think it's okay. Would you squash the three commits as one commit?

I think we are clear to merge now, @kenny-evitt!


How to use API key with this library?

Cannot find any references anywhere?

Hi @peterfigure
google-cloud-java is not a library. All available libraries have individual repos and should be added individually or as a BOM to the project to be used. README of individual libraries have instructions about how to add the particular dependency.
Then follow the instructions to use API keys.

Hope this  answers your question. Closing for now. Feel free to reopen if you have more questions.


Remove version: NCEUFRJ.DosVox version 6.1

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

URL: http://intervox.nce.ufrj.br/dosvox/programas/dv61-setup.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 923)

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 900.)

Close with reason: Duplicate;


add some hints for current IntelliJ IDE setup

as discussed in the cas-dev Google group

Thanks very much!


Ensure linters work inside notebooks

Started this work here:
https://github.com/microsoft/vscode-python/tree/rchiodo/lint_notebooks
Incomplete, need to concat documents so linters can find stuff in other cells. This complicates the whole thing. Linters work on documents so the URI passed down to the actual linter generates diagnostics for the 'document' that is open. We'd need to

Generate a new 'document' that is the concat of all of the cell
Suppress document open for cells and generate one for just the entire notebook
LintingEngine will have to change to allow the diagnostics to be 'un-concated'.


Please add details to the README with changes from stock zgen

I think it's great that you're doing work on a zgen fork (and have added it to the awesome-zsh-plugins list), but I'd like to see what updates you've made so I can consider replacing stock zgen with it in the zsh-quickstart-kit.
Thanks!

Thanks for adding it 👍
Here is a quick list I've done so far:

compiling your sourced scripts
add zgen compile in case you want to recursively compile your dotfiles (manually)
add zgen bin to add an executable to your $PATH
lazy loading zgenom by sourcing zgenom.zsh instead of zgen.zsh

It also merges some pull requests and fixes bugs:

compinit with custom flags wasn't working properly
update to ohmyzsh/ohmyzsh
allow cloning without submodules

This is all done with backwards compatibility in mind. So zgenom shouldn't require you to change anything of your existing zgen configuration.
Things I might add in the future: (somewhat depends on the acceptance and my personal need)

adding to man-pages
conforming to the zsh plugin standard
some sort of zgen cleanup or zgen delete to remove unused plugins.

Hey @unixorn,
I've added this list to the readme.
Do you want me to add some more information?

I see the notes about zgen bin but not zgen compile, otherwise looks good

Added zgen compile. I'll do a rewrite of the readme when I get around to it.
For now everything should be covered 👍

Sweet, thanks.

Please let me know how you decide with zsh-quickstart-kit.
Feel free to post here or create a new issue if there's something missing or you have another question 👍

I did a talk on using the quickstart at work this week and didn't want to mess with it right before the talk. I'll give it a try this weekend, I'd rather be using zgenom since it's getting actively maintained.
Given that a lot of repos are moving to main instead of master, the repo checkout code probably needs a tweak to cope with that sooner rather than later.

My idea was to get the default branch name from GitHub instead of assuming a master or main.

Even better :-)

Now that I'm thinking about it, maybe just clone the repo without specifying a branch unless the user specifies it in the zgen load command. Won't that end up with the repo's default branch?
Then the code wouldn't have to change if the user specifies a bitbucket or other git server besides GH.

I've created an issue for that.
Exactly this was my idea. Then ideally on zgen update I check for those repositories if the default branch has changed and would start using the new branch. (After cloning you can ask a git remote for its head branch)

I didn't know you could query a remote for its head branch, neat!


Modal for date

Discuss whether we should use a modal to announce date. Since there is limited space on mobile, an option to alter the user of what the date for the day is, is to have a modal pop up when they enter the "game" each day.

I think we solved this by creating a space where that information can go on top of where guess goes.


the latest docker image ignore X-Real-IP

nginx config:
location / {
proxy_redirect off;
proxy_pass http://<IP_ADDRESS>:8080;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
}
docker command:
docker run -itd --name=echoip   mpolden/echoip /opt/echoip/echoip -H  X-Real-IP
in another host curl shows the docker gateway IP <IP_ADDRESS>
And I try to run echoip in the host and change proxy pass to http://<IP_ADDRESS>:8080,
curl show the correct remote IP
direct run shows echoip: Trusting remote IP from header(s): X-Real-IP,
and docker not

I have noticed similar issue when running echoip on Kubernetes on Rpi4 and what's strange is that according to logs it looks like -H and several other options aren't supported at all?
# kubectl logs -l app=echoip
  -c string
    	Path to GeoIP city database
  -f string
    	Path to GeoIP country database
  -l string
    	Listening address (default ":8080")
  -p	Enable port lookup
  -r	Perform reverse hostname lookups
  -t string
    	Path to template (default "index.html")

Same problem, but after recreate docker container, it's works, idk how, but works.
My nginx conf:
server {
    include /etc/nginx/options/security.conf;  # some security headers, nvm.
    include /etc/nginx/proxy_params;
    server_name ip.lznet.dev;
    listen 443 ssl;
    location / {
        proxy_pass http://<IP_ADDRESS>:8888/;  # Docker IP in docker0 (bridge-net). And echoip port (8888).
    }
    # <сropped> ssl options.
}

/etc/nginx/proxy_params content:
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

My docker run command:
docker run -itd --name=echoip mpolden/echoip /opt/echoip/echoip -H X-Real-IP -l :8888

The Dockerfile has /opt/echoip/echoip as its entrypoint. See https://docs.docker.com/engine/reference/builder/#entrypoint for what this means. You should use
docker run -itd --name=echoip mpolden/echoip -H X-Real-IP -l :8888.


Add configuration to allow certain attributes

This adds in the attributes that the api returns to us from the truncation of the short bio. @jayzes not sure if we need to add more of these, but I think we are good based off of the defaults: https://github.com/bevacqua/insane#defaults.

👍

FWIW, here are our inbound sanitizer rules: SANITIZER_RULES = {
elements: %w(a b i strong em br),
attributes: { 'a' => %w(href) },
protocols: { 'a' => { 'href' => %w(http https mailto) } },
remove_contents: %w(script embed object style),
}.freeze


Add inputDerivation to enable binary caching

Same rationale as upstream, see
https://github.com/NixOS/nixpkgs/pull/95536

Sorry, I should have reacted earlier; this change is not needed. Unlike upstream's mkShell, mkNakedShell was designed to be built or loaded as a nix-shell. This was part of the design, so you can nix-build the devshell, which has references to all the inputs. So instead of nix-build shell.nix -A inputDerivation | cachix push, you can already nix-build shell.nix | cachix push.

Ok, let me know if you can build a repro

I'm going to assume that it was fine :)


How to determine which branch of a union was used

I've a schema that wraps a record type in a union that all have the same layout. They only differ on record name.
For instance:
Added { payload: Record}
Deleted { payload: Record}
Updated { payload: Record}
I can parse these records and that gives me a Union(Record[payload: Record]) but i can't find a way to determine if it's added, delete or updated.
Is this a limitation of the library and, if so, what do you think about adding a reference to the schema or schema name to the Record struct to make this possible? An alternative would be to add the index of the branch to Union so i can resolve it myself using the reader schema (a bit less user friendly but this won't cause any ownership issues so it might be easier to implement)
Both options may break serde deserialization as well i guess. Any ideas about that?

This looks like one of the recurring issues we've had reported, and still have no fix for this (yet!), after a few attempts :(
Issues #61 #95
Previous attempt #90
Let me know if you were referring to something else. 🙂
If you want to have a go at this, I'd be happy to review it any time you have something (even if not complete)! If not, I'll give it a go later on.
Regarding the implementation, I think adding the index in the Record would be a decent solution. We wouldn't have to deal with lifetime/cloning shenanigans, and we should have all the building blocks ready for that (albeit quite a lot of work is required to make it happen 😄)

decode.rs
encode.rs.
UnionSchema currently only supports one Record per schema, so the code from #90 should be a good inspiration to make this implementation work.

How about using a dedicated enum as follows:
struct Record;

struct Added {
    payload: Record,
}

struct Deleted {
    payload: Record,
}

struct Updated {
    payload: Record,
}

enum UnionOperation {
    Added(Added),
    Updated(Updated),
    Deleted(Deleted),
}

@flavray
No, i think that's the same issue. Sorry about that :)
Thanks for the pointers. That'll be very useful.
I'd like to take a stab at this but i intend to wait until https://github.com/flavray/avro-rs/pull/99 is merged. If i can do something to help there please let me know.
@lerouxrgd
This is indeed how i intend to deserialize this into a rust type but the problem I'm running into now is that the intermediate model (the Value::Union and Value::Record specifically) do not contain the information that would be needed to create to right branch of my enum so that i want to change first.
I assume that I'll also need to change the serde deserialization code to use the additional information added to Union or Record to get that working.
I think I can either match the avro record name to the rust enum branch name or use something like
#[serde(tag = "recordName")] (as described here https://serde.rs/enum-representations.html) if the rust name doesn't match the avro name. My schema contains fully qualified names for instance that I'd like to support.


Sailsjs with nodejs apps (React-Native and Electronjs)

Sails version: 0.12.14
Node version: 6.11.1
NPM version: 5.3.0
DB adapter name: N/A
DB adapter version: N/A
Operating system: macOS Sierra 10.12
I am experiencing a concrete technical issue on making sails socket work on nodejs apps especially react-native, i have tried everything i can but i get an error that socket was unable to connect..
I have already searched for related issues and found a related_closed_issue https://github.com/balderdashy/sails/issues/3687 but unfortunately i tried and gave me errors
I can provide steps to reproduce this issue that others can follow
My environments
Environment:
  OS:  macOS Sierra 10.12
  Node:  6.11.1
  Yarn:  1.3.2
  npm:  5.3.0
  Watchman:  4.9.0
  Xcode:  Xcode 8.3.3 Build version 8E3004b
  Android Studio:  2.3 AI-162.4069837

Packages: (wanted => installed)
  react: 16.0.0-beta.5 => 16.0.0-beta.5
  react-native: 0.49.3 => 0.49.3

steps i did..

created new react-native project just by react-native init projectname
installed socket.io-client and sails.io.js
in my home screen file i just initialized socket.io-client and sails.io.js while i had sails running on localhost:1337 and socket is working on browser as expected as shown below

also in my react-native app i just added these lines..
var socketIOClient = require("socket.io-client");
var sailsIOClient = require("sails.io.js");
var io = sailsIOClient(socketIOClient);
io.sails.useCORSRouteToGetCookie = false;
io.sails.url = "http://localhost:1337";

I am using android emulator and when i debugged i got an error as shown below

I have even tried to use sails.config.sockets.beforeConnect to allow every connection as following but fails to the same errors as above ..
beforeConnect code
  beforeConnect: function(handshake, cb) {
  //   // `true` allows the connection
    var id = '/#'+handshake.headers.cookie.split(';')[0].replace(/^io=/,'');
    sails.log('socketid '+id);
    return cb(null, true);
  //
  // // (`false` would reject the connection)
  },

I am stuck..
I also tried on new electronjs app(desktop app) but gave the same errors... it means sails in socket connection with nodejs apps fails
i even try to move sails server side to online ( not to use localhost ), i lifted there, changed details on react-native and electronjs app but when i tested i got the same errors..

ok, fixed!

I have totally gave up using sails.io in a react native project sorry.
Currently I'm doing a simple XMLHttpRequest polling and in the future I'll probably use Mqtt protocol for that.

Hm, I've definitely used sails.io.js and socket.io.js on an Electron app using the latest version of sails.io.js that ships with Sails 1.0, though I haven't tried it with React-Native.  The "Error: websocket error" message is never very informative.  @pepya2 out of curiosity have you tried on an iOS device, or only Android?

@sgress454 i tested on both simulators (Android and iOS). I am afraid using sails 1.x on production for my client's project since it is not yet officially released as today (20/Nov/2017).

I've heard that React Native is not shiped with node while electron might be and this is why it does not work with react native.
I've succeded in making it work in dev mode (backed by the react native node server) but it never worked in release mode.
There is native library that wraps socket io, you should look at them.
Be aware that I've also had troubles with connection being closed when device is offline (eg. airplane mode).


Implement version, feature_request and report_bug

version - Respond with the current version of the extension running.
feature_request - Respond with link to the issues page with new feature label added, or at least filtered for.
report_bug - Respond with link to the issues page with bug label filter applied.

Maybe combine feature_request and report_bug into report_issue that just responds with a link to the new issue page.


add support for markdown_it_py backend.

scaffold 0.7.0
Bump version: 0.7.0.dev0 → 0.7.0.dev1
ruff autofix
ruff
changelog
format with black
format with black
sort with ruff
Bump version: 0.7.0.dev1 → 0.7.0.dev2
setup for using md-it
kick the details over
use md-it
fix doc syntax
implement md-it details plugin
let black control line length issues
reflect admonition style on details/summary
match admonition style on details/summary
pointer on hover for summary
create source admonition
create details + open by default
style scrollbars
use jinja for docs
fix syntax error
show copy button
strip some chars
formatting
make light mode look ok
sticky the titles

closes #144


Domain activation is Failed - [BRIEF DESCRIPTION]

App Id: d3g7w66oil1mif
Region: ca-central-1
Step: Domain activation
Status: Failed
Issue/question
It wasn't able to validate the domain because of the CNAME.
I had configured it before. So I was trying to use Route53 to do some tests. I deleted the domain I had set and when I try to recreate it the issue starts to say I have a CloudFront set. Because I cannot see anything on CloudFront (because it was created automatically by the Amplify, I guess) I cannot manually delete it to make the setup.
Error message
One or more aliases specified for the distribution includes an incorrectly configured DNS record that points to another CloudFront distribution. You must update the DNS record to correct the problem. For more information, see https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html#alternate-domain-names-restrictions

Didn't see your cname attached to any distribution. Can you simply retry?

Sorry but I try to retry and still have the problem. I cannot see in any
place on AWS the old setup so I can remove it. There is anything I can do?
On Mon., Aug. 3, 2020, 08:20 Gary Lee<EMAIL_ADDRESS>wrote:

Closed #901 https://github.com/aws-amplify/amplify-console/issues/901.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-console/issues/901#event-3616405216,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAITAKTIRQ5PCVBFCALFVRTR63ITPANCNFSM4PIEWE2Q
.


Making Redis password protected

Description
Currently default openwhisk (apigateway) setup doesn't secure Redis with password.
This PR adds password protection to Redis ansible
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[x] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

Codecov Report

Merging #4108 into master will decrease coverage by 4.94%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4108      +/-   ##
==========================================
- Coverage   85.98%   81.04%   -4.95%
==========================================
  Files         148      148
  Lines        7122     7122
  Branches      434      434
==========================================
- Hits         6124     5772     -352
- Misses        998     1350     +352

Impacted Files
Coverage Δ

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-95.54%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-92.6%)
:arrow_down:

...whisk/core/database/cosmosdb/CosmosDBSupport.scala
0% <0%> (-83.34%)
:arrow_down:

...abase/cosmosdb/CosmosDBArtifactStoreProvider.scala
0% <0%> (-62.5%)
:arrow_down:

...penwhisk/core/database/cosmosdb/CosmosDBUtil.scala
92% <0%> (-4%)
:arrow_down:

...rg/apache/openwhisk/common/ForcibleSemaphore.scala
92.3% <0%> (+3.84%)
:arrow_up:

Continue to review full report at Codecov.

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

@dgrove-oss can you take this?

Agree we should add the same password functionality to additional deployments, but that will take PRs to other repos:

Kubernetes: incubator-openwhisk-deploy-kube
Docker-composer: incubator-openwhisk-devetools

PG1 3689 -- looks fine

PG3 3111 🔵


How to obtain the results in the teaser?

hi~ first of all, thanks a lot for your awesome work and open-source codes.
It seems that predict_landmarks.py only produces the landmarks.
How to obtain the transfer results in the teaser, namely the rendered faces given the reference art works?

really would love to know this as well!

The provided a function called "create_img_with_landmarks " in logging_functions.py, which works well for me. But these need some adaptation:

remove parameter "image_size" and "scale" and corresponding codes in that function
open the input image as a NumPy array, convert "pred_lms" to NumPy array and pass them to the adapted function
save the returned result

The provided a function called "create_img_with_landmarks " in logging_functions.py, which works well for me. But these need some adaptation:

remove parameter "image_size" and "scale" and corresponding codes in that function
open the input image as a NumPy array, convert "pred_lms" to NumPy array and pass them to the adapted function
save the returned result


Unexpected current sequence(Version: [1.5.0])

Issue Description
My xrp account on testnet has set wrong sequence.
Transactions from the account in the picture below is less than ten, however, its current sequence is 7,114,878(maybe related to ledger index?).

Steps to Reproduce
I guess accounts created after few days ago is facing this problem.
Expected Result
Account sequence should be set appropriate value.
Actual Result
Account sequence has set unexpeceted value.
Environment
My wallet node is running rippled v 1.5.0 on amazon linux2.
Supporting Files
I found the same issue is going on the acccounts below.
rQr34nTtPBhXPhn2onx7TMc7AZKjZi86YU
rKrXXbGjsUuKUhAkm4dQxd7UN1iJyTvxU6
r4BmT8s9Yb3X3cJMgFZQghecSXcmA5LvyL

@shota-hizawa this is by design since we now have activated  DeletableAccounts via Amendment: "With this amendment, new accounts start with their Sequence numbers equal to the Sequence number matching the index of the ledger in which the account is created. " For more information, see here: https://xrpl.org/known-amendments.html#deletableaccounts

For details about getting ready for Deletable Accounts, see the blog post: https://xrpl.org/blog/2020/get-ready-for-deletable-accounts.html

@carlhua @intelliot
Thank you for quick response! I close this issue.


nuget ver 0.5  appsetting PreferredNetworks not work

set  PreferredNetworks 192.168.0 , the client log is
Sending HTTP request PUT http://<IP_ADDRESS>:8848/nacos/v1/ns/instance/beat?serviceName=DEMO-USER-SERVICE&beat={"port":5050,"ip":"<IP_ADDRESS>","weight":100.0,"serviceName":"DEMO-USER-SERVICE","cluster":null,"metadata":{"preserved.register.source":"ASPNET_CORE"},"scheduled":true,"period":0,"stopped":false}&namespaceId=e37a2391-aa65-4774-9c21-c1a11e4523ce&ephemeral=True&groupName=aicloudview-dev-group&app=MicroService
use the github source code is correct
Sending HTTP request PUT http://<IP_ADDRESS>:8848/nacos/v1/ns/instance/beat?serviceName=DEMO-USER-SERVICE&beat={"port":5050,"ip":"<IP_ADDRESS>","weight":100.0,"serviceName":"DEMO-USER-SERVICE","cluster":null,"metadata":{"preserved.register.source":"ASPNET_CORE"},"scheduled":true,"period":0,"stopped":false}&namespaceId=e37a2391-aa65-4774-9c21-c1a11e4523ce&ephemeral=True&groupName=aicloudview-dev-group&app=MicroService

@dazhu6666 Thanks for your interest in this project.
We will release v0.8.0 to fixed this bug later this week.

v0.8.0 was released to nuget.
Please have a try with it.


Sorting on empty result set display "strange" message

Let's say I have a data view query like the following:
~~~dataview
list
from #type/book and #type/non-existent-tag
sort file.name
~~~

...which returns no results. Dataview displays the following "strange" message:
Dataview: Every row during operation 'sort' failed with an error; first three:
This is something new. It used to just say something like "0 rows returned".
Here are my data view settings: https://d.pr/i/fXvD8X+
Here is the version: https://d.pr/i/8CRYlD+

I believe I corrected this issue in 0.4.1 - does it persist if you restart Obsidian?


Track IR gaze mouse option not there

I'm having trouble getting the Track IR to work with the precision gaze mouse.
"Choose “GazePlusMouse” in the titles tab and set it to use the One:One profile."
This doesn't seem to be an option available. I'm curious if you have do something to trackir to make it an option? If anyone uses the trackir with the precision gaze mouse I would appreciate hearing how you set it up.
I've been able to get the precision gaze mouse to work with both the tobii eye tracker and the enableviacam, but i'd prefer to use the track ir if possible.
Thanks!

Did you remember to refresh or download the latest set of titles?


docs: Update .net framework docs with metrics info

Took me quite a while to find this information buried on Microsoft's website, so explicitly calling out the package needed for metrics support in legacy .net.

Thanks @cedstrom , @open-telemetry/dotnet-approvers please take a look!


[INTERNAL] Update supported node/npm engines

Update support to ^16.18.0 || >=18.0.0.

Coverage remained the same at 94.717% when pulling 596d9992a2edc577e232ec87a80631026440f33c on update-node-engines into 4ac45938d45b224f76d23a2bf5f192794dbe57b3 on main.


Define RADON errors for signaling that Data Requests cannot be relayed

In the incoming bridge design it will be possible that data requests cannot be relayed due to different reasons:

data request is not accepted by the Witnet client due to invalid parameter (e.g. exceeds maximum number of witneseses)
data request parameters exceed a bridge-operator-defined threshold (e.g. collateral) --> mitigates funds drainage and attacks
data request result length exceeds a bridge-contract-defined limit (in bytes) --> limits funds drainage

This issue should include the new definition of those RADON errors in witnet-rust, but also in the Witnet.sol contract.

Done in #158


URL builder for Blob service.

This includes URL builder for shared usage as well.

done in https://github.com/Azure/azure-sdk-for-cpp/pull/144


Support github access tokens

Access tokens Are a necessity for users who have Two-Factor-Authentication enabled.
They should be Available to be used instead of a password, perhaps taken from an environment variable automatically

Thanks for the suggestion! I'm completely on board with using 2FA - however, in this particular case, it's not clear where a 2FA token is required. The only repository that is accessed by the beeware tool is the briefcase template, which is a public repository. Where are you seeing issues with 2FA requirements?

It seems I've misunderstood, the username/password arguments for main.py are for what user?

Aargh - my apologies! I misread the repository name where you reported this issue!
You're absolutely right - 2FA handling may be required, depending on how you use/deploy Beefore. It's less significant for Beeware itself; we use a robot user account that doesn't have 2FA enabled. However, other uses may well need 2FA handling.


[FEATURE REQUEST] Days of Buffering REPORT

Is your feature request related to a problem? Please describe.
I'd like to see how long my savings will last if I lost my income (or it significantly decreases). Days of buffering partially covers this, but it lacks necessary configuration options (e.g. include tracked account, or don't include some accounts, exclude some categories from avg expenses calculations, etc)
Describe the solution you'd like
New report seem like ideal solution to me. It should have our common report options (categories, accounts, dates) and use them to calculate average spending. In addition to that it will be great to have options to:

Select which account balances should be included in DoB calculations, including tracked (i.e. off-budget) accounts (e.g. exclude pension accounts, etc)
Select expected income: regular (X$ per month/week/quarter/etc), one-time (X$ at October 22, 2024), and maybe % from account balance
Select what to use as avg monthly expenses: fixed value or calculate it based on past transactions
Add expected one-time expenses at certain dates

Describe alternatives you've considered
Doing calculations on paper/spreadsheets
Additional context
I'll take care of implementing this feature. Though I'd appreciate feedback from community and if you'll find such report useful

I am glad that someone has already realized this issue.
My understanding of Days of Buffering is that it indicates a disaster backup. Under this situation, transactions moved into tracked accounts like investment activities should not be counted since we wouldn't make investments in an emergency period.


MINOR: Fix issue where the Trogdor Coordinator tracks its own node as an agent

The Trogdor coordinator would erroneously think that every node in the defined topology is an Agent and check its /agent/status endpoint. Since the Coordinator is defined in the topology, it would send requests to itself on a typically invalid default port which only timed out

cc @cmccabe for reviews

This PR is unfortunately not correct.  There's no problem with the coordinator node also having an agent on it.  The coordinator will not track its own node as an agent node unless someone set the port to a non-zero value.  The logic is here:
    TaskManager(Platform platform, Scheduler scheduler, long firstWorkerId) {
        this.platform = platform;
        this.scheduler = scheduler;
        this.time = scheduler.time();
        this.tasks = new HashMap<>();
        this.executor = Executors.newSingleThreadScheduledExecutor(
            ThreadUtils.createThreadFactory("TaskManagerStateThread", false));
        this.nodeManagers = new HashMap<>();
        this.nextWorkerId = firstWorkerId;
        for (Node node : platform.topology().nodes().values()) {
            if (Node.Util.getTrogdorAgentPort(node) > 0) {
                this.nodeManagers.put(node.name(), new NodeManager(node, this));
            }
        }
        log.info("Created TaskManager for agent(s) on: {}",
            Utils.join(nodeManagers.keySet(), ", "));
    }

Is it possible that you accidentally set the agent port to a nonzero value in the configuration, even though there is no agent running?

It does track in common scenarios because Node.Util.getTrogdorAgentPort(node) > 0 is true when the agent port is not set.
public static int getIntConfig(Node node, String key, int defaultVal) {
            String val = node.getConfig(key);
            if (val == null) {
                return defaultVal;
            } else {
                return Integer.parseInt(val);
            }
        }

        public static int getTrogdorAgentPort(Node node) {
            return getIntConfig(node, Platform.Config.TROGDOR_AGENT_PORT, Agent.DEFAULT_PORT);
        }

That is a good point.  The best solution is probably to default trogdor.agent.port to 0 if trogdor.coordinator.port has been set to something non-zero.
Please keep in mind that running both a coordinator and an agent is absolutely a supported configuration (for example, on a single-node test cluster).

Thanks, I hadn't thought of that scenario.

The best solution is probably to default trogdor.agent.port to 0 if trogdor.coordinator.port has been set to something non-zero
I fear this would not solve the case where the Coordinator is ran on the node with the default port (no coordinator port set).

I think my latest commit addresses both scenarios

I'm wondering what would be a better way to catch this issue. This change can have the nasty side effect where an agent running on the same node without an explicitly set port may stop getting health checks from the coordinator

One approach I came up with: we could stop supporting default ports for the coordinator. That way, when an agent starts up it could detect whether a coordinator is intended to be ran on that node and not start up if its own agent port is not configured.


to show placeholder in case of multiple

Please mark the options you have done, before open this Issue. We'll prioritize the issues that are consistent and completed.

[x] I've read the documentation on http://leocaseiro.github.io/angular-chosen.
[x] I've searched on github issues and stackoverflow before open this issue.
[x] I've tested with the angular native select input without the chosen directive
[x] I've tested with the oficial jquery chosen without the angular chosen directive

Please, post your plunker link here:

(plunker link goes here)

If you need a starter plunker for a single select, use this one: https://plnkr.co/edit/Ec9l1C?p=preview
If you need a starter for a multiple select, use this one: https://plnkr.co/edit/vaRw1x?p=preview
Write your issue:
PLEASE ADD THIS INTO YOUR DOCUMENTATION TO SET DEFAULT PLACEHOLDER FOR MULTIPLE CHOOSEN
'
<
select chosen multiple ng-model="location_filter" ng-options="s.cust_location for s in location_name" data-placeholder="LOADING LOCATION" data-placeholder-text-multiple="'SELECT LOCATION'">
 SELECT LOCATION
'

"'

 SELECT LOCATION

'"

Hi @firdousalam, thanks for open this issue, but it's already there http://leocaseiro.github.io/angular-chosen/#chosen-options


Override standard state change of a ng-admin view

Hello,
The problem I have is closed to #678 but cannot be solved by restangular.
I basically want to change the default state a view is going to after performing an action. For instance once a CREATE is done, nh-admin redirect to the editionView of the newly created objects.
In my use case I create an objectX, which in server side trigger the creation of several objects Y & Z.
I want once it has been created, redirect to object Y
I have managed to do so by configuring objectX like so
var objectX= admin.getEntity('objectX');
objectX.creationView()
.title('New Object X')
.fields([
nga.field('id').validation({ required: true}),
nga.field('title').validation({ required: true}),
.....
])
objectX.editionView().fields(objectY.editionView().fields());
objectX.editionView().url(function() {
return +entityId;
});
this work okish, but the displayed URL remain in the form
.../objectX/edit/entityId
Is it possible to do this in a cleaner way by overriding the routing one only on the objectX.creationView() ?
Thanks

Can't you override the routing by setting a ui-router decorator, as explained here?

Thanks for the suggestion. i will investigate this path to ovveride what is defined in ng-admin routing.js and get back to you.
If successull it may be interesting to add an example to the documentation

No news for some time, closing.

No problem. We have not planned to investigate this as the work around prove enough for the moment. I will update the issue when investigated.
Thanks for the help

Le 29 oct. 2015 à 10:01, "Francois Zaninotto"<EMAIL_ADDRESS>a écrit :
No news for some time, closing.
—
Reply to this email directly or view it on GitHub.


re.h: No such file or directory

When I am using $ sudo make install command in Ubuntu, I am getting this error
fatal error: re.h: No such file or directory.
I am using android studio

I have download baresip, re and rem latest. It resolve my problem.


Argument parsing for h3ToGeo, h3ToGeoBoundayr, geoToH3

Continues from #224 to rewrite argument parsing for these three filter applications.

Coverage remained the same at 100.0% when pulling 2b5bd7b40c8e3e4375347c88e64f2bbead8312e2 on isaacbrodsky:args-h3-to-geo into eaecb5c37bd9ef6ccd685d2daa0c571bae6c9275 on uber:master.


AttributeError: 'deeptrack.deeplay' has no attribute 'Model' and RuntimeError with channel mismatch

I downloaded the 03. distinguishing_particles_in_brightfield_tutorial.ipynb from the tutorial and ran it locally. However, I encountered the following error when executing the code:
model = dl.Model(
    net,
    train_data=data_pipeline,
    val_data=data_pipeline,
    loss=dl.torch.nn.CrossEntropyLoss(),
    optimizer=dl.Adam(lr=1e-3),
    metrics=[tm.F1Score(task="multiclass", num_classes=3)],
)

AttributeError: module 'deeptrack.deeplay' has no attribute 'Model'

To resolve this, I modified the code to use dl.Regressor instead of dl.Model:
model = dl.Regressor(
    net,
    loss=dl.torch.nn.CrossEntropyLoss(),
    optimizer=dl.Adam(lr=1e-3),
    metrics=[tm.F1Score(task="multiclass", num_classes=3)],
)

This works, but then I encounter another error when executing the following code:
input_image, target_image = data_pipeline.batch(4)

predicted_image = model.predict(input_image.astype(np.float32)).softmax(1)

RuntimeError: Given groups=1, weight of size [32, 1, 3, 3], expected input[4, 128, 128, 1] to have 1 channels, but got 128 channels instead

My pytorch version is 2.2.1 and python version is 3.11.5.

Is my modification to use dl.Regressor instead of dl.Model correct? If yes, how can I handle the RuntimeError related to channel mismatch in the following code?
In the deeplay tutorial, it's mentioned that the .fit() method handles training, validation, and logging, and also selects the best device (GPU if available). However, it seems to always train on the CPU. How can I force the training loop to run on the GPU?

Thanks in advance for your help!

It should work if you make the following additional changes:
import deeptrack.deeplay as dl
import torchmetrics as tm
import torch

unet_reg = dl.Regressor(
    model=net,
    loss=torch.nn.CrossEntropyLoss(),
    optimizer=dl.Adam(lr=1e-3),
    metrics=[tm.F1Score(task="multiclass", num_classes=3)],
).create()

data_pipeline = ((image_of_particles & (image_of_particles >> get_target_image))
                 >> dt.MoveAxis(-1, 0) >> dt.pytorch.ToTensor(dtype=torch.float))  # This prepares the pipeline for PyTorch.

dataset = dt.pytorch.Dataset(data_pipeline, length=640, replace=0.01)
train_loader = torch.utils.data.DataLoader(dataset, batch_size=8, shuffle=True)
unet_trainer = dl.Trainer(max_epochs=200, accelerator="auto"). # auto here should select automatically CPU/GPU.
unet_trainer.fit(unet_reg, train_loader)

and  for the image prediction:
predicted_image = unet_reg.predict(input_image).softmax(1)

Please, check it and let us know if you need more help.
Note: We're in the process to adapt all examples to DeepTarck2 2.0.0 to accommodate the shift to torch and deeplay from TensorFlow and Keras.
Some already updated notebooks that might be relevant for you are here:
https://github.com/DeepTrackAI/DeepLearningCrashCourse/blob/main/Ch05_UNet/ec05_1_unet/unet.ipynb
https://github.com/DeepTrackAI/DeepLearningCrashCourse/blob/main/Ch05_UNet/ec05_A_qdots_localization/qdots_localization.ipynb
https://github.com/DeepTrackAI/DeepLearningCrashCourse/blob/main/Ch05_UNet/ec05_B_cell_counting/cell_counting.ipynb

@LiYuan-SJTU We have now corrected the notebook and it's working. See: https://github.com/DeepTrackAI/DeepTrack2/blob/develop/examples/tutorials/03. distinguishing_particles_in_brightfield_tutorial.ipynb

Thank you for providing the updated version of  03. distinguishing_particles_in_brightfield_tutorial.ipynb. I’ve tried running the new version, but I encountered another issue.
When executing the following line:
unet_trainer.fit(unet_reg, train_loader)

I got the error: RuntimeError: expected scalar type Long but found Float .
The error seems to originate from:
return torch._C._nn.cross_entropy_loss(input, target, weight, _Reduction.get_enum(reduction), ignore_index, label_smoothing) located in lighting\pytorch\trainer\trainer.py.
Could you help clarify how to resolve this issue? Is it related to the data type of the labels or inputs in the train_loader? Or is it a compatibility issue with the Lightning package? My lightning package version is 2.5.0.post0.
Thanks again for your assistance!


Not getting any video stream to DK2

As described, I've downloaded Core shapshot 125-g7642085, and OSVR-Oculus-Plugin-build63-v0.1-18-g6a3e9ab-with-core-v0.2-125-g7642085-32bits
Bellow is my osvr_server_config.oculusrift.sample.json that I pass to osvr_server.exe
'''
{
"drivers": [
{
"plugin": "com_osvr_OculusRift",
"driver": "OculusRift",
"params": {
"index": 0
}
}
],
"display": "displays/Oculus_Rift_DK2.json"
}
''''
As a result, HMD tracking works, but no video stream.
Any suggestions?

I am using the same setup. Is this with the Unity editor or the downloaded executable? Did you copy com_osvr_OculusRift.dll to osvr-plugins-0 folder?

Downloaded executable, and yes I've copied com_osvr_OculusRift.dll. On the link below is server init log output.
http://oi57.tinypic.com/2r6i2v8.jpg

Looks fine. I don't think the issue is OSVR related if tracking is working. If you run the Unity demo with the Rift off and OSVR server not running, do you see anything? Is the Rift connected as an extended or duplicated display?

"As a result, HMD tracking works, but no video stream." You tested this with the TrackerViewer utility? Are you seeing video on the monitor but not on the HMD?

Rift display mode: Direct HMD Access.
So demo is running without OSVR server and disabled rift.

When I'm enabling server, I see on monitor video that should be displayed in rift, but rift not displaying anything.

Put the Rift in extended mode. That should fix the issue.

So, every project that uses OSVR and Rift should be running in Extended mode?

I think that's the case. Direct Mode requires building with the Oculus SDK at this point.

Thank you.


Remove --abi option

This removes the --abi option since it does the same thing as --target. The ABI will now be determined based on the target.
This will allow for npm install --target=7.0.0 and npm rebuild --target=7.0.0 without needing to specify a ABI. If i recall correctly --target is a "official" npm option in contrast to --abi.
In the process I also changed the usage of process.version to process.versions.node since process.version would return v7.0.0 instead of 7.0.0.
This behavior is also prerequisite for #61 to determine the right version when installing modules with npm install --runtime=electron --target=1.4.10 --dist-url=https://atom.io/download/electron.

Regarding Electron, a bit more work needs to be done.
I did some research and made a list of Electron ABIs similar to Node.js.
I also did some testing on Linux and Windows with native modules built against different versions of Electron. There are some strange things happening on very old Electron versions but for the most part this looks very promising:
https://travis-ci.org/lgeiger/zmq-prebuilt/builds/180257275
https://ci.appveyor.com/project/lgeiger/zmq-prebuilt/build/1.0.185

I did some research and made a list of Electron ABIs similar to Node.js.

You should make a module out of that

You should make a module out of that

Great idea: https://www.npmjs.com/package/electron-abi

Superseded by #141


ERROR:subliminal.api:Unexpected error in provider 'opensubtitles', discarding it

Hi,
This error has just started to appear. Is there a way to work around it?
ERROR:subliminal.api:Unexpected error in provider 'opensubtitles', discarding it
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/subliminal/api.py", line 116, in list_subtitles
provider_subtitles = self[name].list_subtitles(video, provider_languages)
File "/usr/local/lib/python2.7/site-packages/subliminal/api.py", line 61, in getitem
provider.initialize()
File "/usr/local/lib/python2.7/site-packages/subliminal/providers/opensubtitles.py", line 109, in initialize
'subliminal v%s' % get_version(version)))
File "/usr/local/lib/python2.7/xmlrpclib.py", line 1233, in call
return self.__send(self.__name, args)
File "/usr/local/lib/python2.7/xmlrpclib.py", line 1591, in __request
verbose=self.__verbose
File "/usr/local/lib/python2.7/xmlrpclib.py", line 1273, in request
return self.single_request(host, handler, request_body, verbose)
File "/usr/local/lib/python2.7/xmlrpclib.py", line 1301, in single_request
self.send_content(h, request_body)
File "/usr/local/lib/python2.7/xmlrpclib.py", line 1448, in send_content
connection.endheaders(request_body)
File "/usr/local/lib/python2.7/httplib.py", line 997, in endheaders
self._send_output(message_body)
File "/usr/local/lib/python2.7/httplib.py", line 850, in _send_output
self.send(msg)
File "/usr/local/lib/python2.7/httplib.py", line 812, in send
self.connect()
File "/usr/local/lib/python2.7/httplib.py", line 1212, in connect
server_hostname=server_hostname)
File "/usr/local/lib/python2.7/ssl.py", line 350, in wrap_socket
_context=self)
File "/usr/local/lib/python2.7/ssl.py", line 566, in init
self.do_handshake()
File "/usr/local/lib/python2.7/ssl.py", line 788, in do_handshake
self._sslobj.do_handshake()
SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:581)

It's most likely a misconfiguration of your environment or a temporary failure of OpenSubtitles. If you can access https://api.opensubtitles.org/xml-rpc without SSL warning you should be able to use subliminal without issue.


Adding ollama support fails

I tried to include ollama model into /home/user/.config/ailice/config.json as explained in the readme:
(env) user@debian-ai:~/AIlice$ ailice_main --modelID=ollama:llama2:latest --prompt="main"
config.json is located at /home/user/.config/ailice

In order to simplify installation and usage, we have set local execution as the default behavior, which means AI has complete control over the local environment. To prevent irreversible losses due to potential AI errors, you may consider one of the following two methods: the first one, run AIlice in a virtual machine; the second one, install Docker, use the provided Dockerfile to build an image and container, and modify the relevant configurations in config.json.  Note that this may include downloading the model weights, so it may take some time.
Vector database has been started. returned msg: vector database has been switched to a non-persistent version. tokenizer: bert-base-uncased, model: nomic-ai/nomic-embed-text-v1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Encountered an exception, AIlice is exiting: 'llama2:latest'
  File "/home/user/AIlice/ailice/AIliceMain.py", line 126, in main
    mainLoop(**kwargs)
  File "/home/user/AIlice/ailice/AIliceMain.py", line 91, in mainLoop
    llmPool.Init([modelID])
  File "/home/user/AIlice/ailice/core/llm/ALLMPool.py", line 21, in Init
    self.pool[id] = MODEL_WRAPPER_MAP[config.models[modelType]["modelWrapper"]](modelType=modelType, modelName=modelName)
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/user/AIlice/ailice/core/llm/AModelChatGPT.py", line 16, in __init__
    modelCfg = config.models[modelType]["modelList"][modelName]
               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^

the config.json looks like this:
 {
  "maxMemory": {},
  "quantization": null,
  "models": {
    "hf": {...},
    "peft": {...},
    "oai": {...},
    "groq": {...},
    "mistral": {...},
    "ollama": {
      "modelWrapper": "AModelChatGPT",
      "apikey": "fakekey",
      "baseURL": "http://localhost:4000",
      "modelList": {
        "ollama/llama2:latest": {
          "contextWindow": 8192,
          "systemAsUser": false
        }
      }
    },
    "anthropic": {...}
  },
  "temperature": 0.0,
  "flashAttention2": false,
  "speechOn": false,
  "contextWindowRatio": 0.6,
  "services": {...}
}

Considering your configuration, the appropriate modelID should be:
ollama:ollama/llama2:latest

That gives another error:
Encountered an exception, AIlice is exiting: 'formatter'
File "/home/user/AIlice/ailice/AIliceMain.py", line 126, in main
mainLoop(**kwargs)
File "/home/user/AIlice/ailice/AIliceMain.py", line 91, in mainLoop
llmPool.Init([modelID])
File "/home/user/AIlice/ailice/core/llm/ALLMPool.py", line 21, in Init
self.pool[id] = MODEL_WRAPPER_MAP[config.models[modelType]["modelWrapper"]](modelType=modelType, modelName=modelName)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/user/AIlice/ailice/core/llm/AModelChatGPT.py", line 17, in init
self.formatter = CreateFormatter(modelCfg["formatter"], tokenizer = self.tokenizer, systemAsUser = modelCfg['systemAsUser'])

It seems that there was a misleading error in my documentation (strange why such an error would occur).
The correct configuration requires adding a line:
"ollama/llama2:latest": {
"formatter": "AFormatterGPT",
"contextWindow": 8192,
"systemAsUser": false
}


Can't output graphics as wrapped React elements.

Describe the bug
Reading documentation I have an impression that outputting graphics (elements that are placed on Graphics page in Figma file) as wrapped react elements is build into the Figmagic library. I manage only to export everything as svgs. I tried to use custom template but with no success.
My config
"figmagic": "^4.0.15"
{
  "fontUnit": "rem",
  "remSize": "10",
  "outputFileName": "figma.json",
  "outputFolderBaseFile": ".figmagic",
  "outputFolderTokens": "tokens",
  "outputFolderElements": "elements",
  "outputFormatGraphics": "svg",
  "outputFolderGraphics": "./src/icons",
  "outputGraphicElements": true,
  "outputGraphicElementsMap": true,
  "syncGraphics": true,
  "outputFormatCss": "mjs",
  "outputFormatTokens": "mjs",
  "spacingUnit": "rem",
  "usePostscriptFontNames": true,
  "templates": {
    "templatePathGraphic": "./node_modules/figmagic/templates/graphic",
    "templatePathReact": "./node_modules/figmagic/templates/react",
    "templatePathStyled": "./node_modules/figmagic/templates/styled",
    "templatePathStorybook": "./node_modules/figmagic/templates/story"
  }
}

When I run: "figmagic:graphics": "node ./node_modules/figmagic/build/index.js --syncGraphics" I get only svg files.
When I run "figmagic:sync": "node ./node_modules/figmagic/build/index.js --syncElements --syncGraphics" I get one element that I have in Elements page but I don't get wrapped React elements for svg files
Expected behavior
SVG icons placed on Graphics page in Figma are exported as React components
Desktop (please complete the following information):

macOS

Hi!
Given that you set "syncElements": true in the config (or use --syncElements) you should be getting a result similar to the attached image.

Hi @jmak,
I will be closing this since this should be able to be corrected as per above. I will look into updating docs to clarify!

Thanks for your explanation.


The link to multiple-tracker 404s

Pointed at:
https://github.com/philipwalton/analyticsjs-boilerplate/blob/master/src/analytics/multiple-tracker.js
Should probably resolve to:
https://github.com/philipwalton/analyticsjs-boilerplate/blob/master/src/analytics/multiple-trackers.js

Thanks for letting me know! This should be fixed now.


a Big Bug!

 God Damed!Thanks and Fu,ck,you!!!
LOOK AT THIS :-1: var cal = that.calendar;
curr = cal.find('.calendar-dates'),
dayLabel = cal.find('.calendar-labels'),
currMonth = cal.find('.calendar-curr-month'),
container = cal.find('.calendar-date-holder'),
cElem = curr.clone(),
rows = [], cells = [], count = 0;

@152016726, I'm sorry can you explain to me what bug this is? Because to me this is just a coding convention issue. This doesn't cause any problem to the plugin, because you can declare variables in JavaScript without putting the var keyword before it, as far as I know.


[WIP] New TIS Analysis

This PR provides an alternate approach to do TIS analysis. Overall, I'm suggesting a 3-step process for updating our analysis subsystem; this PR will do step 1:

Have this as an alternate approach to the current approach. It has the advantage that it is more flexible, but the disadvantage that it is a little harder to use than the old version. For now, both exist side-by-side.
In a future PR (1.0 or 1.x), keep the simplified API of the old version, but internally use the new version. That means we'll be getting rid of old code that doesn't have unit tests, and replacing it with code that does.
Create better default approaches, and (probably in 2.0) replace the current defaults with defaults that will be even easier (and less error-prone) for users (see, e.g., #551).

What's new in this approach:
First, none of the TIS analysis code will be located inside the "high-level" objects like Transition or TransitionNetwork. Moving the analysis outside of that makes it easier to customize the analysis approach. For example, it is now very easy to change the details (like cutoff) of the WHAM procedure, or to replace it with something else (once we have something else — MBAR, TISBAR — implemented). It also makes it easier to add very different approaches to obtain the rates from TIS (e.g., using path-type analysis), and provides a more natural way to switch between a pre-calculated flux (as we need for MISTIS) and the minus move flux.
Another big idea in this is that most of the classes are basically functions. That is, they don't cache their results. Caching is convenient for efficiency, but really obnoxious when trying to re-use parts in some interesting way. The only objects that cache results are the main TISAnalysis object (and its subclass, StandardTISAnalysis). That way the "outermost" objects in the analysis heirarchy cache the results for efficiency, and the details of how things are calculated are treated more like functions.
This is a huge PR, but nearly all of it is in new files. A few more details will follow in the comments below. Before it is complete, I'll also add a detailed overview of this analysis system to the docs; once it is there, that might be the best place to go in order to understand this PR.

[x] New TIS analysis approach for crossing probability
[x] Unit tests for crossing probability
[x] New TIS analysis approach for conditional transition probability
[x] Unit tests for conditional transition probability
[x] New TIS analysis approach for pre-calculated flux
[x] Unit tests for pre-calculated flux
[x] Main TISAnalysis class and StandardTISAnalysis subclass
[ ] Unit tests for StandardTISAnalysis
[x] Test new TIS against MISTIS example
[x] New TIS analysis approach for minus move flux
[ ] Unit tests for minus move flux
[x] Test new TIS against MSTIS example
[ ] Docstrings
[ ] Example notebooks
[ ] Detailed overview docs

A few comments on some changes you might notice (outside the main new files):
Flux
The minus move flux here re-uses code from #435 instead of the older code from #254. The results are not identical, because when the minus move has two excursions from the interface, the old code only used the first in its statistics. This uses both. (And a checked [by eye] that the lengths found for "inside" were the same and that alternating length from the "outside" were the same as the code from #254.)
TrajectoryTransitionAnalysis.flux_from_flux_dict
Refactored so that this part of the code can be re-used elsewhere.
Changes in network.py
I added some convenience dictionaries for mapping between sampling transitions and analysis transitions.

This is ready for review.
It is an incredibly large PR. My suggestion for reviewing it:

It includes new documentation in docs/topics/tis_analysis.rst and the visual description in docs/topics/tis_analysis_structure.png. Look at those first, to get the big picture.
See it in use in the new notebook example/toy_model_mstis/toy_mstis_A3_new_analysis.ipynb.
Most of the actual additions changes are in openpathsampling/analysis/tis/, a new directory with several new files. This is the main thing to review. These things are not in the main openpathsampling namespace; you have to use them by importing openpathsampling.analysis.tis.
Other changes are relatively minor, but include some performance stuff (especially in sequential ensemble), some new conveniences in networks, some minor docs updates, and some PEP8 stuff.

In general, this looks fine to me. I have a few suggestions or think we might think about.
You are using some complicated looking dict constructs to hold specific data. It looks like a very flexible thing to use, but it makes it - as you mention above - also complicated to use. I think most objects are already generated in the correct structure, but I was wondering if it would be possible to hide this complexity to some degree in classes that are returned. A user that does not create these objects does not really care how the data is internally structure and might be scared by an object like this.
I guess you know what I mean. E.g. the fluxes could just be a FluxData or FluxDescriptor object that holds the data with some convenience function to access specific data and some helper constructors to make it easy to construct these. But we can do that in a later version anyway.
I like the figure that is also for understanding TIS a good image to have when talking about the decomposition of mathematical objects needed to get the rate, etc. And so I see the idea to make it flexible and replace the methods used. Say replace flux computation by given fluxes from an external simulation.
Overall the analysis part is (and I have so solution to this) one of the more complicated parts, which I hope will not stay that way. Say in a perfect world, the definition of ensembles should imply the way to compute all properties and also which properties are accessible and not require knowledge about the whole analysis process. I mean, that would be pretty cool, but possible a multi-year project :) ...
I say, go ahead an merge as soon as you want to. It looks good the way it is.

Thanks; I'll merge, but add discussion here to clarify a few points so you can see if there's anything that need to be modified in the near-ish future. Note that I consider this still a somewhat experimental API; even if it goes into 0.9.3 as-is, we should be allowed to change it before 1.0. (In fact, I already know one thing I'll be changing, which is to get the WHAM code to return weights as well, which we will need for reweighted path ensemble -- a quick addition, if I wasn't coming up on a deadline!)
To your specific comments:

You are using some complicated looking dict constructs to hold specific data.

Overall, I would split these into 3 categories:

The (very complicated) results dictionary in the TISAnalysis objects.
The dictionary used as input to the DictFlux object (or output from the MinusMoveFlux)
The dictionary based on the TrajectoryTransitionAnalysis for fluxes, which has keys of 'in' and 'out', each mapping to a TrajectorySegmentContainer holding specific frames of a trajectory representing "inside the interface" and "outside the interface" segments.

I'll take these in order 2, 1, 3:
Only the second should ever be created by a user. That one is of the format {(state, interface): flux_value}, which is, I think, already the simplest possible way to make it. It's the flux out of a given state and through a given interface, so you need the state and interface as key, and the flux as a value. Also, the MinusMoveFlux outputs in the same format that the DictFlux takes as input, so that can simplify some things. (Don't remember if DirectSimulation outputs in the same format, but if not, I should make that change.)
The first category, the results dict, does almost exactly what you suggest, except without a new class. The results dictionary should almost never be used directly; instead, you use convenience methods inside the TISAnalysis or StandardTISAnalysis class to access it. But instead of using a container class, we can just save the results dictionary (into storage.tags) and load it into the class. That stores the final results as well as any intermediates that might be worth analyzing. By just using the dictionary instead of a class, we don't have to worry about how it is handled in storage, don't have to worry about the user understanding immutability, and we can keep a clean separation of the "function" and "data" parts of the analysis (the setup of the way you do the analysis is a "function," the results are the "data;" once you mix the two, we start getting the problems with extensibility that this PR is trying to avoid).
I considered having a separate results class, but the problem was that then you'd need a different results class for each analysis setup, and that would be too hard to manage (not to mention needing to create stores for them). I think that properly dealing with these intermediates requires lots of documentation. This PR already includes a lot, but there may be a need for even more.
The third category is leftover from TrajectoryTransitionAnalysis (#435, #448). This could be moved into a namedtuple instead of a dict, but hasn't been yet. This is only an intermediate part of the calculation, and won't usually be accessed by users (but it is saved because it could be useful for troubleshooting, if a user knows how to use it.)

A user that does not create these objects does not really care how the data is internally structure and might be scared by an object like this.

I see what you're saying, but my hope is that these objects would normally be hidden from users, in the same way that the fact that the minus move is actually a complicated ConditionalSequentialMover is hidden -- always accessible if you know how to look for it, but not something that you must deal with. Digging into the details at that level is useful for troubleshooting, but hopefully not something you'll need to do.
The only exception is if you use the DictFlux, there's number 2 above. But I think that is as straightforward as it can be.
For the simplest cases, we can (and probably should) directly replace the current analysis in the TransitionNetwork objects with this. By using default behavior, usage there is just as easy as it currently is. What's new in this PR is the ability to set up an analysis that doesn't use the defaults. Overall, I'd recommend pushing users toward using these analysis classes instead of the network methods, because I think that will likely help them in the future, even if it technically takes one more line of code (creating a StandardTISAnalysis object).

I like the figure that is also for understanding TIS a good image to have when talking about the decomposition of mathematical objects needed to get the rate, etc. And so I see the idea to make it flexible and replace the methods used.

Glad you like that figure! I'm pretty happy with the docs on the TIS analysis here; I think it's a clearer picture of the connection between code and math than is often made. And yes, the flexibility is the primary goal of this PR.

Say in a perfect world, the definition of ensembles should imply the way to compute all properties and also which properties are accessible and not require knowledge about the whole analysis process. I mean, that would be pretty cool, but possible a multi-year project :)

Haha -- multi-year or multi-lifetime? :-) I think the biggest challenge is finding the right amount of extra troubleshooting information to provide. I mean, the rates are easy enough to calculate, but most of the additional information stored in the results dict are about troubleshooting and sanity-checking your results. (This is also where the hypothetical "red flags" module I've talked about for years plays a role -- I worry that inexperienced users will get nonsense results and not know how to check their data for signs that they can't trust it.) But that's definitely stuff to explore in the future.


[SPARK-17614] [SQL] sparkSession.read() .jdbc(***) use the sql syntax "where 1=0" that Cassandra does not support

What changes were proposed in this pull request?
Use dialect's table-exists query rather than hard-coded WHERE 1=0 query
How was this patch tested?
Existing tests.

Test build #65766 has started for PR 15196 at commit 27fe87d.

Test build #65766 has finished for PR 15196 at commit 27fe87d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65766/
Test PASSed.

Test build #65819 has started for PR 15196 at commit aa64b82.

Test build #65819 has finished for PR 15196 at commit aa64b82.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65819/
Test PASSed.

Merged build finished. Test PASSed.

Just curious ,  Is overwrite of getSchemaQuery() for  Posgres, and MySQL  dialects required ?  I thought default query works  fine  for My SQL, and Postgres also.

@sureshthalamati I'm assuming it's required because the existing getTableExistsQuery is overridden in the same way. @JoshRosen if this is what you had in mind, I'll merge it.

@srowen, I think that @sureshthalamati is right and that we shouldn't override for those other dialects until we know that there's a problem with them.

Sounds fine. I guess I'm surprised these wouldn't have to be overridden in the same way, but, on the other hand I suppose the existing query works today for MySQL et al? this is a more conservative change now, yes.

Test build #65928 has started for PR 15196 at commit c8789b5.

Test build #65928 has finished for PR 15196 at commit c8789b5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65928/
Test PASSed.

@srowen  Thanks for the clarification. My understanding is  because read path takes query,  "select * from $table where 1!=0  is preferred when it works . Hope is that source  will optimize the query , and does not execute the user specified query completely.
getTableExistsQuery() is primarily used to check the table in the data frame write path, there is no user specified query in this case.  "select 1 from $table limit 1" performance might be ok. If we find select * from $table where 1 !=0 is better, then this query can be changed;  otherwise leaving it as is may be the safest bet.
I did not see CassandraDialect in the change set. Are you planning to add one ?

OK, let's leave the more conservative change here. I myself don't know what works or not on these dialects. I didn't add the Cassandra dialect; I think the idea is that a user could add such a dialect, for now, but only if this bug is fixed so that this query can be overridden. Later incorporating it into Spark is another question.

LGTM

Merged to master


x/pkgsite: Incorrect "latest" version leads to missing "Deprecated" message.

What is the URL of the page with the issue?
https://pkg.go.dev/github.com/github/fakeca
What is your user agent?
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36

Screenshot

What did you do?
I published a v0.2.0 tag for three packages, each with a similar // Deprecated: comment in go.mod:

https://pkg.go.dev/github.com/github/fakeca
https://pkg.go.dev/github.com/github/certstore
https://pkg.go.dev/github.com/github/ietf-cms

What did you expect to see?
All three show a ⚠ Deprecated message like this:

What did you see instead?
https://pkg.go.dev/github.com/github/fakeca doesn't show the message, but the other packages do.

https://pkg.go.dev/github.com/github/fakeca?tab=versions seems to know about v0.2.0 but it doesn't seem to be getting picked up as the "latest"<EMAIL_ADDRESS>shows this, and clicking "Go to latest" takes you to v0.1.0:

The proxy has the right latest, so pkgsite seems to be behind.
go mod download -json github.com/github/fakeca@latest
{
	"Path": "github.com/github/fakeca",
	"Version": "v0.2.0",
	"Info"<EMAIL_ADDRESS>	"GoMod"<EMAIL_ADDRESS>	"Zip"<EMAIL_ADDRESS>	"Dir"<EMAIL_ADDRESS>	"Sum": "h1:xtBwXN7dmDPK8U5z0KHW1jupDVTDSINxrKRAc5//XFY=",
	"GoModSum": "h1:XhVUBgZ9+o0O6XzVXOl4H5qNxkV/MImtB3FuI/Zcti0="
}

This seems to have resolved itself by now. 🤔
(But as documented with screenshots, it definitely was an issue for a while!)

I'm running into the same issue with the module github.com/nishanths/exhaustive. The latest tag at the time of writing is v0.7.9, which pkg.go.dev knows about in its versions page: https://pkg.go.dev/github.com/nishanths/exhaustive?tab=versions.

However the v0.7.9 main page doesn't seem to think its version the latest. Instead the v0.7.8 main page seems to think its version is the latest.
v0.7.9 main page:

v0.7.8 main page:

(And just for completeness, no symbols were deprecated in packages in this module between the two versions.)

I'm not sure exactly what happened there, but I do notice that v0.7.8, ...9, ...10 and ...1 were published within two hours of each other on November 11. It's possible that some out-of-order processing caused a temporary glitch, but it seems fine now: the latest page is v0.7.11, as it should be.


v4.8.0 not published

Hi again 😄
@newbreedofgeek, did you forget to release version 4.8.0 on npm?
Greetings, Tom

@tomtoxx tnx for the push - its now published.
Are you able to do a simple Redux example? I would really appreciate that...


UP-4934:  Enhancements to the JGROUPS DDL selection strategy -- list …

…an additional SQLServer2008Dialect (as well as SQLServerDialect); all dialects not listed in jgroupsInitSqlMap will use the jgroupsDefaultInitSql
https://issues.jasig.org/browse/UP-4934

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change

Just a couple small tweaks intended to make the solution more flexible.

Nice improvement!


emit module-deps 'missing' event from browserify

The missing event is useful because it will tell me the name of the thing that was required, and its parent: https://github.com/substack/module-deps/blob/master/index.js#L95
but this event is not exposed by browserify:
https://github.com/substack/node-browserify/blob/master/index.js#L374
I tried listening to the event like this:
bundler.pipeline.get('deps').on('missing', function(id, parent) {
       console.error("CANNOT REQUIRE: [" + id + "] from [" + parent + "]");
});

but that does not work, I had to do this instead:
bundler._mdeps.on('missing', function(id, parent) {...});

Which isnt good.

Hello @mkoryak. So you're passing ignoreMissing: true to browserify in both cases?
As you say, relying on the non-public API _mdeps is not good. You can do it via the pipeline, it just needs to be b.pipeline.get('deps').get(0) (by default that's the object that's at _mdeps). That's better, but not all the way; see #1158.
I'll leave this open for now as a feature request for browserify to re-emit missing from module-deps.

 So you're passing ignoreMissing: true yes

No problem!


Outline out of order and missing sections

I'm new to AsciidocFX, but from what I can tell, the outline appears to be misbehaving when I include files from a top level document.
I've created an example where the top level document includes two chapter documents, each with 3 sections of their own.  For some reason, sections of chapter 2 appear to be missing, and the 1 section that is present, is out of order (i.e., the one visible section from chapter 2 appears before the same section in chapter 1).  As can be seen from the preview (see screen capture attachment), this renders properly, but the outline doesn't seem to accurately reflect the document structure.
It seems that the section from chapter 2 that does appear in the outline is dependent upon whether there is any text in the parent section or not (i.e., there is currently no text before the child section).  Adding text to this parent section, makes the child section disappear from the outline as well, leaving only the sections from chapter 1 in the outline.
I've tried this on Linux 1.6.6 and Windows 1.6.8 versions (both versions using the included JRE) and both exhibit this behavior.
Note that for each individual chapter file, the outline appears correct, it's only when viewing the outline from the top-level document that it appears incorrect.
As more of an investigation into this, I've also tried in-lining chapter 1 into the top-level document and leaving chapter 2 as an include.  When I do this, the outline will then show all sections of both chapters, but chapter 2 (and it's sections) are shown in the outline before chapter 1 (and it's sections).
test.zip

I fixed this issue here https://github.com/asciidocfx/AsciidocFX/commit/922181011f27259fe460af4f25aa90770754ac8f . It will be available in next release. However, when you click outline item, it will not able to position line in any included file.

I'm closing this issue, please let me know if it is not working.


debug commit

I'm closing this as it seems to be a commit issued for some debugging purposes. Please feel free to reopen if we still need this.